Veritas NetBackup™ OpsCenter Performance and Tuning Guide
- Overview
- About OpsCenter configuration
- About OpsCenter performance and tuning
- Sizing considerations
- Sizing guidelines
- About tuning OpsCenter for increased performance
- About performance tuning guidelines
- About adding NetBackup Master Servers to OpsCenter
- About using a web browser to access OpsCenter
- 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
- About purging data periodically
- Moving OpsCenter server to a different computer
- OpsCenter best practices
About OpsCenter Server on a virtual machine
This section talks about the OpsCenter Server configuration on a virtual machine.
For better performance, ensure the following before setting up an OpsCenter Server on a virtual machine.
Dedicate CPUs and RAM to the OpsCenter VM based on the recommendations in this document.
See Sizing guidelines.
Ensure that ESX on which OpsCenter VM is running is not overloaded in terms of CPU, memory, and disk space usage.
Select optimum CPU Power Management Policy based on your requirement.
VMware snapshots increase the I/O heavily. Try to avoid snapshots.
Align file system (VMFS) partitions to 1MB.
Refrain from installing other Java applications on OpsCenter VM.
Install the OpsCenter database on a drive that is different from OpsCenter Server host. This drive should be on datastore, which is on dedicated LUN.
Make sure that OpsCenter database does not reside on a datastore where Guest OS swap and VM swap reside.
To reduce I/O, save the OpsCenter debug log files on a drive other than the one where the database is installed.
The following sections provide more information about OpsCenter Server configuration in a virtual environment.
See Physical versus virtual configuration for OpsCenter Server.
See Guidelines on the OpsCenter VM parameters.
See About VM settings and % gains during OpsCenter report generation.