DSMSERV RESTORE DB (Restore a database to its most current state)

Use the DSMSERV RESTORE DB utility to restore a database to its most current state under certain conditions.

The following conditions must be met:
  • An intact volume history file is available.
  • The recovery logs are available.
  • A device configuration file with the applicable device information is available.
Restrictions: You cannot restore a server database if the release level of the server database backup is different from the release level of the server that is being restored. For example, an error occurs when you restore a Version 6.3 database and you are using a Version 7.1 Tivoli® Storage Manager server.
You cannot restore a server database from a different Tivoli Storage Manager server if both of the following conditions are present:
  • The database backup is stored on virtual volumes
  • The connection to the Tivoli Storage Manager server is protected by SSL (Secure Sockets Layer)

Tivoli Storage Manager requests volume mounts to load the most recent backup series and then uses the recovery logs to update the database to its most current state.

Snapshot database backups cannot be used to restore a database to its most current state.

Syntax

Read syntax diagramSkip visual syntax diagram
>>-DSMSERV -+----------------------+---------------------------->
            |  (1)                 |   
            '------- -u--user_name-'   

                                 (2).- -k--Server1--.   
>--+-------------------------+------+---------------+----------->
   |  (1)                    |      '- -k--key_name-'   
   '------- -i--instance_dir-'                          

>--+-------------------+--+----------+--+-------+--RESTORE DB--->
   '- -o--options_file-'  '-noexpire-'  '-quiet-'               

>--+---------------------------+-------------------------------->
   '-RECOVerydir--=--directory-'   

>--+----------------------------+------------------------------->
   '-ACTIVELOGDir--=--directory-'   

                                     .-PReview--=--No------.   
>--+------------------------------+--+---------------------+---->
   '-ON--=--target_directory_file-'  '-PReview--=--+-Yes-+-'   
                                                   '-No--'     

   .-RESTOREKeys--=--No-------.   
>--+--------------------------+--------------------------------->
   '-RESTOREKeys--=--+-No---+-'   
                     +-YES--+     
                     '-ONLY-'     

>--+----------------------------+------------------------------><
   '-PASSword--=--password_name-'   
Notes:
  1. This parameter applies to AIX®, HP-UX, Linux, and Solaris servers only.
  2. This parameter applies only to Windows servers.

Parameters

AIX operating systemsHP-UX operating systemsLinux operating systemsOracle Solaris operating systems-u user_name
AIX operating systemsHP-UX operating systemsLinux operating systemsOracle Solaris operating systemsSpecifies a user name to switch to before initializing the server.
AIX operating systemsHP-UX operating systemsLinux operating systemsOracle Solaris operating systems-i instance_dir
AIX operating systemsHP-UX operating systemsLinux operating systemsOracle Solaris operating systemsSpecifies an instance directory to use. This instance directory becomes the current working directory of the server.
Windows operating systems-k key_name
Windows operating systemsSpecifies the name of the Windows registry key from which to retrieve information about the server. The default is SERVER1.
-o options_file
Specifies an options file to use.
noexpire
Specifies that expiration processing is suppressed when starting.
quiet
Specifies that messages to the console are suppressed.
RECOVerydir
Specifies a directory in which to store recovery log information from the database backup media. This directory must have enough space to hold this transaction recovery information and must be an empty directory. If this parameter is not specified, the default is to the directory specified by one of the following parameters in the DSMSERV FORMAT or DSMSERV LOADFORMAT utility:
  • ARCHFAILOVERLOGDIRECTORY, if specified
  • ARCHLOGDIRECTORY, if ARCHFAILOVERLOGDIRECTORY is not specified
ACTIVELOGDir
Specifies a directory in which to store the log files that are used to track the active database operations. This directory must be specified only if the intent is to switch to an active log directory different from the one that had already been configured.
On
Specifies a file that lists the directories to which the database is restored. Specify each directory on a separate line in the file. For example, the ON parameter specifies the restorelist.txt file, which contains the following list:AIX operating systemsHP-UX operating systemsLinux operating systemsOracle Solaris operating systems
/tsmdb001
/tsmdb002
/tsmdb003
Windows operating systems
e:\tsm\db001
f:\tsm\db002
g:\tsm\db003
If this parameter is not specified, the original directories that were recorded in the database backup are used.
Tip: If you specify multiple directories, ensure that the underlying file systems are of equal size to ensure a consistent degree of parallelism for database operations. If one or more directories for the database are smaller than the others, they reduce the potential for optimized parallel prefetching and distribution of the database.
PReview
Specifies that the volume history files be examined and that the database backup volumes from the volume history file be evaluated.
  1. Which set of database backup volumes best meets the most current criteria that are specified for restore processing? The volume history information provides details about the backup series ID, the operation ID (full, incremental 1, incremental 2, and so on), the date of the database backup, and the device class. This information and the parameters that are specified in the DSMSERV RESTORE DB command determine what to use to perform the restore. The volume history file is examined to find the most recent database backup and then to restore the data by using that backup.
  2. Is self-describing data available for the selected set of database backup volumes? Cross-check the volume history information for this backup series. The reconciliation reports what the self-describing data contains compared to what was learned from the volume history entries. The cross-check involves mounting one or more of the volumes that are indicated by the volume history. Then, using the self-describing data that was included in the database backup volumes, that information is reconciled against what is in the volume history for the database backup. If the information from the volume history file is inconsistent with the self-describing data, then messages are issued to identify the problem. For example, not all values are specified and available, and no self-describing data is found.

If the volume history information is consistent with self-describing data from the database backup, a message is issued indicating that the database backup can be used for restore processing.

If the volume history information is inconsistent with the self-describing data from the database backup or if the self-describing data for the backup cannot be found, error messages are issued indicating what was checked and what was missing.

If the PREVIEW parameter is not specified or if it is set to NO, and if the volume history and self-describing data from the database backup are consistent, then the restore proceeds.

If the PREVIEW parameter is not specified or if it is set to NO, and the reconciliation and validation fail, the database restore is not performed. Make extra volumes available and referred to from the volume history file, or remove the incomplete backup series or operation so that the Tivoli Storage Manager server selects a different preferred series or operation and continues processing.

If the PREVIEW parameter is set to YES, the process performs only the evaluation of the volume history file and the reconciliation and validation against the selected database backup.

AIX operating systemsLinux operating systemsOracle Solaris operating systemsWindows operating systemsRESTOREKeys
AIX operating systemsLinux operating systemsOracle Solaris operating systemsWindows operating systemsSpecifies whether to restore the server master encryption key that is used to encrypt storage pool data when the database is restored. This parameter is optional and only applies if you are using encrypted container storage pools in a cloud environment. If the server master key is protected when the database is restored, the default is YES. If the server master key is not protected when the database is restored, the default is NO. You can specify one of the following values:
No
Specifies that the server master key is not restored when the database is restored.
Yes
Specifies that the server master key is restored when the database is restored. You must specify a password with this parameter.
Only
Specifies that only the server master key is restored. The database is not restored.
AIX operating systemsLinux operating systemsOracle Solaris operating systemsWindows operating systemsPASSword
AIX operating systemsLinux operating systemsOracle Solaris operating systemsWindows operating systemsSpecifies the password that is used to protect the database backup. This parameter only applies if you are using encrypted container storage pools in a cloud environment. If you specify a password for database backup, you must specify the same password on the RESTORE DB command to restore the database. You must use a password if you specify the RESTOREKEYS=YES or RESTOREKEYS=NO parameter.

Example: Restore the database to its most current state

Restore the database to its most current state by using the already configured active log directory.
 dsmserv restore db

Example: Restore the server master key without restoring the database

Restore the server master key without restoring the database by issuing the following command:
dsmserv restore db restorekeys=only