Domdsmc fullselective

The domdsmc fullselective command is a method of backing up both NSF and DB2® enabled Notes® databases.

Purpose

The domdsmc fullselective command first backs up all of the Domino® NSF databases and then runs a full backup of the Domino DB2 database to back up all of the DB2 enabled Notes databases. It differs from the selective command, which backs up NSF databases only. For non-DB2 enabled servers, use the selective command.

Syntax


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

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

>--+---------------------+-------------------------------------->
   '-/ADSMPWD=--password-'   

>--+--------------------------------------------+--------------->
   |            .-3----------.  .-,1024-------. |   
   '-/BUFFers=--+-numbuffers-+--+-,buffersize-+-'   

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

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

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

>--+----------------------+--+--------+------------------------->
   |              .-Yes-. |  '-/Quiet-'   
   '-/MOUNTWait=--+-No--+-'               

>--+-----------------------------+-----------------------------><
   |             .-1-----------. |   
   '-/SESSIONS=--+-numsessions-+-'   

Parameters

/ADSMNODe=nodename
Specifies the IBM Storage Protect node name Data Protection for IBM® Domino uses to log on to the IBM Storage Protect server. The command-line value overrides the value in the IBM Storage Protect options file.
/ADSMOPTFile=optionsfile
Specifies the IBM Storage Protect options file name. The file name can include a fully qualified path name. If you do not specify a path, the installation directory and then the current directory are searched for the specified file. The default is dsm.opt.
/ADSMPWD=password
Specifies the IBM Storage Protect password Data Protection for HCL Domino uses to logon to the IBM Storage Protect server. If you specify passwordaccessgenerate in the IBM Storage Protect 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.

/BUFFers=numbuffers, buffersize
Specifies the number and size of data buffers that transfer data between the Domino server and the IBM Storage Protect API. Increasing the number or size (or both) of the data buffers can improve throughput.

You can specify 2 - 8 buffers. The default value is 3. The size of the buffers can be 64 - 8192 kb. The default value is 1024.

If the /buffers parameter is not specified on the command line or defined in the preferences file, Data Protection for HCL Domino uses the default values.

/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 IBM Domino is installed.

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 one.
/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.

The default log file is domdsm.log.

When you are using multiple simultaneous instances of Data Protection for IBM 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.
/MOUNTWait=Yes|No
If the IBM Storage Protect server is configured to store transaction log backup data on removable media, then the IBM Storage Protect server can indicate to Data Protection for HCL Domino that it is waiting for a required storage volume to be mounted. In this case, you can specify whether Data Protection for HCL Domino waits for the media mount or stops the current operation. Removable media is media such as tapes.
You can specify:
Yes
Wait for tape mounts. This value is the default.
No
Do not wait for tape mounts.
/Quiet
Specifies that status information does not display. However, the information is written to the activity log.
/SESSions=numsessions|1
Specifies the number of IBM Storage Protect server sessions to be used by Data Protection for HCL Domino. You can specify from 1 to 64 sessions. The default value is 1.

Example

The following example backs up both NSF and DB2 enabled Notes databases using two sessions for the DB2 IBM Storage Protect agent to access the IBM Storage Protect server: domdsmc fullselective /db2session=2

Starting Domino full backup...
Initializing Domino connection...
Querying Domino for a list of databases, please wait...

Restart Analysis (0 MB): 100%
09/28/2011 06:55:58 AM Recovery Manager: Restart Recovery complete. 
(0/0 databases needed full/partial recovery)
09/28/2011 06:56:01 AM The map for DB2 errors was successfully created.


...

Backing up database statrep5.ntf, 114 of 122.
Full: 0 Read: 1,686,528 Written: 1,686,528 Rate: 4,844.12 Kb/Sec

Backup of statrep5.ntf completed successfully.

Backing up database teamrm7.ntf, 115 of 122.
Full: 0 Read: 2,883,584 Written: 2,883,584 Rate: 6,834.95 Kb/Sec

Backup of teamrm7.ntf completed successfully.

Backing up database toolbox.ntf, 116 of 122.
Full: 0 Read: 688,128 Written: 688,128 Rate: 5,209.30 Kb/Sec

Backup of toolbox.ntf completed successfully.

Backing up database updatesite.ntf, 117 of 122.
Full: 0 Read: 2,883,584 Written: 2,883,584 Rate: 8,233.92 Kb/Sec

Backup of updatesite.ntf completed successfully.

Backing up database userlicenses.ntf, 118 of 122.
Full: 0 Read: 663,552 Written: 663,552 Rate: 4,729.93 Kb/Sec

Backup of userlicenses.ntf completed successfully.

Backing up database userreg.ntf, 119 of 122.
Full: 0 Read: 458,752 Written: 458,752 Rate: 3,612.90 Kb/Sec

Backup of userreg.ntf completed successfully.

Backing up database webadmin.nsf, 120 of 122.
Full: 0 Read: 8,388,608 Written: 8,388,608 Rate: 11,457.34 Kb/Sec

Backup of webadmin.nsf completed successfully.

Backing up database webadmin.ntf, 121 of 122.
Full: 0 Read: 10,747,904 Written: 10,747,904 Rate: 11,371.61 Kb/Sec

Backup of webadmin.ntf completed successfully.

Backing up database xxx\busytime.ntf, 122 of 122.
Full: 0 Read: 248,832 Written: 248,832 Rate: 1,840.91 Kb/Sec

Backup of xxx\busytime.ntf completed successfully.

Backing up DB2 database DOMINO7.

Domino DB2 database backup completed successfully.


Total Domino NSF databases inspected: 122
Total Domino NSF backed up: 122
Total Domino NSF excluded: 0
Total Domino NSF deduplicated: 0
Total Domino NSF bytes inspected: 1,734,538,240
Total Domino NSF bytes transferred: 1,734,538,240
Total Domino NSF LanFree bytes transferred: 0
Total Domino NSF bytes before deduplication: 0
Total Domino NSF bytes after deduplication: 0
Total Domino NSF data compressed by: 0%
Total Domino NSF deduplication reduction: 0.00%
Total Domino NSF data reduction ratio: 0.00%

Domino DB2 database inspected: 1
Domino DB2 database backed up: 1

Throughput rate: 19,821.81 Kb/Sec
Total bytes transferred: 2,325,935,104
Elapsed processing time: 114.59 Secs