About catalog backup parent and child jobs on Windows
Normally, a hot, online catalog backup consists of one parent job and two or more child jobs. Events for these jobs appear in the dbm log.
An overview of the hot catalog backup process consists of the following process:
Make a temporary copy of database files to a staging directory by typing the following command:
Once the copy is made, NetBackup can back up the catalog files.
A child job backs up files in a single stream as follows:
A second child job begins the image catalog backup.
The backup of any 5.x media server appears as a separate job.
If BMR is installed and a remote EMM server is in use, the backup of the EMM server appears as a separate job.
Transaction logs are truncated after a successful full or incremental backup.
If the transaction logs are manually changed or deleted, a hole could exist in the recovery.
The child job for the relational database backup is normally run on the master server. The master server is the default location for NBDB and the required location for BMRDB.
If NBDB was moved to a media server, the child job runs on the media server. In this case, additional logging for the job appears in the admin log on the media server.
If NBDB was moved to a media server and BMRDB is installed on the master server, two child jobs exist for the relational database backup portion of the online, hot catalog backup. One on the media server for NBDB and one on the master server for BMRDB.
See About online, hot catalog backups on Windows
See Commands for backing up and recovering the relational databases on Windows