Moving OpsCenter server because of issues in the existing setup
This section provides the procedure to move OpsCenter server to a different machine. You need to move OpsCenter server to a different machine in certain scenarios for example:
Faulty hardware
Hardware upgrade
Operating System upgrade
Moving from physical machine to virtual machine (or from virtual machine to physical machine)
To move OpsCenter server to a different machine
- Steps to be carried out on the OpsCenter source host
On the OpsCenter source host, perform a backup of the OpsCenter database using the dbbackup script. You should run this script when you need to back up your OpsCenter database and database password file (
db.conf). - OpsCenter source host may have authentication (AT) data that you want to import into OpsCenter target host. You need to first export the AT data on the OpsCenter source host, which you can import into OpsCenter target host.
Export the AT data to an xml file using the
atutilutility. AT data comprises OpsCenterUsers(vx) users and certificates. - Copy the XML file to the OpsCenter target host.
Note:
While copying the exported xml file, the DOS to UNIX conversion may result into garbage characters in the xml file that can cause import failure. To avoid this problem, copy the xml file through FTP and with binary format.
- Steps to be carried out on the OpsCenter target host
Install OpsCenter on the new host that is target host.
- Stop all OpsCenter services.
- Carry out the performance tuning steps that you had done earlier.
The new OpsCenter Performance and Tuning Guide provides information on how to tune OpsCenter for improved performance. The online version of the OpsCenter Performance and Tuning Guide can be found at:
- Restore the database that you have backed up earlier.
- Update the following information from the
db.conffile:If you are using the port that is different than the default one, update the value of the db.port as follows:
db.port=13786
Set the db.serviceName parameter to the name of the target host as follows:
db.serviceName=TargetHostName
- Import old authentication or AT data into OpsCenter target host.
Make sure that you have copied the export xml file that you have created on the OpsCenter source host to OpsCenter target host.
Run the following command for import:
Windows
<OpsCenterInstallLocation>\OpsCenter\server\authbroker\bin\atutil import -p <password of exported xml file> -f <location of xml file that contains old AT data> -z <location of AT data folder> - overwrite
UNIX
<OpsCenterInstallLocation>/SYMCOpsCenterServer/authbroker/bin/atutil import -p <password of exported xml file> -f <location of xml file that contains old AT data> -z <location of AT data folder> - overwrite
Note:
If the import is not successful, the default OpsCenter user needs to reset the passwords of OpsCenterUsers(vx) domain users that you have imported from the earlier OpsCenter version. Trust between NBAC-enabled NetBackup / PureDisk server and OpsCenter server need to be established again.
- Start OpsCenter services.