Forum Discussion

luisvidal's avatar
luisvidal
Level 5
13 years ago
Solved

Does a Full or Incremental Backup change the DBIID for a Notes DB?

Hi gang,

 

Trying to review my Lotus Notes agent backups, and I have a question that I don't fully understand and wanted to get your feedback on. NBU Agent for Notes, backs up a database (NSF) when its DBIID changes. Do any of these backups change the DBIID on the databases to register that the DB has already been backed up?

 

7.1.x and Earlier
Agents
Backing Up
Backup and Recovery
NetBackup
  • Will_Restore's avatar
    Will_Restore
    13 years ago

    DBIID is set and changed by Lotus Notes and not by NetBackup.  

     

    Article URL http://www.symantec.com/docs/HOWTO47928

    describes NetBackup for Lotus Notes backup types

     

     

    Full backup

    This backup type is used to back up all the Lotusdatabases that are identified in the Backup Selections list. Available transaction logs extents are also backed up if the BACKUP_TRANSACTION_LOGS directive is specified in the Backup Selections list. All transaction log extents are backed up that are identified as available for backup by the Domino server. The inactive transaction log extents are marked as ready to be recycled after they are successfully backed up. The Domino server handles the actual recycling of transaction log extents.

    Differential Incremental backup

    The type of Lotus Notes database affects how NetBackup performs a differential incremental backup, as follows:

    • Unlogged databases or local databases

      Backs up all unlogged databases or local databases that were modified since the last full or incremental backup. The last modification date, not the time stamp or date stamp of the database file, determines the time the database was last modified.

    • Logged databases (archival-style logging enabled)

      Backs up only those logged databases that were assigned a new DBIID since the last full or incremental backup.

    • Logged databases (circular-style and linear-style logging enabled)

      Backs up all logged databases that were modified or assigned a new DBIID since the last full or incremental backup. The last modification date, not the time stamp or date stamp of the database file, determines the time the database was last modified.

    • Transaction logs

      Backs up all transaction log extents that are identified as available for backup by the Domino server. The inactive transaction log extents are marked as ready to be recycled when the backup complets successfully.

    See About supported Lotus Notes database configurations

    Cumulative Incremental backup

    The type of Lotus Notes database that is encountered affects how NetBackup performs a cumulative incremental backup, as follows;

    • Unlogged databases or local databases

      Backs up all unlogged databases or local databases that were modified since the last full backup. The last modification date, not the time stamp or date stamp of the database file, determines the time the database was last modified.

    • Logged databases (archival-style logging enabled)

      Backs up only those logged databases that were assigned a new DBIID since the last full backup.

    • Logged databases (circular-style and linear-style logging enabled)

      Backs up all logged databases that were modified or have been assigned a new DBIID since the last full backup. The last modification date, not the time stamp or date stamp of the database file, determines the time the database was last modified.

    • Transaction logs

      Backs up all transaction log extents that are identified as available for backup by the Domino server. The transaction log extents are not marked as ready to be recycled when the backup is completed.

     

  • Will_Restore's avatar
    Will_Restore
    Level 6
    13 years ago

    DBIID is set and changed by Lotus Notes and not by NetBackup.  

     

    Article URL http://www.symantec.com/docs/HOWTO47928

    describes NetBackup for Lotus Notes backup types

     

     

    Full backup

    This backup type is used to back up all the Lotusdatabases that are identified in the Backup Selections list. Available transaction logs extents are also backed up if the BACKUP_TRANSACTION_LOGS directive is specified in the Backup Selections list. All transaction log extents are backed up that are identified as available for backup by the Domino server. The inactive transaction log extents are marked as ready to be recycled after they are successfully backed up. The Domino server handles the actual recycling of transaction log extents.

    Differential Incremental backup

    The type of Lotus Notes database affects how NetBackup performs a differential incremental backup, as follows:

    • Unlogged databases or local databases

      Backs up all unlogged databases or local databases that were modified since the last full or incremental backup. The last modification date, not the time stamp or date stamp of the database file, determines the time the database was last modified.

    • Logged databases (archival-style logging enabled)

      Backs up only those logged databases that were assigned a new DBIID since the last full or incremental backup.

    • Logged databases (circular-style and linear-style logging enabled)

      Backs up all logged databases that were modified or assigned a new DBIID since the last full or incremental backup. The last modification date, not the time stamp or date stamp of the database file, determines the time the database was last modified.

    • Transaction logs

      Backs up all transaction log extents that are identified as available for backup by the Domino server. The inactive transaction log extents are marked as ready to be recycled when the backup complets successfully.

    See About supported Lotus Notes database configurations

    Cumulative Incremental backup

    The type of Lotus Notes database that is encountered affects how NetBackup performs a cumulative incremental backup, as follows;

    • Unlogged databases or local databases

      Backs up all unlogged databases or local databases that were modified since the last full backup. The last modification date, not the time stamp or date stamp of the database file, determines the time the database was last modified.

    • Logged databases (archival-style logging enabled)

      Backs up only those logged databases that were assigned a new DBIID since the last full backup.

    • Logged databases (circular-style and linear-style logging enabled)

      Backs up all logged databases that were modified or have been assigned a new DBIID since the last full backup. The last modification date, not the time stamp or date stamp of the database file, determines the time the database was last modified.

    • Transaction logs

      Backs up all transaction log extents that are identified as available for backup by the Domino server. The transaction log extents are not marked as ready to be recycled when the backup is completed.