In this situation, we suggest the following principle to find the best practice.
1.Upgrade OS and NNM version to latest one as far as possible to reduce the version gap between OLD server and NEW server,it would help the data moving become more smoothly.
2.Follow formal support way as far as possible to reduce any potential risk and unnecessary problem.
Here is the verified steps that was implemented by the customer successfully and without any error or problem.
1 Identify two servers that you will use during this procedure:
• Server A is the current NNMi management server running RHEL (version 5.x).
• Server B will become the new NNMi management server running RHEL 6.4 or later.
2.Install HP Public key on the server B.
To do this, point your browser to the following location and follow the instructions:
for more detailed informaiton, please refer to installation guide.
3.On server A, Upgrade NNM9.10+patch6/Linux5.x to NNM9.20+patch4/Linux5.5, if NNM9.10/Linux5.x lower than 5.4 then upgrade OS version to 5.4 or later firstly.
4.Use nnmbackup.ovpl to take a offline full backup on server A.
#/opt/OV/bin/nnmbackup.ovp –type offline –force –target <directory>
5.On server B, install Linux6.4 and NNM9.20+patch4.
6. restore data which from step 4 into server B.
#nnmrestore.ovpl –force –source <backupfile full path and filename>
7.On server B, upgrade NNM9.20+patch4 to NNM10.0
8.ovstop -v/ovstart -v to restart NNM.