20.2 Moving the NNMi configuration and database
To move the NNMi configuration and the database, such as from a test system to a production system, make a complete backup of all NNMi data on the source (test) system, and then restore the backup to the target (production) system. To ensure that no changes are made to the NNMi database after the backup is made, stop all NNMi processes and create an offline backup.
- Example:
nnmbackup.ovpl -type offline -scope all -target nnmi_backups\offline
Verify that the items listed in 18.3.2 Different-system restore are the same in both systems, and then execute a command similar to the following example.
- Example:
nnmrestore.ovpl -source nnmi_backups\offline\newest_backup
- Important note
-
NNMi uses the same SSL certificate for accessing the database and for supporting HTTPS access to the NNMi console. The certificate for accessing the database was created when the NNMi processes first started on the source system. This certificate is included in the backup and restore data. Without this certificate, NNMi cannot access the database from the target system.
However, for HTTPS access to the NNMi console, the SSL certificate must be generated on the target system. Because the current implementation of JBoss does not support certificate merging, NNMi does not support HTTPS access to the NNMi console on a system that was set up by restoring data from a different system. If the target system must support HTTPS access to the NNMi console, use the procedure described in 20.3 Moving the NNMi configuration, and then begin data collection anew on the target system.
For different system restores, during the restore to the source system, the old SSL certificate is saved on the server (as nnm.keystore.backup and nnm.truststore.backup). The old and new certificates are merged during the restoration.