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
- 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
- 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 configuring data collection for NetBackup
- About the Breakup Jobs option
- Viewing primary server details and data collection status
- About configuring data collection for NetBackup
- Managing OpsCenter views
- About OpsCenter views
- About managing OpsCenter views
- Managing static views
- Managing dynamic 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 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. Attributes of NetBackup data
- Appendix B. Man pages for CLIs
- Appendix C. Creating views using CSV, TSV, and XML files
- Appendix D. Error messages in OpsCenter
Moving the OpsCenter database and database logs to a different hard disk
To improve OpsCenter performance, OpsCenter database files and the log files that are associated with the OpsCenter database should be stored on separate hard disks. You can store the OpsCenter database files on one hard disk and the log files on another hard disk.
It is not recommended to store the database files on the hard disk that contains your operating system files.
You can specify a custom location (non-default location) for the OpsCenter database during OpsCenter installation. The default location for the OpsCenter database can also be changed after OpsCenter has been installed.
Use the following procedures to move the OpsCenter database and log files to a different hard disk. The first two procedures are for moving the OpsCenter database files on Windows or UNIX. The last two procedures are for moving the database log files.
To move the OpsCenter database to a different hard disk on Windows
- Stop all OpsCenter services. Enter the following command:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop
- Open the
databases.conf
file with a text editor like notepad from the following directory:INSTALL_PATH\OpsCenter\server\db\conf
This file has the following contents:
"INSTALL_PATH\OpsCenter\server\db\data\vxpmdb.db"
This path specifies the default location of the OpsCenter database.
- To move the database to a custom location like E:\Database, replace the contents of the file with the following:
"E:\Database\vxpmdb.db"
Caution:
Make sure that you specify the database path in double quotes. The directories in the specified path and also the
databases.conf
file should not contain any special characters like %, ~, !, @, $, &, ^, #, and so on. For example, do not specify a path likeE:\Database%
. Commenting out the path is also not allowed. For example, the following string is not allowed in thedatabases.conf
file:#"E:\Database\vxpmdb.db"
If you want to change the database path, you should replace the original path with the new one instead of commenting out the original path.
If the
databases.conf
file contains characters or strings other than the database location, the database upgrade will not succeed.If you need a reference, you can create a backup copy of the original
databases.conf
file with a different file name.Save the
databases.conf
file. - Copy the database files to the new location. Copy
vxpmdb.db
,symcOpscache.db
,symcopsscratchdb.db
, andsymcsearchdb.db
fromINSTALL_PATH\OpsCenter\server\db\data
to a location like E:\Database. - Restart all OpsCenter server services.
To restart all OpsCenter services, enter the following command:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start
You should run and monitor OpsCenter for a certain period after moving the database. If OpsCenter works as expected, you can delete
vxpmdb.db
,symcOpscache.db
,symcopsscratchdb.db
, andsymcsearchdb.db
from the default location (INSTALL_PATH\OpsCenter\server\db\data
).
To move the OpsCenter database to a different hard disk on UNIX
- Stop all OpsCenter server processes. Enter the following command:
<INSTALL_PATH>/SYMCOpsCenterServer/bin/opsadmin.sh stop
- The default location of the OpsCenter database is
<INSTALL_PATH>/SYMCOpsCenterServer/db/data
.Back up the OpsCenter database (
<INSTALL_PATH>/SYMCOpsCenterServer/db/data
) to some other location. Enter the following command:cp - R <INSTALL_PATH>/SYMCOpsCenterServer/db/data /backup/data
- To move the database to a custom location like
/usr/mydata
, always create a new directory named OpsCenterServer inside/usr/mydata
by entering the following command:mkdir -p /usr/mydata/OpsCenterServer
It is recommended that when you move the OpsCenter database to a custom location on UNIX, the database must be saved in a directory named OpsCenterServer inside the custom location: /CUSTOM_LOCATION/OpsCenterServer.
- To move the database to a custom location like
/usr/mydata/OpsCenterServer
, enter the following command:mv <INSTALL_PATH>/SYMCOpsCenterServer/db/data/* /usr/mydata/OpsCenterServer
- Remove the symbolic link that exists for the OpsCenter database. Enter the following command:
unlink <INSTALL_PATH>/SYMCOpsCenterServer/db/data
- Create a symbolic link to
/usr/mydata/OpsCenterServer
in<INSTALL_PATH>/SYMCOpsCenterServer/db/data
. To create a symbolic link, enter the following command:ln -s /usr/mydata/OpsCenterServer <INSTALL_PATH>/SYMCOpsCenterServer/db/data
- Restart all OpsCenter server processes by entering the following command:
<INSTALL_PATH>/SYMCOpsCenterServer/bin/opsadmin.sh start
You should run and monitor OpsCenter for a certain period after moving the database. If OpsCenter works as expected, you can delete
vxpmdb.db
andsymcOpscache.db
from /backup/data.
To move the database log files to a different hard disk on Windows
- Stop all OpsCenter server services. Enter the following command:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop
- Navigate to the following location for 32-bit and 64-bit systems respectively:
INSTALL_PATH\OpsCenter\server\db\WIN32
INSTALL_PATH\OpsCenter\server\db\WIN64
Enter the following commands:
dblog -t directory_path\vxpmdb.log database_path\vxpmdb.db
where directory_path is the path where you want to store the database logs and database_path is the path where your database is located.
This command moves the log file that is associated with the OpsCenter database to the new directory (directory_path). It is recommended to use vxpmdb.log as the name of the log file.
- Restart all OpsCenter server services.
To restart all OpsCenter services, enter the following command:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start
To move the database log files to a different hard disk on UNIX
- Stop all OpsCenter server processes. Enter the following command:
<INSTALL_PATH>/SYMCOpsCenterServer/bin/opsadmin.sh stop
- Set the path of the LD_LIBRARY_PATH variable in the following manner:
LD_LIBRARY_PATH=<INSTALL_PATH>/SYMCOpsCenterServer/db/ lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH
- Navigate to the following location:
<INSTALL_PATH>/SYMCOpsCenterServer/db/bin
Enter the following commands:
./dblog -t directory_path/vxpmdb.log database_path/vxpmdb.db
where directory_path is the path where you want to store your database log file and database_path is the path where the OpsCenter database is located.
This command moves the log file that is associated with the OpsCenter database to the new directory (directory_path). It is recommended to use vxpmdb.log as the name of the log file.
- Restart all OpsCenter server processes by entering the following command:
<INSTALL_PATH>/SYMCOpsCenterServer/bin/opsadmin.sh start