Veritas NetBackup™ OpsCenter Performance and Tuning Guide
- 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
- Installation and upgrade best practices
- OpsCenter database best practices
- Backup products best practices
Installation and upgrade best practices
Following are the best practices for installing and upgrading OpsCenter:
Veritas recommends that, especially in large backup environments (more than 1000 backup jobs a day), you install OpsCenter Server on a separate standalone host than on the backup product host or OpsCenter Agent hosts
Veritas recommends that you install OpsCenter Server on a system having at least 8 GB RAM. System configuration largely depends on the number of backup products to be monitored, alerts, or jobs that are generated per day and so on.
If 8.3 file name creation is disabled on a Windows host, it is recommended that you enable it and restart the Windows host before installing or upgrading OpsCenter components.
See the following link for details:
Veritas recommends that you install OpsCenter Agent on a host that is different from the OpsCenter Server host.
Veritas recommends that you deploy the OpsCenter Agent geographically closer to the managed server.
In a clustered environment, first install OpsCenter Server on the active node and then on the passive nodes. Note that OpsCenter supports only Windows VCS clusters.
Ensure that you install OpsCenter Server, Agent, and View Builder of the same versions.
To achieve optimum performance, configure the OpsCenter log files to be created on a physical disk that is different from where the OpsCenter Server and operating system (OS) files are installed.
If you have the database transaction logs and databases at different locations, move the logs to the database location before upgrade.
Ensure that the available disk space is at least three times the database size.
This recommendation for the available disk space is based on the existing database size. It does not take the future growth of the database into account.
Back up the OpsCenter database before performing changes like database defragmentation, upgrade, applying Emergency Engineering binaries (EEB), object merge and so on.
Refer to the 'Backing up the OpsCenter database' section in the OpsCenter Administrator's Guide.