About the catalog backup process
Normally, a 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 catalog backup process consists of the following process:
Creates a staging directory where the command can store the temporary copies:
On Windows: install_path\NetBackupDB\staging
On UNIX: /usr/openv/db/staging
Once the copy is made, NetBackup can back up the catalog files.
A child job backs up files in a single stream as follows:
Configuration files (server.conf, database.conf, vxdbms.conf)
Database files
BMR_DATA.db
BMRDB.db
BMRDB.log
BMR_INDEX.db
DARS_DATA.db
DARS_INDEX.db
DBM_DATA.db
DBM_INDEX.db
EMM_DATA.db
EMM_INDEX.db
JOBD_DATA.db
NBAZDB.db
NBAZDB.db.template
NBAZDB.log
NBDB.db
NBDB.log
vxdbms.conf
If BMR was installed
A second child job begins the image catalog backup.
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 primary server. The primary 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 primary server, two child jobs exist for the relational database backup portion of the catalog backup. One on the media server for NBDB and one on the primary server for BMRDB.