How to migrate OpsCenter to new hardware

Description

1. Log on to the old OpsCenter server host and back up the OpsCenter database.
   • The dbbackup.bat script backs up the database files, database password files, and encryption key file in the backup directory that you specify, for example C:\MyDbBackupFolder.
   • On  a Windows OpsCenter server, as an administrator run the following command:
     install_path\OpsCenter\server\bin\dbbackup.bat C:\MyDbBackupFolder
2. Install the same version of OpsCenter on the new server.
3. When the install is complete copy the directory C:\MyDbBackupFolder from the old server to the new server.
4. Tune OpsCenter to use the resources on the new server. This is imperative to get the best performance out of the OpsCenter application and database as possible.
   • Related Article: OpsCenter Tuning Quick Reference - https://www.veritas.com/docs/100032298
5. Restore the OpsCenter database files on the new server by executing the following command:
   install_path\OpsCenter\server\bin\dbbackup.bat C:\MyDbBackupFolder -restore
6. If the OpsCenter server name was changed during the migration edit the file db.conf to reflect the new host name of the OpsCenter server.
   • The file is located here:
     install_path\OpsCenter\server\config\db.conf
   • Modify this line to reflect the new host name:
     db.serviceName=OPSCENTER_<newhostname>
7. If the OpsCenter server name was changed, also change the OpsCenter Server name in the NetBackup Master Server Server's list to match the new OpsCenter hostname. Remove the old server name if it is no longer applicable.
8. If you are using LDAP on the original OpsCenter server you will need this configured on new OpsCenter server as well.

Note: When migrating OpsCenter from Windows to Linux, or vice versa, you need to update the path to the transaction log in the database or the migration will not work. Once the application has been migrated to the new OS, the database recovered and OpsCenter has been tuned to use the new server/resources, the following command needs to be ran, to update the transaction log path:

• Windows:
  • install_path\OpsCenter\server\db\WIN64\dblog -t directory_path/vxpmdb.log database_path/vxpmdb.db
• Linux:
  • install_path/SYMCOpsCenterServer/bin/dblog -t directory_path/vxpmdb.log database_path/vxpmdb.db

Example Commands: (if installed to the default locations)

• Windows:
  • C:\Program Files\Symantec\OpsCenter\server\db\WIN64\dblog -t C:\Program Files\Symantec\OpsCenter\server\db\data\vxpmdb.log C:\Program Files\Symantec\OpsCenter\server\db\data\vxpmdb.db 
• Linux:
  • /opt/SYMCOpsCenterServer/db/bin/dblog -t /opt/SYMCOpsCenterServer/db/data/vxpmdb.log /opt/SYMCOpsCenterServer/db/data/vxpmdb.db