Domdsmc DB2selective

How to use the domdsmc db2selective command is described.

Purpose

The domdsmc db2selective command backs up DB2 Groups and the Domino® DB2 database.
  • If the Domino DB2 database is enabled for rollforward recovery, an online backup is run.
  • If the Domino DB2 database is not enabled for rollforward recovery, Data Protection for IBM® Domino cannot back it up.
  • DB2 Group backups are only available when the Domino DB2 database is enabled for rollforward recovery.
Tip: When you are backing up multiple DB2 groups, increase the value of the Tivoli® Storage Manager server COMMTIMEOUT option to avoid a backup failure because of a session timeout.
>>-DOMDSMC--DB2Selective--+-"*"----------+---------------------->
                          | .-,--------. |   
                          | V          | |   
                          '---db2group-+-'   

>--+----------------------+------------------------------------->
   '-/ADSMNODe=--nodename-'   

>--+--------------------------------+--------------------------->
   |                .-dsm.opt-----. |   
   '-/ADSMOPTFile=--+-optionsfile-+-'   

>--+---------------------+--+-------------------------------+--->
   '-/ADSMPWD=--password-'  |               .-domdsm.cfg--. |   
                            '-/CONFIGfile=--+-cfgfilename-+-'   

>--+--------------------------------+--+-------+---------------->
   |                .-1-----------. |  '-/FULL-'   
   '-/DB2SESSIONS=--+-numsessions-+-'              

>--+----------------------------+--+--------------------+------->
   |            .-domdsm.log--. |  |             .-60-. |   
   '-/LOGFile=--+-logfilename-+-'  '-/LOGPRUne=--+-n--+-'   
                                                 '-No-'     

>--+--------+--------------------------------------------------><
   '-/Quiet-'   

Parameters

"*"|db2group,db2group,...
Specifies the DB2 Groups to back up. When a DB2 Group is not specified and the /full parameter is specified, a full DB2 database backup is run. Otherwise, a table space backup is run. The wildcard character asterisk (*) is used to specify a group of databases when used in the db2group. Multiple db2groups can be specified separated with commas.

If you specify the wildcard character in the db2group, you must use double or single quotation marks, for example, "abc*" or 'abc*'.

/ADSMNODe=nodename
Specifies the IBM Storage Protect node name Data Protection for HCL Domino uses to log on to the IBM Storage Protect server. The command-line value overrides the value in the IBM Storage Protect system options file.
/ADSMOPTFile=optionsfile
Specifies the name of the options file used by the IBM Storage Protect API. The default file name is dsm.opt. The optionsfile variable can include a fully qualified path name or a relative path. A relative path means that the path is relative to the directory from which Data Protection for HCL Domino is run. Note the following considerations:
  • When Data Protection for HCL Domino is started by a Domino startup script, tools/startup, that was configured by the dominstall program, a relative path means that the path is relative to the Domino Data directory and NOT to the directory from which Data Protection for HCL Domino is run.
  • This parameter functions in the same manner as the DSMI_CONFIG environment variable. When the DSMI_CONFIG environment variable is set, the options file specified by this environment variable is recognized as the default options file.
  • Specify the adsmoptfile parameter in the Data Protection for HCL Domino preferences file domdsm.cfg when you are using the web client GUI.
/ADSMPWD=password
Specifies the IBM Storage Protect password Data Protection for HCL Domino uses to log on to the IBM Storage Protect server. If you specify passwordaccessgenerate in the IBM Storage Protect system options file, then the password is not required. In this case, Data Protection for HCL Domino uses the password that is stored by the IBM Storage Protect API.

If passwordaccess is set to generate and you specify a password, the value is ignored unless a password for this node is not stored. In this case, the specified password is stored and used for the current command execution.

If passwordaccess is set to prompt and you specify a password on the command line, you are not prompted for a password. The command-line value overrides the prompt.

If passwordaccess is set to prompt and you do not specify a password on the command line, then you are prompted for a password.

/CONFIGfile=cfgfilename
Specifies the name of the Data Protection for HCL Domino preferences file. The file name can include a fully qualified path. If you do not specify a path, it is assumed the preferences file in the directory where Data Protection for HCL Domino is installed.

You can also specify the preferences file with the DOMI_CONFIG environment variable.

The default preferences file is domdsm.cfg.

/DB2SESSIONS=numsessions
Specify the number of IBM Storage Protect sessions that the DB2 IBM Storage Protect agent uses. You can specify 1-64 sessions. The default value is 1.
/FULL
Specify whether a full DB2 database is backed up.
/LOGFile=logfilename
Specifies the name of the activity log that is generated by Data Protection for HCL Domino. The log file name is used for the current command and does not update the default log file that is stored in the preferences file. You can use the set command to change the default log file name that is stored in the preferences file. The command-line parameter can be used to override the default for one command run. If the specified file does not exist, it is created. If it does exist, new log entries are appended to the file. The file name can include a fully qualified path. If you do not specify a path, the file is written to the directory where Data Protection for HCL Domino is installed.

You can specify the log file with the DOMI_LOG environment variable.

The default log file is domdsm.log.

When you are using multiple simultaneous instances of Data Protection for HCL Domino to run operations, use the /logfile parameter to specify a different log file for each instance. Using this parameter directs logging for each instance to a different log file and prevents interspersed log file records. Failure to specify a different log file for each instance can result in unreadable log files.

/LOGPRUne=60|n|No
Specifies whether to prune log entries. By default, log pruning is enabled and done daily. You can use the set command to do one of the following actions:
  • Change the defaults so that log pruning is disabled
  • Change the number of days log entries are saved
You can use the /logprune option to override these defaults for one command run. Note, when the value of /logprune is a number, the prune is done even if one is complete for the day.
You can specify:
60
Specifies that log entries are saved for 60 days before pruning.
n
Specifies the number of days to save log entries. The range of values is 0 - 9999. A value of 0 deletes all entries in the log except for the current command run entries.
No
Do not prune the log.
Changes to the value of the timeformat or dateformat parameter can result in an undesired pruning of the log file. If you are running a command that prunes the log file and the value of the timeformat or dateformat parameter changes, run one of the following to prevent pruning of the log file:
  • Make a copy of the existing log file.
  • Specify a new log file with the /logfile parameter or logfile setting.
/Quiet
Specifies that status information does not display. However, the information is written to the activity log.

Examples

Example 1: The following example backs up the Domino DB2 database:
domdsmc db2selective /full
Output example:
Starting Domino DB2 database backup... 
Backing up DB2 database DOMINO. 
Domino DB2 database backup completed successfully.
Example 2: The following example backs up the DB2 Groups GRP1 and GRP2:
domdsmc db2selective GRP1,GRP2
Output example:
Starting Domino DB2 group backup... 
Backing up DB2 group Default/GRP1, 1 of 2. 
Backup of GRP1 completed successfully.  

Backing up DB2 group Default/GRP2, 2 of 2. 
Backup of GRP1 completed successfully