More configuration options

Edit online

Customize your Data Protection for HCL Domino environment by configuring extra options for server communication, compression, encryption, and deduplication.

COMMRESTARTDURATION

Use COMMRESTARTDURATION to specify the total number of minutes that the server will attempt to restart a session after a communication failure. The range of values is 1 - 9999 and the default is 60. This option must be set high on a network that is unreliable.

You can specify this option in the Data Protection for HCL Domino preferences file.

COMMRESTARTINTERVAL

Use COMMRESTARTINTERVAL to specify how many seconds the server will wait before it attempts to restart a session after a communication failure. The range of values is one through 9999 and the default is 15. The restart interval setting means that the network is not overloaded with restart requests. The COMMRESTARTINTERVAL time must always be less than or equal to the COMMRESTARTDURATION time.

You can specify this option in the Data Protection for HCL Domino preferences file.

deduplication

Use deduplication to specify whether data deduplication is used. The option can be set to deduplication yes or deduplication no depending on your requirements. You can specify this option in the Data Protection for HCL Domino preferences file.

domnode

Use domnode to use the web client GUI to back up and restore Domino server data. It provides the web client GUI with the IBM Storage Protect node name and respective Domino server to access for processing. It also provides important configuration information for the specified node. Specify the full path and name of the Data Protection for HCL Domino preferences file. For example: domnode /usr/tivoli/tsm/client/domino/bin64/domdsmc_notes/domdsm.cfg

Consider the following items when you are specifying the domnode option:

  • It must be specified to access the web client GUI.
  • It can be specified multiple times for as many Domino servers or Domino Partitioned Servers as are available.
  • It can be used in short form domno and is not case-sensitive.
  • Specify this option in the dsm.sys file that is used by the backup-archive client.

domnode example

In this example, the backup-archive client can access Domino server A, Domino server B, and Domino server C:

  • Contents of the dsm.sys file: 
    SERVERNAME serverA_notes 
DOMNODE /opt/tivoli/tsm/client/domino/bin/domdsmc_notesA/serverA.cfg  
SERVERNAME serverB_notes 
DOMNODE /opt/tivoli/tsm/client/domino/bin/domdsmc_notesB/serverB.cfg  
SERVERNAME serverC_notes 
DOMNODE /opt/tivoli/tsm/client/domino/bin/domdsmc_notesC/serverC.cfg
  • Contents of dsm1.opt: SERVERNAME domservA
  • Contents of dsm2.opt: SERVERNAME domservB
  • Contents of dsm3.opt: SERVERNAME domservC
  • Contents of serverA.cfg: NOTESInipath /home/notes1/notesdata DOMINstallpath /opt/lotus/bin ADSMLOGDIR=/opt/tivoli/tsm/client/domino/bin/domdsmc_notes1 ADSMOPTFILE=/opt/tivoli/tsm/client/domino/bin/domdsmc_notes1/dsm.opt LOGFILE=/opt/tivoli/tsm/client/domino/bin/domdsmc_notes1/domdsm.log DOMI_DIR=/opt/tivoli/tsm/client/domino/bin
  • Contents of serverB.cfg: NOTESInipath /home/notes2/notesdata DOMINstallpath /opt/lotus/bin ADSMLOGDIR=/opt/tivoli/tsm/client/domino/bin/domdsmc_notes2 ADSMOPTFILE=/opt/tivoli/tsm/client/domino/bin/domdsmc_notes2/dsm.opt LOGFILE=/opt/tivoli/tsm/client/domino/bin/domdsmc_notes2/domdsm.log DOMI_DIR=/opt/tivoli/tsm/client/domino/bin
  • Contents of serverC.cfg: NOTESInipath /home/notes/notesdata DOMINstallpath /opt/domino6/lotus/bin ADSMLOGDIR=/opt/tivoli/tsm/client/domino/bin/domdsmc_notes ADSMOPTFILE=/opt/tivoli/tsm/client/domino/bin/domdsmc_notes/dsm.opt LOGFILE=/opt/tivoli/tsm/client/domino/bin/domdsmc_notes/domdsm.log DOMI_DIR=/opt/tivoli/tsm/client/domino/bin

enableclientencryptkey

When enableclientencryptkey is set to yes, Data Protection for IBM Domino provides 128-bit Transparent encryption of Domino databases during backup and restore processing. One random encryption key is generated per session and is stored on the IBM Storage Protect server with the object in the server database. Although IBM Storage Protect manages the key, a valid database must be available to restore an encrypted object. You can specify the databases that you want encrypted by adding an include statement with the include.encrypt option in the dsm.sys file. See Include and exclude processing for an example of an include.encrypt statement. Transparent encryption is only available on IBM Storage Protect server Version 5.3 (or later). For more information, see IBM Storage Protect Using the Application Program Interface.

The encryption status of a backup can be seen during the backup or restore process by using the /DEtail command.

asnodename

When asnodename is specified, Data Protection for HCL Domino backs up or restores databases on multiple clients under the single IBM Storage Protect node name that is specified by this option. Unlike the nodename option that requires you to enter the password for the node name you specify, the asnodename option requires that you enter the password for your client node to access data that you own. Specify this option in the dsm.sys file. See IBM Storage Protect for UNIX and Linux Backup-Archive Clients Installation and User's Guide for more information about the asnodename option.