To move the existing OpsCenter server to a different machine

1. Steps to be carried out on the existing OpsCenter server 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).

2. Existing OpsCenter server host may have AT (Veritas Product Authentication Service) data that you want to import into the new OpsCenter. You need to first export the AT data on the existing OpsCenter server host, which you can import into the new OpsCenter setup.

   Export the shared or remote AT broker's data to an XML file using the atutil utility. AT data comprises OpsCenterUsers(vx) users and certificates.

3. Copy the XML file that you have created in the earlier step to the new 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.

4. Steps to be carried out on the new host where you want to install the latest version of OpsCenter

   Install the latest version of OpsCenter on the new host.

5. Stop all OpsCenter services on the new host.

6. 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:

   http://www.veritas.com/docs/DOC5808

7. Restore the database that you have backed up earlier.

8. Update the following information from the db.conf file:

   • If you are using the port that is different than the default one, update the value of the db.port parameter as follows:

     db.port=13786

   • Set the db.serviceName parameter to the name of the target host as follows:

     db.serviceName=TargetHostName

9. Upgrade the database using dbUpgrade command.

   Run the following command:

   Windows	dbUpgrade.bat install <old_version_number> <new_version_number> For example: <OpsCenterInstallLocation>\OpsCenter\server\bin\dbUpgrade.bat install 8.0 8.1
   UNIX	dbUpgrade.sh install <old_version_number> <new_version_number> For example: <OpsCenterInstallLocation>/SYMCOpsCenterServer/bin/dbUpgrade.sh install 8.0 8.1

10. Check the progress of database upgrade in the upgrade logs at the following location:

    Windows	<OpsCenterInstallLocation>\ OpsCenter\server\db\log
    Unix	<OpsCenterInstallLocation>/SYMCOpsCenterServer/db/log

11. Import old authentication or AT data into the new OpsCenter server host.

    Make sure that you have copied the export XML file that you have created on the existing OpsCenter server host to the new OpsCenter server host.

    Run the following command:

    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 For example: atutil import -p "password" -f \temp\userdata.xml -z C:Program Files\Symantec\OpsCenter\server\authbroker\data - 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 For example: atutil import -p "password" -f /temp/userdata.xml -z /opt/SYMCOpsCenterServer/authbroker/data - 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.

12. Start OpsCenter services.