![]() |
![]() |
You can create a disaster recovery plan file and store the file locally or on another server.
The recovery plan contains the following information:
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 diskettes, on NFS-mounted 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 Storage Pools" and Backing Up the Database for details about these procedures.
If you manually send backup media offsite, see Moving Backup 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 Chapter 17, Automating Server Operations).
prepare source=dbsnapshot
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. For example, to store the recovery plan file locally in the /u/server/recoveryplans/ directory, enter:
prepare planprefix=/u/server/recoveryplans/
Recovery plan files that are stored locally are not automatically expired. You should periodically delete down-level recovery plan files manually.
DRM appends to the file name the date and time (yyyymmdd.hhmmss). For example:
/u/server/recoveryplans/20000925.120532
When you create a recovery plan file and specify a device class, the file is stored on a target server. Storing recovery plan files on a target server provides the following:
First, set up the source and target servers and define a device class a device type of SERVER (see Setting Up Source and Target Servers for Virtual Volumes for details). For example, assume a device class named TARGETCLASS is defined on the source server where you create the recovery plan file. Then to create the plan file, enter:
prepare devclass=targetclass
The recovery plan file is written as an object on the target server, and a volume history record is created on the source server. For more about recovery plan files that are stored on target servers, see Displaying Information about Recovery Plan Files.