Modify button

Click the Modify button to select a transaction mode and determine when the transaction log is automatically truncated outside of the catalog backup process.

This option affects all databases managed by the database server (NBDB and BMRDB). The database server must be restarted in order for the transaction log mode change to take effect.

Full (default)

With Full selected, the transaction log is truncated automatically after a successful online (hot) or offline (cold) catalog backup. All of the database files are included in the backup. (NBDB, NBDB.db, EMM_DATA.db, EMM_INDEX.db, NBDB.log.)

The differential incremental schedule for the online (hot) catalog backup includes only the transaction log file.

To recover using a full and an incremental backup, all of the database files are restored and the transaction logs are applied one at a time in order.

Partial

With Partial selected, all schedules used for the hot catalog backup policies include backups of all of the relational database files.

Partial mode forces a deletion of the transaction log whenever a database checkpoint occurs.

In Partial mode, the online (hot) catalog backup must always be a full backup and all incremental schedules are automatically converted to full schedules by NetBackup. The cold catalog backup is always a full backup.