IBM Tivoli Storage Manager Extended Edition, Version 7.1

Preparing for disaster recovery

Stay prepared for a disaster by establishing a procedure for disaster recovery by using the Disaster Recovery Manager (DRM). The steps are performed by the onsite administrator unless otherwise indicated.

Procedure

Complete the following steps to prepare for disaster recovery:

  1. Record the following information in the RECOVERY.INSTRUCTIONS stanza source files:
    • Software license numbers
    • Sources of replacement hardware
    • Any recovery steps specific to your installation
  2. Store the following information in the database:
    • Server and client node machine information (DEFINE MACHINE, DEFINE MACHINENODE ASSOCIATION, and INSERT MACHINE commands)
    • The location of the boot recovery media (DEFINE RECOVERYMEDIA command)
  3. Schedule automatic nightly backups to occur in the following order:
    • Primary Storage Pools
      • Backup active and inactive data to copy storage pools.
      • Copy active data to active-data pools.
    • Database
      • Back up the database
      Restriction: Ensure that the primary storage pool backup process is complete before you back up the database.
  4. Daily, create a list of the previous night's database, copy storage pool, and active-data pool volumes to be sent offsite:
    query drmedia * wherestate=mountable
    1. Check the volumes out of the library:
      move drmedia * wherestate=mountable
      Restriction: Ensure that the BACKUP STGPOOL command and the BACKUP DB command are complete before you issue the MOVE DRMEDIA command.
    2. Send the volumes offsite and record that the volumes were given to the courier:
      move drmedia * wherestate=notmountable
  5. Create a recovery plan:
    prepare
  6. Give a copy the recovery plan file to the courier.
  7. Create a list of tapes that contain data that is no longer valid and that should be returned to the site:
    query drmedia * wherestate=vaultretrieve
  8. Give the courier the database backup tapes, storage pool backup tapes, active-data pool tapes, the recovery plan file, and the list of volumes to be returned from the vault.
  9. The courier gives you any tapes that were on the previous day's return from the vault list.
    Update the state of these tapes and check them into the library:

    AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems
    move drmedia * wherestate=courierretrieve cmdf=/drm/checkin.libvol
      cmd="checkin libvol libauto &vol  status=scratch"
    Windows operating systems
    move drmedia * wherestate=courierretrieve cmdf=c:\drm\checkin.mac
      cmd="checkin libvol libauto &vol status=scratch"

    The volume records for the tapes that were in the COURIERRETRIEVE state are deleted from the database. The MOVE DRMEDIA command also generates the CHECKIN LIBVOL command for each tape that is processed in the file

    AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems ⁄drm⁄checkin.libvol.Windows operating systems c:\drm\checkin.mac. For example:

    checkin libvol libauto tape01 status=scratch
    checkin libvol libauto tape02 status=scratch
    ...
    Note: An administrator can run the MACRO command by specifying

    AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems ⁄drm⁄checkin.libvol.Windows operating systems c:\drm\checkin.mac as the macro name to process the CHECKIN LIBVOL commands.

    AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems
    > dsmadmc -id=xxxxx -pa=yyyyyy -se=zzzz MACRO /drm/checkin.libvol
    Windows operating systems
    > dsmadmc -id=xxxxx -pa=yyyyyy MACRO c:\drm\checkin.mac
  10. The courier takes the database backup tapes, storage pool backup tapes, active-data pool tapes, the recovery plan, and the list of volumes to return from the vault.
  11. Call the vault and verify that the backup tapes arrived and are secure, and that the tapes to be returned to the site have been given to the courier.
  12. Set the location of the volumes sent to the vault:
    move drmedia * wherestate=courier
  13. Set the location of the volumes that are given to the courier by the vault:
    move drmedia * wherestate=vaultretrieve

Example

The following example of a custom maintenance script shows the recommended sequence of steps for a specific Tivoli Storage Manager server configuration:
PARALLEL
BACKUP STGPOOL PRIMDISK DRM_COPYTAPE WAIT=YES
BACKUP STGPOOL PRIMTAPE DRM_COPYTYPE WAIT=YES
SERIAL
PARALLEL
COPY ACTIVEDATA PRIMDISK DRM_ACTTAPE WAIT=YES
COPY ACTIVEDATA PRIMTAPE DRM_ACTTAPE WAIT=YES
SERIAL
BACKUP DB DEVCLASS=TS7650G_N34 TYPE=FULL WAIT=YES
MOVE DRMEDIA * WHERESTATE=MOUNTABLE TOSTATE=VAULT SOURCE=DBBACKUP WAIT=YES
PREPARE SOURCE=DBBACKUP WAIT=YES
MIGRATE STGPOOL PRIMDISK LOWMIG=0 WAIT=YES
EXPIRE INVENTORY SKIPDIRS=NO RESOURCE=4 WAIT=YES
PARALLEL
RECLAIM STGPOOL PRIMDISK THRESHOLD=50 WAIT=YES
RECLAIM STGPOOL PRIMTAPE THRESHOLD=50 WAIT=YES
Restriction: Ensure that the BACKUP STGPOOL command and the BACKUP DB command complete before you issue other commands, for example, the MOVE DRMEDIA command.


Feedback