You can create a disaster recovery plan file and store the file locally or on another server.
About this task
- The recovery procedure
- A list of required database volumes, copy storage pool volumes, and active-data pool volumes, devices to read those volumes, and database and recovery log space requirements
- Copies of the server options file, device configuration file, and volume history information file
- Commands for performing database recovery and primary storage pool recovery
- Commands for registering licenses
- Instructions that you define
- Machine and recovery media information that you define
For details about the recovery plan file, see The disaster recovery plan file.
DRM creates one copy of the disaster recovery plan file each time you issue the PREPARE command. You should create multiple copies of the plan for safekeeping. For example, keep copies in print, on CD, on disk space that is located offsite, or on a remote server.
Before creating a disaster recovery plan, back up your storage pools then backup the database. See Backing up primary storage pools and Backing up the server database for details about these procedures.
If you manually send backup media offsite, see Moving copy storage pool and active-data pool volumes offsite. If you use virtual volumes, see Using virtual volumes to store data on another server.
When your backups are both offsite and marked offsite, you can create a disaster recovery plan.
You can use the Tivoli Storage Manager scheduler to periodically run the PREPARE command (see Automating server operations).
- The plan file that DRM generates is a template that contains information, including commands for recovering the database, that might not apply to your replacement systems or to your particular recovery scenario. To modify the plan or to store additional instructions that you will need during recovery from an actual disaster, use the RECOVERY.INSTRUCTIONS stanzas. Enter your site-specific information in the stanzas when you first create the plan file or after you test it.
- DRM creates
a plan that assumes that the latest database full plus incremental
series would be used to restore the database. However, you may want
to use DBSNAPSHOT backups for disaster recovery and retain your full
plus incremental backup series on site to recover from possible availability
problems. In this case, you must specify the use of DBSNAPSHOT backups
in the PREPARE command. For example:
prepare source=dbsnapshot
- Use the SET DRMPRIMSTGPOOL command or the PRIMSTGPOOL parameter with the PREPARE command to specify the names of the primary storage pools that will be eligible for DRM PREPARE processing and do not include Centera storage pools. If a specified pool name contains a wildcard, ensure that the expanded name will not match the name of any Centera storage pool defined to the Tivoli Storage Manager server.
- Or, if a Centera storage pool is included in the primary pool
list when a PREPARE command is executed, update the recovery plan
file that it generated. Delete or comment out the commands for the
Centera storage pool that may be included in the following stanzas:
- PRIMARY.VOLUMES.DESTROYED
- PRIMARY.VOLUMES.REPLACEMENT
- STGPOOLS.RESTORE
- Storing the disaster recovery plan locally
When you create a recovery plan file but do not specify a device class, the file is stored locally in a file system. If you store the file locally, you can specify a storage location. - Storing the disaster recovery plan on a target server
When you create a recovery plan file and specify a device class, the file is stored on a target server. 
Disaster recovery plan environmental considerations
The environment (for example, directory structure and location of the server executable and enrollment certificates) for a recovery using the disaster recovery plan file is assumed to be the same as the original environment. If the recovery environment is not the same, then you must edit the plan file to account for the changes in the environment.