Administer > Maintain NNMi > Changing the Management Server > Moving the NNMi Configuration and Embedded Database

Moving the NNMi Configuration and Embedded Database

To move the NNMi configuration and the embedded database, for example from a test system to a production system, perform 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 NNMidatabase after the backup is made, stop all NNMi processes and create an offline backup. For example:

nnmbackup.ovpl -type offline -scope all -target nnmi_backups\offline

Ensure that the requirements listed in "Different System Restore" on page 1 are met on the new system, and then run a command similar to the following example:

nnmrestore.ovpl -source nnmi_backups\offline\newest_backup

Caution NNMi uses the same SSL certificate for accessing the database (embedded or external) and 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 Moving the NNMi Configuration, and then begin data collection fresh on the target system.