Domdsmc activatedbs

Purpose

Use Domdsmc activatedbs command to bring restored database backups online. If the database is logged, you can apply all applicable transactions from the transaction logs. Alternatively you can apply transactions up to a specific point in time to update the database.

You can put databases in a corrupted state if you press CTRL-C or cancel the job in the middle of an activate action. Canceling the action prevents the databases from being activated. Also, any databases that are activated before the CTRL-C cancel was run, can be corrupted, and must be restored and activated again.

This command acts on restored database backups that are pending activation, and that have been restored with the /activate=no parameter. The IBM Storage Protect server is not contacted unless archived transaction logs are needed for the /applylogs parameter.

Domino Server: restroan01     
--------------      

Logger Id: OF88256BC1:005F8602-ON00000365:0136DCCF 
---------- 
                          Transaction   

Log Archive Date       Log Filename    A/I      Size 
---------------------    ------------    ---     ------ 
05/22/2004 10:27:26      S0000000.TXN     A     64.00MB       


Domino Server: restroan01
--------------      

Logger Id: OF88256BC1:005EDBA5-ON00000365:0136DCCF
----------                           
                                    Transaction   

Log Archive Date       Log Filename    A/I      Size 
---------------------    ------------    ---     ------ 
05/22/2004 10:20:23      S0000000.TXN     A     64.00MB

Data Protection for IBM® Domino uses an alternative restore path for the transaction logs on a Domino 6 or later environment when the TRANSLOG_RECOVER_PATH variable is specified in the NOTES.INI file. If the alternative log restore path specified in the NOTES.INI file is not a fully qualified path, Data Protection for HCL Domino does not use the alternative restore path.

You can use any of the displayed Logger IDs to restore logged databases. To use any of the Logger IDs other than the current one, you must use an alternative server to restore logged databases. See NSF databases restore to alternate server and alternate partition for detailed instructions on how to run this procedure.

Parameters

/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 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 log on to the IBM Storage Protect server. If you specify the command 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 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 requirement to 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.

/APPLYLogs=date,time

Specifies that transaction log recovery for the restored databases is run if they are logged. The date and time values must be specified in the same date and time format that is defined in the Data Protection for HCL Domino preferences file. The transaction logs are applied to a specified point in time or to the current date and time if no date and time values are specified.

date

Specify a date string in the active date format. Transactions that are completed and committed before the specified date are applied to the restored database. The date that is specified must be after the backup date of the backup image that is being restored. The /pit option can be used with the restore command to automatically restore the most recent full backup image that is run before the wanted point-in-time.

Because there is one transaction log for all logged databases, all the databases must be activated together in one command. This situation applies when you are restoring multiple databases that requirement to have transactions that are applied from the log. This prevents the fetching of the same transaction logs multiple times from the IBM Storage Protect server. The databases can be restored separately if necessary, with the /activate=no parameter and then activated together with a single activatedbs command.

If you are restoring a database that is backed up from a different Domino server, logged transactions cannot be applied. In this case, you can activate only a full backup image. You must also use the Notes® fixup utility to reset the internal sequence numbers of the restored and activated database.

Note: If circular logging is in effect, it might not be possible to properly apply transactions if the log is wrapped. If an attempt to apply transaction logs fails, the database or databases that are processed are marked as corrupted. The database or databases must be restored again.

The date must be specified with the same date format that is defined in the Data Protection for HCL Domino preferences file. See Domdsmc set for a list of available date formats.

time

Specify a time string in the active time format. If you specify a date without the time, 00:00:00 on a 24-hour clock is used.

The time must be specified with the same time format that is defined in the Data Protection for HCL Domino preferences file. See Domdsmc set for a list of available time formats.

/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 is in the directory where Data Protection for HCL Domino is installed.

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.

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 for each instance is directed 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 to run daily. You can use the set command to:

• 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 already completed for the day.

You can specify:

60

Specifies that log entries are saved for 60 days before pruning. 60 days is the default.

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 Data Protection for HCL Domino log file. If you are running a command that prunes the log file and the value of the timeformat or dateformat parameter is changed, run 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.

/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. With this option, 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 or DVDs.

You can specify:

Yes

Wait for tape mounts.

No

Do not wait for tape mounts.

/PICk

Displays a list of the restored databases that are waiting for activation. The databases that are listed are the ones that match the dbname pattern specified. Databases to be activated can be selected from the list.

The pick list is presented as a scrollable list with the same manipulation functions as in the base IBM Storage Protect client PICK function.

/Quiet

Specifies that status information does not display. However, the information is written to the activity log.