To recover from a disaster you will need database backup volumes and copy storage pool volumes. To prepare for a disaster, you will need perform the following daily tasks:
Task | Required Privilege Class |
---|---|
Send backup volumes offsite and back onsite | Unrestricted storage or operator |
Offsite recovery media management does not process virtual volumes. To display all virtual copy storage pool and database backup volumes that have their backup objects on the remote target server, issue the following command:
query drmedia * wherestate=remote
Offsite recovery media management does not move or display any two-sided volumes that have a REMOVABLEFILE device type.
The disaster recovery plan includes backup volume location information and can provide a list of offsite volumes required to restore a server.
The following diagram shows the typical life cycle of the recovery media:
Figure 89. Recovery Media Life Cycle
DRM assigns the following states to volumes. The location of a volume is known at each state.
After you have created the backup copies of your primary storage pools and database, you can send your backup media offsite. To send media offsite, mark the volumes as unavailable to TSM and give them to the courier. Do the following to identify the database backup and copy storage pool volumes and move them offsite:
query drmedia * wherestate=mountable
DRM displays information similar to the following:
+--------------------------------------------------------------------------------+ |Volume Name State Last Update Automated | | Date/Time LibName | |--------------- ---------------- ------------------- ----------------- | | TPBK05 Mountable 01/01/2000 12:00:31 LIBRARY | | TPBK99 Mountable 01/01/2000 12:00:32 LIBRARY | | TPBK06 Mountable 01/01/2000 12:01:03 LIBRARY | +--------------------------------------------------------------------------------+
move drmedia * wherestate=mountable
For all volumes in the MOUNTABLE state, DRM does the following:
Notes:
move drmedia * wherestate=mountable remove=no
Next, access a list of the volumes by issuing the following command:
query drmedia wherestate=notmountable
From this list identify and remove the cartridges (volumes) from the library.
move drmedia * wherestate=notmountable
For all volumes in the NOTMOUNTABLE state, DRM updates the volume state to COURIER and the volume location according to the SET DRMCOURIERNAME. If the SET command has not yet been issued, the default location is COURIER. For more information, see Specifying Defaults for Offsite Recovery Media Management
move drmedia * wherestate=courier
For all volumes in the COURIER state, DRM updates the volume state to VAULT and the volume location according to the SET DRMVAULTNAME command. If the SET command has not yet been issued, the default location is VAULT. For more information, see Specifying Defaults for Offsite Recovery Media Management.
query drmedia wherestate=vault
DRM displays information similar to the following:
+--------------------------------------------------------------------------------+ |Volume Name State Last Update Automated | | Date/Time LibName | |----------------- -------------- ------------------- ----------------- | |TAPE0P Vault 01/05/2000 10:53:20 | |TAPE1P Vault 01/05/2000 10:53:20 | |DBT02 Vault 01/05/2000 10:53:20 | |TAPE3S Vault 01/05/2000 10:53:20 | +--------------------------------------------------------------------------------+
move drmedia * wherestate=notmountable tostate=vault
For all volumes in the NOTMOUNTABLE state, DRM updates the volume state to VAULT and the volume location according to the SET DRMVAULTNAME command. If the SET command has not yet been issued, the default location is VAULT.
See Staying Prepared for a Disaster for an example that demonstrates sending server backup volumes offsite using MOVE DRMEDIA and QUERY DRMEDIA commands.
Use the following procedure to expire the non-virtual database backup volumes and return the volumes back onsite for reuse or disposal.
The following example sets the number of days to 30.
set drmdbbackupexpiredays 30
A database backup volume is considered eligible for expiration if all of the following conditions are true:
Note: | Database backup volumes that are virtual volumes are removed during expiration processing. This processing is started manually by issuing the EXPIRE INVENTORY command or automatically through the EXPINTERVAL option setting specified in the server options file. |
To determine which volumes to retrieve, issue the following command:
query drmedia * wherestate=vaultretrieve
move drmedia * wherestate=vaultretrieve
The server does the following for all volumes in the VAULTRETRIEVE state:
move drmedia * wherestate=courierretrieve
The server does the following for all volumes in the COURIERRETRIEVE state:
move drmedia * wherestate=vaultretrieve tostate=onsiteretrieve
The server does the following for all volumes with in the VAULTRETRIEVE state: