NetBackup for Lotus Notes backup types
In a policy's schedule you define the type of backups you want to perform.
Table: Description of NetBackup for Lotus Notes backup types
Type of backup | Description |
|---|
Full backup
| Backs up all the Lotus databases 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 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 reuse after they are successfully backed up. The Domino server handles the actual recycling of transaction log extents.
|
Differential Incremental backup
| The type of 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 reuse when the backup complets successfully.
|
Cumulative Incremental backup
| The type of 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 reuse when the backup is completed.
|
User backup
|
A user backup is identical to a full backup with one exception. Transaction log extents are not marked as ready to be recycled after they are successfully backed up. Because transaction log extents are not reused, a user backup is similar to a snapshot of the databases at a given point in time. The content of ongoing full and incremental backups is not impacted.
A user backup is not automatically scheduled and must be initiated on the target client machine.
You may also want to create a separate policy for User Backup schedule types. This configuration lets you easily separate user-directed and scheduled backups. If you decide to create a separate policy for user backups, the considerations are similar to those for automatic backups. One difference is that you do not need to indicate any backup selections because users select the files.
|
