Create policy

Information about IBM Storage Protect policy settings is provided.

Although Data Protection for HCL Domino operates in ways similar to other IBM Storage Protect clients, it is unlike regular IBM Storage Protect clients in that it does not always store complete replacements for objects on the IBM Storage Protect server. When a database file is backed up, it is a complete backup of the entire database and becomes a new backup version of that database. When archival logging is being used on the Domino server, then each archived transaction log file contains changes to one or more logged databases over time. Each of these transaction log files has a unique name so there are never multiple versions of the same transaction log file. Because of this difference, Data Protection for HCL Domino requires special IBM Storage Protect policy settings.

How Data Protection for HCL Domino has an impact on policy (NSF databases)

Data Protection for HCL Domino has an impact on IBM Storage Protect backup policy for NSF databases in these ways:

Regular use of the Domdsmc Inactivatelogs command deactivates the archived transaction log files when all NSF databases that would require that file for a complete recovery are inactive. Ensure to set the retention period for inactive transaction log files to be equal to, or greater than the database backup objects. Files are available when any inactive database file that might need them is available. A point in time recovery of an inactive database backup version can be accomplished. The same management class for the transaction log files for the database files is used.
It is possible to have multiple versions of the same transaction log file under certain circumstances. Data Protection for HCL Domino and the Domino Server provide the capability to archive the currently filling transaction log. Thus, the same transaction log file can be backed up multiple times (while it is filling and again when it is full). If the Domino server is stopped abnormally after transaction log files are archived but not yet reused by the Domino server, those transaction log files can be archived. These files might be unchanged. As a result, version limit parameters for the management class that is used for transaction log files must be set to ensure that extra versions of a transaction log file are purged from the backup storage pools.
To optimize the recovery process, use collocation for the file space that contains the transaction log files if they are stored on sequential media on the IBM Storage Protect server. The transaction log files are stored in a separate file space from the database files on the IBM Storage Protect server.

How Data Protection for HCL Domino has an impact on policy (DB2 enabled Notes databases)

Data Protection for HCL Domino has an impact on IBM Storage Protect backup policy for DB2 enabled Notes databases in these ways:

Use the Domdsmc DB2INActivateobjs command regularly to deactivate the archived transaction log files. It backs up objects when all DB2 enabled Notes databases that would require those files for a complete recovery are inactive. Therefore, be sure to set the retention period for inactive transaction log files to be equal to or greater than the database backup objects. The retention period ensures that the files are available when any inactive database file that might need them is available. A point in time recovery of an inactive database backup can be accomplished with the same management class for the transaction log files. The same is true when the same backup objects for the database files are used.
To optimize the recovery process, use collocation for the file space that contains the transaction log files if they are stored on sequential media on the IBM Storage Protect server. The transaction log files are stored in a separate file space from the database files on the IBM Storage Protect server.

Policy settings

Use default values for the following Backup Copy Group parameters because they are not applicable to Data Protection for HCL Domino:

frequency
mode
serialization

Define a separate policy domain where the default management class has the settings that are required for your Domino backup data. Register all Domino IBM Storage Protect nodes to that domain. When you are defining a new management class within an existing policy domain that is not the default management class for that domain, you must add an include statement. The include statement in the Data Protection for HCL Dominoinclude-exclude options file binds all objects to that management class. For example: include * mcname.

See your IBM Storage Protect administrator or the appropriate IBM Storage Protect Administrator Guide for your server, for more information about defining or updating policy domains, and copy groups.

Data Protection for HCL Domino stores all objects as backup objects on IBM Storage Protect so an Archive Copy Group is not required, although it can exist.

All database backup objects are complete file backups so normal version controls available through IBM Storage Protect server policies apply. Set the verdeleted, verexists, retonly, and retextra parameters of the Backup Copy Group according to your needs for the number of backup versions to be kept and the retention period of these backup versions.