Domdsmc resetdatabase

Purpose

Running the domdsmc resetdatabase command resets a Domino server database that is incomplete because of an unexpected termination during a Data Protection for HCL Domino backup. An unexpected termination during a Data Protection for HCL Domino backup can be caused by the following actions:

• A program check or segment violation.
• A kill command.
• Exiting a debugging program.

Subsequent attempts to back up such a database fails until the resetdatabase command is issued.

You can specify one or more Domino databases to be reset. You must specify the database name. The resetdatabase command does not accept wildcard characters.

For more information about disaster recovery procedures, see Recovering from loss of Domino transaction logs for NSF databases.

>>-DOMDSMC--RESETdatabase--+-dbname-----+----------------------->
                           | .-,------. |   
                           | V        | |   
                           '---dbname-+-'   

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

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

Parameters

dbname dbname,dbname,...,

Specifies the database to be reset. Multiple dbnames can be specified separated with commas.

/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 is stored 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.

/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 used. Logging is directed 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 run daily. Use the set command to do 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. When the value of /logprune is a number, the prune is run even if one has already been run 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, do one of the following to prevent undesired 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.