Veritas NetBackup™ OpsCenter 8.0 Performance and Tuning Guide
- Overview
- About OpsCenter configuration
- About OpsCenter performance and tuning
- About tuning OpsCenter for increased performance
- About saving the OpsCenter log files on a different drive
- About adjusting the heap size or cache size for OpsCenter services
- About OpsCenter database defragmentation
- Moving OpsCenter server to a different computer
- OpsCenter best practices
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
Stop all OpsCenter services.
- Copy all the database files (including log files that is *.*) from the installed location to a temporary location.
The database location is as follows:
Windows
OpsCenterInstallLocation\OpsCenter\server\db\data
UNIX
OpsCenterInstallLocation/SYMCOpsCenterServer/db/data
- Copy the database password file, that is
db.conf
file from the installed location to a temporary location.The
db.conf
file location is as follows:Windows
OpsCenterInstallLocation\OpsCenter\server\config
UNIX
OpsCenterInstallLocation/SYMCOpsCenterServer/config
- 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
atutil
utility. AT data comprises OpsCenterUsers(vx) users and certificates. - Copy the XML file to the OpsCenter target host.
- 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.
- Copy the backed up database files from the temporary location to the OpsCenter database location.
The database location is as follows:
Windows
OpsCenterInstallLocation\OpsCenter\server\db\data
UNIX
OpsCenterInstallLocation/SYMCOpsCenterServer/db/data
- Copy the backed up the database password file, that is
db.conf
file from the temporary location to the OpsCenter server installed location.The
db.conf
file location is as follows:UNIX
Windows
OpsCenterInstallLocation\OpsCenter\server\config
OpsCenterInstallLocation/SYMCOpsCenterServer/config
- 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.