Veritas NetBackup™ Logging Reference Guide
- Using logs
- About unified logging
- About legacy logging
- About global logging levels
- Troubleshooting error messages in the NetBackup Administration Console
- Backup process and logging
- Media and device processes and logging
- Restore process and logging
- Advanced Backup and Restore Features
- Storage logging
- NetBackup Deduplication logging
- OpenStorage Technology (OST) logging
- Storage lifecycle policy (SLP) and Auto Image Replication (A.I.R.) logging
- Snapshot technologies
- Locating logs
- Java-based administration console logging
Hot catalog backup
The hot catalog backup is a policy-based backup, with all of the scheduling flexibility of a regular backup policy. This backup type is designed for highly active NetBackup environments where other backup activity usually takes place.
You can use an option in the NetBackup Administration Console to start a manual backup of the NetBackup catalogs. Or, you can configure a NetBackup policy to automatically back up its catalogs.
Figure: Hot catalog backup process shows the hot catalog backup process.
NetBackup initiates the following hot catalog backup jobs:
A parent job that is started manually by the administrator or by a catalog backup policy schedule.
A child job that copies NBDB to the staging directory and validates the information.
The SQL Anywhere files database agent makes an online copy of the relational database files to /usr/openv/db/staging.
A child job that backs up the NBDB database files.
After the files are in the staging area, the SQL Anywhere database agent backs them up in the same manner as an ordinary backup.
A child job that backs up the NetBackup database files (all files in /usr/openv/netbackup/db).
NetBackup creates the disaster recovery file, and emails it to the administrator if the email option was selected in the policy.
Consult the following logs for messages on hot catalog backup:
bpdbm, bpbkar, bpbrm, bpcd, bpbackup, bprd
For messages pertaining only to the relational database files, see the EMM server.log file and the bpdbm log file in the following directories: