The following items are notes about catalog policy schedules:

• The following schedules are supported in the online, hot catalog backup policy type:

  • Full

  • Differential incremental (depends on a full schedule)

  • Cumulative incremental

  • Session-based differential incremental

  • Session-based cumulative incremental

• Symantec recommends that only one catalog backup policy be configured.

• The media server that is used for catalog backups must be at the same NetBackup version as the master server.

• The incremental schedule depends on a full schedule.

• The least frequent schedule runs if many schedules are due at the same time.

• One catalog backup policy can contain multiple session-based incremental schedules:

  • If one is cumulative and the others are differential, the cumulative runs when the backup session ends.

  • If all are cumulative or all are differential, the first schedule that is found runs when the backup session ends.

• The queued scheduled catalog backup is skipped if a catalog backup job from the same policy is running.

• Session end means that no jobs are running. (This calculation does not include catalog backup jobs.)

• The Vault catalog backup is run whenever triggered from Vault, regardless of whether a catalog backup job is running from the same policy.

• When an online catalog backup is run, it generates three jobs: a parent job, a child job for NetBackup relational database tables, and a child job for catalog images and configuration data. The child jobs contain the actual backed up data. Consider both child jobs to duplicate, verify, or expire the backup.

  Note:

  Additional child catalog jobs are created for the BMR database if a remote EMM server is configured.