This agent has the following unique functionality. The Lotus Notes Database
iDataAgent backs up very specific sets
of data depending upon what type of operation you choose. Review the following to
understand exactly what will be backed up when you perform a backup job at the indicated
level:
The job that is performed when you select a full or incremental backup depends
on the type of subclient that you are backing up:
Default subclient
When you perform a full backup job for the default subclient, the system performs
a discover on the partition and executes a full backup of:
all the databases that are already configured within the subclient.
unconfigured databases within the partition (discovered).
When an incremental backup job is performed for the default subclient, the system
performs a discover of the partition, and executes a backup of:
unconfigured databases (discovered).
any databases manually added since the last backup.
any previously backed up databases where the DBIID has changed since the
last backup.
non-logged databases that have been modified since the last backup.
When you add new databases to a default Subclient, the auto discovery finds
the new databases and backs them up as Full.
User-defined subclients
When a full backup job is performed for a user-defined subclient, the system
executes a full backup of:
that subclient's databases.
When an incremental backup job is performed for a user-defined subclient, any
database that was not part of this subclient on the last backup (incremental or
full) will get backed up:
any databases manually added since the last backup.
any previously backed up databases where the DBIID has changed since the
last backup.
non-logged databases that have been modified since the last backup.
When you add new database(s) to the user-defined subclients that are already
created for Lotus Notes iDataAgent,
the system performs a full backup for newly added database(s).
Transaction log subclient
To use the transaction log subclient you must have
Domino Server configured in archive logging style.
The Lotus Notes iDataAgent creates
a transaction log subclient that handles backing up transaction logs for all databases
within the partition. You can only perform incremental backup jobs for a transaction
log subclient. When you perform an incremental backup, the system backs up all full
log extents. For Domino Server versions 5.0.4 and above, the active log extent is
backed up as well.
Any changes in the database(s) is logged and backed up by the Transaction log
subclient.
When a full backup job is performed at the partition level, the following actions
take place:
New databases that are not yet configured for Backup are added to the default
subclient.
All databases that are already part of this partition are backed up.
After a full backup, each subclient in the partition
will be represented in the Backup History. Full backups backup databases.
Full backups do not backup the transaction log subclient.
When an incremental backup job is performed for a partition, the following actions
take place:
New databases that are not yet configured for Backup are added to the default
subclient.
Any database that was not part of the partition on the last backup (incremental
or full) is backed up.
Any previously backed up databases where the DBIID has changed since the
last backup are backed up.
Non-logged databases that have been modified since the last backup are backed
up.
This agent has the following unique functionality. The Lotus Notes Document
iDataAgent backs up very specific sets
of data depending upon what type of operation you choose. Review the following to
understand exactly what will be backed up when you perform a backup job at the indicated
level:
The jobs that are performed when you select a full, incremental, differential
or synthetic full backup depend on the type of subclient that you are backing up:
When you perform a full backup job for the default subclient, the following
takes place:
The software performs a discover on the partition and executes a full backup
of any new databases.
The software performs a full backup of the databases that already exist
within the subclient.
When you perform an incremental backup job for the default subclient, the following
takes place:
The software performs a discover of the partition, and executes a full backup
of any new databases.
The software performs a full backup for any databases that were manually
added since the last backup.
The software performs a backup for any new or changed documents of previously
backed up databases of the subclient.
When you perform a differential backup job for the default subclient, the following
takes place:
The software performs a discover of the partition, and executes a full backup
of any new databases.
The software performs a full backup for any databases that were manually
added since the last backup.
The software performs a backup for any new or changed documents of existing
databases since the last full backup.
When you perform a synthetic full backup job for the default subclient, the following
takes place:
The software creates a full image of the data in the subclient by overlaying
existing incremental and/or differential backups onto the latest full
backup.
No new databases are discovered or added to the backup.
When you perform a full backup job for a user-defined subclient, the following
takes place:
The software executes a full backup of its databases.
When you perform an incremental backup job for a user-defined subclient, the
following takes place:
Any new or changed documents of existing databases that were not part of
this subclient on the last backup are backed up.
The software performs a full backup for any databases that were manually
added since the last backup.
When you perform a differential backup job for a user-defined subclient, the
following takes place:
Any new or changed documents of the existing databases that were not part
of this subclient on the last full backup are backed up.
The software performs a full backup for any databases that were manually
added since the last backup.
When you perform a synthetic full backup job for the default subclient, the following
takes place:
The software creates a full image of the data in the subclient by overlaying
existing incremental and/or differential backups onto the latest full backup.
No new databases are discovered or added to the backup.
Using a Backup Set backup job is an efficient means to run a specified backup
type in one operation on all the subclients of the backup set.
When a full backup job is performed for a backup set, the following actions take
place:
New databases that are not yet configured for Backup are added to the default
subclient.
All databases that are part of this backup set are backed up.
When an incremental backup job is performed for a backup set, the following actions
take place:
New databases that are not yet configured for Backup are added to the default
subclient.
Any database that was not part of this backup set on the last backup will
get backed up.
When a differential backup job is performed for a backup set, the following actions
take place:
New databases that are not yet configured for Backup are added to the default
subclient.
Any database that was not part of this backup set on the last full backup
will get backed up.
When a synthetic full backup job is performed for a backup set, the following
actions take place:
The software creates a full image of the data in the backup set by overlaying
existing incremental and/or differential backups onto the latest full
backup.
No new databases are discovered or added to the backup.
Before performing any backup procedures for this agent, review the following
information:
Best Practices for Domino Attachment and Object Service (DAOS) Backups
Consider the following when performing backups of Domino servers utilizing
DAOS:
If deferred deletion is configured, the interval time should be set to a
period longer than the period between backups. For example, if backups are
performed once every two weeks, the deferred deletion interval should be set
to 15 days or longer. This setting can be specified in the server document's
Defer deletion of DAOS objects in n days option.
The following files are not backed up by the Lotus Notes iDataAgents;
however, they can be backed up by the File System iDataAgent:
DAOS.CFG
all NLO files
DAOS links are not preserved during Lotus Notes Document iDataAgent
restores. To reintroduce these links, the following compact operation must
be performed:
load compact -C -daos on test.nsf
Best Practices for Transaction Logging
Keep the transaction log on a separate partition or drive.
Use the largest log drive possible or at least 4 to 5 times larger
than your observed daily usage to safeguard against media contention
situations.
Make sure the speed of logs being archived is faster than that of new
logs being created. Otherwise, the total log size will increase over
time.
Enable transaction logging in ARCHIVE mode for Notes Database
database-level backups. Although the Lotus Notes Database
iDataAgent allows you to install,
backup and restore when the transaction logging setting for Domino server is
ARCHIVE , CIRCULAR, DISABLED or (LINEAR, R6 only), it is highly recommended
that you make use of transaction logging in ARCHIVE mode for Notes Database
level backups. Transaction logging in ARCHIVE mode provides for the best
possibilities for data recovery over ALL other modes.
Be aware that when not using ARCHIVE mode:
The backup data size of incremental backups could be close to full
backups, and point-in-time restore is not always possible, and
When CIRCULAR (LINEAR in R6) logging is used, transaction log
backups are not possible, and point-in-time restore is possible only if
logs are not overwritten.