16.7.3 Backing up and restoring NNMi

(1) Backing up NNMi

You can back up NNMi configured for application failover by using the same procedure as is used for ordinary systems. However, you cannot use the -force option (for forcing NNMi into a state suitable to backup). Place NNMi in a state appropriate for backing up before starting backup.

Do the following on the active server:

1. Place NNMi in a state appropriate for backing up.

   Using nnmbackup.ovpl:

   For online backup: Start the NNMi service.

   For offline backup: Stop the NNMi service.

   Using nnmbackupembdb.ovpl:

   Start the NNMi service.

2. Make a backup.

   Run the nnmbackup.ovpl or nnmbackupembdb.ovpl command.

   Important note

   Make the backup on the active server (the server that was previously running if you stopped NNMi for an offline backup).

To Page Top

(2) Restoring NNMi

To restore your NNMi database from an original backup when active and standby NNMi management servers are configured for application failover, follow these steps:

1. Run the nnmcluster -halt command on the active NNMi management server.

   This stops NNMi on both the active and standby servers. To verify that the NNMi service has stopped, run the nnmcluster command with no options specified (interactive mode) or the nnmcluster -display command.

2. Delete or move the following directories on both the active and standby NNMi management servers:

   • Windows:

     %NnmDataDir%shared\nnm\databases\Postgres_standby

     %NnmDataDir%shared\nnm\databases\Postgres.OLD

   • UNIX:

     $NnmDataDir/shared/nnm/databases/Postgres_standby

     $NnmDataDir/shared/nnm/databases/Postgres.OLD

3. Restore the database on the active NNMi management server:

   a. Temporarily cancel the application failover configuration setting.

   Modify the following file to comment out the cluster name com.hp.ov.nms.cluster.name (by adding the characters #! at the beginning of the line):

   Windows:

   %NnmDataDir%shared\nnm\conf\props\nms-cluster.properties

   UNIX:

   $NnmDataDir/shared/nnm/conf/props/nms-cluster.properties

   b. Restore the database as normal. Run the nnmrestore.ovpl command or the nnmrestoreembdb.ovpl command with the -force option. After the services necessary for restoration are started by the specification of the -force option, restoration is performed. For details about these commands, see 18.3 Restoring NNMi data.

   If you restore data that was backed up using nnmbackup.ovpl, the change made in step a might be overwritten in the restored files. Therefore, do step a again.

   c. Run the ovstop command on the active NNMi management server. This stops the services that were started in step b for restoration processing.

   d. Reset the application failover configuration.

   Modify the following file to uncomment the cluster name com.hp.ov.nms.cluster.name (by deleting the #! characters added in step a):

   Windows:

   %NnmDataDir%shared\nnm\conf\props\nms-cluster.properties

   UNIX:

   $NnmDataDir/shared/nnm/conf/props/nms-cluster.properties

4. Run the ovstart command on the active NNMi management server.

5. Wait until the active NNMi management server generates a new backup (a ZIP file for synchronizing the active and standby servers).

   To verify that this step is complete, run the nnmcluster -display command and look for an ACTIVE_NNM_RUNNING message.

6. Run the ovstart command on the standby NNMi management server.

   The standby NNMi management server copies and extracts the new backup (the ZIP file created in step 5). To verify that this step is complete, run the nnmcluster -display command and look for a STANDBY_READY message.

To Page Top