Veritas NetBackup™ OpsCenter Administrator's Guide
- Overview of NetBackup OpsCenter
- About OpsCenter
- About OpsCenter components
- About starting the OpsCenter console
- About OpsCenter console components
- About the View pane
- Sizing the Content pane
- About using tables
- Installing OpsCenter
- About planning an OpsCenter installation
- About the OpsCenter licensing model
- Managed NetBackup master server considerations
- About designing your OpsCenter Server
- About planning an OpsCenter Agent deployment
- Installing OpsCenter on Windows and UNIX
- About OpsCenter upgrade on Windows and UNIX
- About post-installation tasks
- About uninstalling OpsCenter on Windows and UNIX
- About clustering OpsCenter
- About planning an OpsCenter installation
- Getting started with OpsCenter
- Administering OpsCenter
- About the services and processes used by OpsCenter
- OpsCenter server scripts on Windows and UNIX
- About OpsCenter database administration
- About backup and restore of OpsCenter and OpsCenter Analytics
- About communication ports and firewall considerations in OpsCenter
- About OpsCenter log files
- Understanding OpsCenter settings
- Setting user preferences
- About managing licenses
- Configuring the data purge period on the OpsCenter Server
- Configuring SMTP server settings for OpsCenter
- Adding host aliases in OpsCenter
- Merging objects (hosts) in OpsCenter
- Modifying tape library information in OpsCenter
- Copying a user profile in OpsCenter
- Setting report export location in OpsCenter
- About managing Object Types in OpsCenter
- About managing OpsCenter users
- About adding AD / LDAP user groups in OpsCenter
- About managing recipients in OpsCenter
- About managing cost analysis and chargeback for OpsCenter Analytics
- Understanding data collection
- About data collection in OpsCenter
- About managing OpsCenter Agents
- About managing OpsCenter Data Collectors
- About configuring data collection for NetBackup
- About the Breakup Jobs option
- Viewing master server details and data collection status
- Collecting data from PureDisk
- Managing OpsCenter views
- About OpsCenter views
- About managing OpsCenter views
- View filters in OpsCenter
- Monitoring NetBackup using OpsCenter
- Controlling the scope of Monitor views
- About monitoring NetBackup using the Overview tab
- About monitoring NetBackup jobs
- Monitor > Services view
- About monitoring Audit Trails
- Managing NetBackup using OpsCenter
- About managing alert policies
- About creating (or changing) an alert policy
- About managing NetBackup storage
- About managing NetBackup devices
- About Operational Restore and Guided Recovery operations
- About Operational Restores from OpsCenter
- About OpsCenter Guided Recovery
- Troubleshooting Guided Recovery
- About managing NetBackup Hosts
- About managing NetBackup Deployment Analysis
- Data compilation for the Capacity License report
- Generating a Capacity Licensing report
- Supporting Replication Director in OpsCenter
- Understanding and configuring OpsCenter alerts
- About using SNMP
- About using SNMP
- Reporting in OpsCenter
- About OpsCenter reports
- Report Templates in OpsCenter
- About managing reports in OpsCenter
- Creating a custom report in OpsCenter
- About managing My Reports
- About managing My Dashboard
- About managing reports folders in OpsCenter
- About managing report schedules in OpsCenter
- About managing time schedules in OpsCenter
- Appendix A. Additional information on PureDisk data collection
- Appendix B. Attributes of NetBackup data
- Appendix C. Man pages for CLIs
- Appendix D. Creating views using CSV, TSV, and XML files
- Appendix E. Error messages in OpsCenter
Moving OpsCenter server because of constraints in upgrade
This section provides the procedure to move the existing OpsCenter server to a different machine where you want to install the latest version of OpsCenter. The following example explains the scenario in detail:
You have OpsCenter setup that you want to upgrade to the latest version. If OpsCenter is installed on a platform that is not supported by the latest version of OpsCenter, you need to move the existing OpsCenter server to a different machine that has a supported platform.
You need to carry out a few steps on the existing OpsCenter server host and a few on the new host.
To move the existing OpsCenter server to a different machine
- 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
). - 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.
See Exporting authentication settings.
See About OpsCenter AT.
See About OpsCenter upgrade scenarios with respect to OpsCenter AT.
- 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.
- 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.
- Stop all OpsCenter services on the new host.
- 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.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
- 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
- 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
- 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.
- Start OpsCenter services.