Administrator's Guide


DRM User Scenarios

This section presents a realistic example of using DRM to prepare for and recovery from disaster. The detailed steps are followed by an outline that gives you a brief day-by-day picture of the DRM tasks.

Scenario 1: Tivoli Disaster Recovery Manager Controls Volume Movement

This scenario shows how to use TSM and DRM policies to move volumes offsite for disaster recovery protection and back onsite for reuse. It also shows how to update the tape management product database (for example, RMM) with the current volume locations.

  1. TSM storage pool backup and database backup processing is performed nightly using TSM central scheduling.

  2. RMM Inventory Management (including Vital record processing, Expiration processing, and Storage location management processing) runs nightly after backups.

  3. At 8 a.m. the tape administrator issues the following command to mark the database backup and copy storage pool volumes created last night unavailable for processing, and also generate the RMM CHANGEVOLUME commands for each volume successfully processed by the MOVE DRMEDIA command and put the RMM commands in a file, ADSM.DRM.EXEC.CMDS (set by the previous SET DRMCMDFILENAME command):
           move drmedia * wherestate=mountable
                cmd="rmm changevolume &vol location( ironvault) manualmove"
    

    The content of the resulting ADSM.DRM.EXEC.CMDS file is:

           RMM CHANGEVOLUME DBTP01 LOCATION(IRONVAULT) MANUALMOVE
           RMM CHANGEVOLUME DBTP02 LOCATION(IRONVAULT) MANUALMOVE
           RMM CHANGEVOLUME CSTP01 LOCATION(IRONVAULT) MANUALMOVE
           RMM CHANGEVOLUME CSTP02 LOCATION(IRONVAULT) MANUALMOVE
    

    The tape administrator issues the following TSO command to run the RMM commands. The volumes are ejected from the ATL1 library because the library is a system-managed library and marked in transit to IRONVAULT:

              EXEC 'ADSM.DRM.EXEC.CMDS'
    

  4. The administrator then packages the volumes so that they can be given to the courier.

  5. The courier arrives to pick up today's backup tapes. The administrator records that the volumes will be given to the courier by issuing the following command:
           move drmedia * wherestate=notmountable
    

  6. To generate a recovery plan file with the latest volume information, the administrator issues the following command:
          prepare
    

    The administrator copies the recovery plan file to a diskette that will be given to the courier.

  7. Several weeks ago during a scheduled server reclamation processing, copy storage pool volume CSP01 was reclaimed and its TSM volume status was changed to PENDING. The volume is physically located at the offsite vault.

  8. Last night the PENDING window passed for volume CSP01 and its TSM volume status is now EMPTY. Also, a database backup series at vault has exceeded the value specified by SET DRMDBBACKUPEXPIREDAYS command. The volumes no longer contain valid backup data and should be brought back onsite for reuse or disposal.

  9. To determine and delete any tapes from database and return them to scratch for reuse, the administrator issues the following command:
           move drmedia * wherestate=vaultretrieve tostate=onsiteretrieve
    

    This command deletes volume records for the empty/expired volumes at vault. The volumes become 'PENDING SCRATCH' in the RMM database because the deletion exit, ARCTVEXT, is invoked during volume deletion.

  10. The administrator gives the database backup and copy storage pool tapes, the recovery plan file diskette, and the RMM Movement Report that lists the volumes to be returned from the vault to the courier.

  11. The courier gives the tapes that were on the previous day's return from the vault list to the administrator. When the volumes are physically entered into ATL1, the movement is automatically confirmed by RMM because the ATL1 is a system-managed library. The volumes are returned to scratch status.

  12. The courier drives to the vault with today's backup volumes, the recovery plan diskette, and the volumes to return from the vault list.

  13. At 4 p.m. the tape administrator calls the vault and verifies that today's backup volumes arrived and are secure. The administrator issues the following command:
           move drmedia * wherestate=courier
                cmd="rmm changevolume &vol confirmmove"
    

    The MOVE DRMEDIA command sets the location of the volumes to Ironvault and generates the RMM CHANGEVOLUME CONFIRMMOVE commands for each volume successfully processed, and saves the generated commands in a file, ADSM.DRM.EXEC.CMDS:

            RMM CHANGEVOLUME DBTP01 CONFIRMMOVE
            RMM CHANGEVOLUME DBTP02 CONFIRMMOVE
            RMM CHANGEVOLUME CSTP01 CONFIRMMOVE
            RMM CHANGEVOLUME CSTP02 CONFIRMMOVE
    

  14. The tape administrator issues the following TSO command:
              EXEC 'ADSM.DRM.EXEC.CMDS'
    

    After the command is issued, the RMM database is confirmed with the location, IRONVAULT, for each volume in the file.

    Note:If you want the RMM CHANGEVOLUME commands to be written to a file other than the default one, ADSM.DRM.EXEC.CMDS, specify the file name on the MOVE DRMEDIA command with CMDFILENAME parameter.

  15. Later that week, an audit team from headquarters arrives unannounced and asks the administrator for a copy of the disaster recovery plan for this server. The administrator gives the auditors a copy of the recovery plan file generated two hours earlier with up-to-date information that includes the volumes required for recovery, their location, and the commands required to use them to restore the server. The auditors are impressed by the plan's timeliness and completeness.

Scenario 2: Removable Media Management Controls Volume Movement

This scenario demonstrates how to use the policies defined with RMM Vital Record Specification (VRS) for moving volumes offsite for disaster recovery protection and back onsite for reuse, and how to use policies defined with TSM and DRM to expire or empty the volumes at the vault. If you use a tape management product to move your volumes to the offsite location today and you want to update TSM database to reflect the movement of the TSM volumes, you may consider following this scenario:

  1. Storage pool backup and database backup is performed nightly using TSM central scheduling.

  2. RMM Inventory Management (including Vital record processing, Expiration processing, and Storage location management processing) runs nightly after backups.

  3. RMM SEARCHVOLUME command runs after RMM Inventory Management processing:
         SEARCHVOLUME VOLUME(*) LIMIT(*) DESTINATION(IRONVAULT)
                      LOCATION(ATL1) INTRANSIT(NO) OWNER(TIVSM)
                      CLIST('RMM CHANGEVOLUME ',' LOCATION(IRONVAULT)')
    
    Note:ATL1 is a system-managed library. If you want to eject all volumes scheduled to move from the library to IRONVAULT, the specification of the OWNER is not necessary.

    The SEARCHVOLUME command builds CHANGEVOLUME commands for each volume belonging to TSM and its tape data set name matches the data set name specified in VRS, and saves the commands in a CLIST data set, prefix.EXEC.RMM.CLIST:

          RMM CHANGEVOLUME DBTP01 LOCATION(IRONVAULT)
          RMM CHANGEVOLUME DBTP02 LOCATION(IRONVAULT)
          RMM CHANGEVOLUME CSTP01 LOCATION(IRONVAULT)
          RMM CHANGEVOLUME CSTP02 LOCATION(IRONVAULT)
    

  4. At 8 a.m. the tape administrator issues the following TSO command and all database backup and copy storage pool volumes created last night are ejected from the ATL1 library because the library is a system-managed library and marked in transit to IRONVAULT:
                 EXEC 'prefix.EXEC.RMM.CLIST'
    

  5. After the volumes are ejected from the library and packaged for sending to IRONVAULT, the tape administrator runs SEARCHVOLUME command to generate MOVE DRMEDIA commands for each TSM volume in the transition to IRONVAULT:
         SEARCHVOLUME VOLUME(*) LIMIT(*) DESTINATION(IRONVAULT)
                      LOCATION(ATL1) INTRANSIT(Y) OWNER(TIVSM)
                      CLIST('MOVE DRMEDIA ',' TOSTATE=COURIER')
    
    Note:OWNER is used here to restrict to only TSM volumes. The MOVE DRMEDIA command is used to mark the volumes unavailable for onsite processing in the database.

    The SEARCHVOLUME command generates the following MOVE DRMEDIA commands and saves them as a macro in a CLIST data set, prefix.EXEC.RMM.CLIST:

            move drmedia dbtp01 tostate=courier
            move drmedia dbtp02 tostate=courier
            move drmedia cstp01 tostate=courier
            move drmedia cstp02 tostate=courier
    

  6. The tape administrator then runs the macro with the CLIST data set, prefix.EXEC.RMM.CLIST, as the macro name to issue the MOVE DRMEDIA commands:
              DSMADMC -id=xxxx -pa=yyyy MACRO 'prefix.EXEC.RMM.CLIST'
    

    After the macro command is run, the volumes are marked offsite and unavailable for processing in database.

  7. The courier arrives to pick up today's backup tapes. The administrator generates a recovery plan file with the latest volume information by issuing the following command:
         prepare
    

    The administrator copies the recovery plan file to a diskette that will be given to the courier.

  8. Several weeks ago during a scheduled server reclamation processing, copy storage pool volume CSP01 was reclaimed and its TSM volume status was changed to PENDING. The volume is physically located at the offsite vault.

  9. Last night the PENDING window passed for volume CSP01 and its TSM volume status is now EMPTY. The volume no longer contains valid backup data. Also, one database backup series at vault that is in DBTP55 and DBTP33 volumes has exceeded the value specified by the SET DRMDBBACKUPEXPIREDAYS command. These volumes no longer contain valid backup data and should be brought back onsite for reuse or disposal.

  10. To make the EMPTY/EXPIRED TSM volumes become scratch volumes for moving back onsite for reuse, the administrator issues:
          move drmedia * wherestate=vaultretrieve tostate=onsiteretrieve
    

    This command deletes TSM volume records for the empty/expired volumes at vault. The volumes become 'PENDING SCRATCH' in the RMM database because the deletion exit, ARCTVEXT, is invoked during volume deletion.

  11. The administrator gives the database backup and copy storage pool tapes, the recovery plan file diskette, and the RMM Movement Report that list the volumes to be returned from the vault to the courier.

  12. The courier gives the tapes that were on the previous day's return from the vault list to the administrator. When the volumes are physically entered into ATL1, the movement is automatically confirmed by RMM because the ATL1 is a system-managed library. The volumes are returned to the scratch status for reuse.

  13. The courier drives to the vault with today's backup volumes, the recovery plan diskette, and the volumes to return from the vault list.

  14. At 4 p.m. the tape administrator calls the vault and verifies that today's backup volumes arrived and are secure. The administrator run the SEARCHVOLUME command to generate MOVE DRMEDIA command for each TSM volume received at IRONVAULT:
         SEARCHVOLUME VOLUME(*) LIMIT(*) DESTINATION(IRONVAULT)
                      LOCATION(ATL1) INTRANSIT(Y) OWNER(TIVSM)
                      CLIST('MOVE DRMEDIA ',' TOSTATE=VAULT')
    
    Note:OWNER is used here to restrict to only TSM volumes. The MOVE DRMEDIA command is used to update the volume location and state in the TSM database.

    The CLIST data set, prefix.EXEC.RMM.CLIST, contains the following MOVE DRMEDIA commands for each volume:

            move drmedia dbtp01 tostate=vault
            move drmedia dbtp02 tostate=vault
            move drmedia cstp01 tostate=vault
            move drmedia cstp02 tostate=vault
    

  15. The administrator runs the TSM macro command with the CLIST data set, prefix.EXEC.RMM.CLIST, as the macro name to execute the MOVE DRMEDIA commands:
            DSMADMC -id=xxxx -pa=yyyy macro 'prefix.EXEC.RMM.CLIST'
    

    After the macro command is run, the TSM database is updated to reflect the new ORM state and location for each volume.

  16. The administrator runs the SEARCHVOLUME command to generate the CHANGEVOLUME CONFIRMMOVE command for each TSM volume received at IRONVAULT:
          SEARCHVOLUME VOLUME(*) LIMIT(*) DESTINATION(IRONVAULT)
                       LOCATION(ATL1) INTRANSIT(Y) OWNER(TIVSM)
                       CLIST('RMM CHANGEVOLUME ',' CONFIRMMOVE')
    

    The CLIST data set, prefix.EXEC.RMM.CLIST, contains the following CHANGEVOLUME CONFIRMMOVE commands for each TSM volume and the administrator runs the CLIST to confirm the movement:

            RMM CHANGEVOLUME DBTP01 CONFIRMMOVE
            RMM CHANGEVOLUME DBTP02 CONFIRMMOVE
            RMM CHANGEVOLUME CSTP01 CONFIRMMOVE
            RMM CHANGEVOLUME CSTP02 CONFIRMMOVE
    
    Note:If you want to confirm all volumes, including TSM volumes, moved from ATL1 to IRONVAULT, the 'RMM CHANGEVOLUME * CONFIRMMOVE(ATL1, IRONVAULT)' command can be issued without running SEARCHVOLUME command to generate CONFIRMMOVE command for each volume.

  17. Later that week, an audit team arrives unannounced and asks the administrator for a copy of the disaster recovery plan for this server. The administrator has a recovery plan file generated two hours earlier. The file contains current information that includes the volumes required for recovery, their location, and the commands required to use them to restore the server.

Recovering the Server Scenario

The following scenario shows how an administrator uses the latest recovery plan file to recover the TSM server. The TSM server in this example does not use virtual volumes. A disaster has destroyed the TSM server, and a complete recovery of the server is required.

  1. The administrator reviews the latest recovery plan file for the TSM server. Following the notes in the INSTR.GENERAL stanza, the administrator reviews the sequence of steps required to recover the server.

  2. The administrator obtains the backup tapes that were stored offsite.

  3. The administrator reviews the INSTR.OFFSITE stanza for the name and telephone number of the courier that the company uses to move tapes between the data center and the offsite vault.

  4. The administrator uses a locally written procedure to break out the recovery plan file stanzas into multiple files. (See Breaking Out a Disaster Recovery Plan File.) These files can be viewed, updated, printed, or run as TSM macros, REXX EXEC, or JCL.

  5. The administrator prints the VOLUMES.REQUIRED file. The printout is handed to the courier who goes to the offsite vault to obtain the backup volumes.

  6. The administrator finds a suitable replacement machine. Stanza DEVICES.REQUIRED specifies the required tape drive type that will be needed to read the backup tapes. Stanza SERVER.REQUIRE summarizes the required amount of disk space.

  7. The administrator restores the TSM server and administrative client software. The software and its location were specified in the INSTR.INSTALL stanza.

  8. The administrator reviews the TSM macros contained in the recovery plan. At the time of the disaster, the courier had not picked up the database and storage pool incremental backup volumes created the previous night. However, they were not destroyed. The administrator removes the entry for the storage pool backup volume from the COPYVOL.DESTR file.

  9. The courier returns with the required volumes. Somehow, the vault could not find one of the copy storage pool volumes. There is not enough time to wait for the vault location to find the lost volume. The administrator removes the entry for that volume from the COPYVOL.AVAIL file.

  10. All of the server's primary volumes were destroyed. The administrator decides there are no changes required to the PRIMVOL JCL and TSM macro files.

  11. To restore the database to a point where clients can be recovered, the administrator invokes the RECOVERY.DRMODE REXX EXEC by entering the TSO command:
       exec recovery.drmode 'tsmadm1 adm1pw dsm1599'
    
    Note:The administrator could instead have used the steps in the RECOVERY.DRMODE REXX EXEC as a guide and manually run each step.
    The following are the steps run in this recovery REXX EXEC:

    1. Copy the TSM server options file from the SERVOPT.FILE file to its original location.

    2. Copy the volume history file required by TSM DSMSERV RESTORE DB processing from the VOLHIST.FILE file to its original location.
      Note:Use this copy of the volume history file unless you have a more recent copy (after the disaster occurred).

    3. Copy the device configuration file required by DSMSERV RESTORE DB processing from the DEVCONF.FILE file to its original location.

    4. Create the TSM server recovery log and database volumes using DSMFMT.

    5. Issue DSMSERV FORMAT for the recovery log and database files.

    6. Issue the DSMSERV RESTORE DB.

    7. Start the server.

    8. Mark copy storage pool volumes retrieved from vault as available.

    9. Mark copy storage pool volumes which cannot be obtained as unavailable.

    10. Mark primary storage pool volumes as destroyed.

    Notes:

    1. Due to changes in hardware configuration during recovery it may be necessary to update the device configuration file located in the restored TSM database, see Updating the Device Configuration File.

    The TSM server is now recovered to the point where it can service the restore requests of any of its connected clients.

  12. The administrator invokes the RECOVERY.NMODE REXX EXEC file to restore the server primary storage pools. However, in this scenario, the client machines were not damaged so the focus of the administrator is to restore full TSM server operation.

    The administrator could instead have used the steps in the RECOVERY.NMODE REXX EXEC as a guide and manually executed each step.

    The steps run in this recovery REXX EXEC are:

    1. Create replacement primary volumes.

    2. Define the replacement primary volumes to TSM.

    3. Restore the primary storage pools.
    Note:This action is optional at this time because TSM can access the copy storage pool volumes directly to restore client data. Using this feature, the administrator can minimize client recovery time because server primary storage pools do not have to be restored first.

  13. The administrator collects the database backup and copy storage pool volumes used in the recovery so that they can be returned to the vault. For these backup volumes to be returned to the vault using the routine MOVE DRMEDIA process, the administrator issues the following commands for the database backup volumes:
         update volhist TPBK50 devcl=lib3494 ormstate=mountable
         update volhist TPBK51 devcl=lib3494 ormstate=mountable
    

    The copy storage pool volumes used in the recovery already have the correct ORMSTATE.

  14. The administrator runs the BACKUP DB command to back up the newly restored database.

  15. The administrator issues the MOVE DRMEDIA * WHERESTATE=MOUNTABLE command to mark the volumes unavailable for TSM onsite processing and to generate the tape management product commands to check the volumes out of the library.

  16. The administrator creates a list of the volumes to be given to the courier, the administrator issues the QUERY DRMEDIA * WHERESTATE=NOTMOUNTABLE.

  17. The administrator packages the volumes, gives them to the courier, and issues the MOVE DRMEDIA * WHERESTATE=NOTMOUNTABLE command.

  18. The administrator issues the PREPARE command.

Recovering Clients Scenario

The following scenario demonstrates the recovery of clients. A week after the TSM server was recovered, another water pipe burst in the building that houses distributed systems applications. Many machines that were backed up using clients were destroyed. A disaster is declared.

  1. To view a list of client machines that were lost in building 21 and their restore priority, the administrator issues the following command:
    query machine building=021 format=detailed
    

    TSM displays information similar to the following:

    +--------------------------------------------------------------------------------+
    |          Machine Name: POLARIS                                                 |
    |      Machine Priority: 1                                                       |
    |              Building: 21                                                      |
    |                 Floor: 2                                                       |
    |                  Room: 1                                                       |
    |               Server?: No                                                      |
    |           Description: Payroll                                                 |
    |             Node Name: POLARIS                                                 |
    |   Recovery Media Name: MKSYSB1                                                 |
    |      Characteristics?: Yes                                                     |
    |Recovery Instructions?: Yes                                                     |
    +--------------------------------------------------------------------------------+

  2. For each machine, the administrator issues the following commands:

    1. To determine the location of the boot media, the administrator issues the QUERY RECOVERYMEDIA command. For example:
      query recoverymedia mksysb1
      

      TSM displays the following information:

      +--------------------------------------------------------------------------------+
      |Recovery Media Name  Volume Names    Location    Machine Name                   |
      |-------------------- -----------     ----------  ----------------               |
      |MKSYSB1              vol1 vol2       IRONVAULT    POLARIS                       |
      |                      vol3                                                      |
      +--------------------------------------------------------------------------------+

    2. To determine the machine specific recovery instructions for the POLARIS machine, the administrator issues:
      query machine polaris format=recoveryinstructions
      

      TSM displays the following:

      +--------------------------------------------------------------------------------+
      |Recovery Instructions for Polaris.                                              |
      |Primary Contact:                                                                |
      |   Jane Smith (wk 520-000-0000 hm 520-001-0001)                                 |
      |Secondary Contact:                                                              |
      |   John Adams (wk 520-000-0001 hm 520-002-0002)                                 |
      +--------------------------------------------------------------------------------+

    3. To determine the machine hardware requirements for POLARIS, the administrator issues:
      query machine polaris format=characteristics
      

      TSM displays information similar to the following:

      +--------------------------------------------------------------------------------+
      |devices                                                                         |
      |aio0         Defined                Asynchronous I/O                            |
      |bus0         Available 00-00        Microchannel Bus                            |
      |fd0          Available 00-00-0D-00  Diskette Drive                              |
      |fda0         Available 00-00-0D     Standard I/O Diskette Adapter               |
      |fpa0         Available 00-00        Floating Point Processor                    |
      |gda0         Available 00-04        Color Graphics Display Adapter              |
      |hd1          Defined                Logical volume                              |
      |hd2          Defined                Logical volume                              |
      |hd3          Defined                Logical volume                              |
      |hdisk0       Available 00-01-00-00  400 MB SCSI Disk Drive                      |
      |hdisk1       Available 00-01-00-40  Other SCSI Disk Drive                       |
      |hft0         Available              High Function Terminal Subsystem            |
      |inet0        Available              Internet Network Extension                  |
      |ioplanar0    Available 00-00        I/O Planar                                  |
      |kbd0         Defined   00-00-0K-00  United States keyboard                      |
      |lb0          Available 00-02-00-20  TIVSM Library                               |
      |lo0          Available              Loopback Network Interface                  |
      |loglv00      Defined                Logical volume                              |
      |lp0          Available 00-00-0P-00  IBM 4201 Model 3 Proprinter III             |
      |lv03         Defined                Logical volume                              |
      |lv04         Defined                Logical volume                              |
      |lvdd         Available              N/A                                         |
      |mem0         Available 00-0B        8 MB Memory Card                            |
      |mem1         Available 00-0C        16 MB Memory Card                           |
      |mous0        Defined   00-00-0M-00  3 button mouse                              |
      |mt0          Available 00-02-00-40  TIVSM Tape Drive                            |
      |ppa0         Available 00-00-0P     Standard I/O Parallel Port Adapter          |
      |pty0         Available              Asynchronous Pseudo-Terminal                |
      |rootvg       Defined                Volume group                                |
      |sa0          Available 00-00-S1     Standard I/O Serial Port 1                  |
      |sa1          Available 00-00-S2     Standard I/O Serial Port 2                  |
      |scsi0        Available 00-01        SCSI I/O Controller                         |
      |scsi1        Available 00-02        SCSI I/O Controller                         |
      |sio0         Available 00-00        Standard I/O Planar                         |
      |siokb0       Available 00-00-0K     Keyboard Adapter                            |
      |sioms0       Available 00-00-0M     Mouse Adapter                               |
      |siotb0       Available 00-00-0T     Tablet Adapter                              |
      |sys0         Available 00-00        System Object                               |
      |sysplanar0   Available 00-00        CPU Planar                                  |
      |sysunit0     Available 00-00        System Unit                                 |
      |tok0         Available 00-03        Token-Ring High-Performance Adapter         |
      |tr0          Available              Token Ring Network Interface                |
      |tty0         Available 00-00-S1-00  Asynchronous Terminal                       |
      |tty1         Available 00-00-S2-00  Asynchronous Terminal                       |
      |usrvice      Defined                Logical volume                              |
      |veggie2      Defined                Volume group                                |
      |logical volumes by volume group                                                 |
      |veggie2:                                                                        |
      |LV NAME             TYPE       LPs   PPs  PVs  LV STATE      MOUNT POINT        |
      |hd2                 jfs        103   103  1    open/syncd    /usr               |
      |hd1                 jfs        1     1    1    open/syncd    /home              |
      |hd3                 jfs        3     3    1    open/syncd    /tmp               |
      |hd9var              jfs        1     1    1    open/syncd    /var               |
      |file systems                                                                    |
      |Filesystem    Total KB    free %used   iused %iused Mounted on                  |
      |/dev/hd4          8192     420   94%     909    44% /                           |
      |/dev/hd9var       4096    2972   27%      87     8% /var                        |
      |/dev/hd2        421888   10964   97%   17435    16% /usr                        |
      |/dev/hd3         12288   11588    5%      49     1% /tmp                        |
      |/dev/hd1          4096    3896    4%      26     2% /home                       |
      +--------------------------------------------------------------------------------+

    4. With the necessary recovery information now available, the administrator successfully restores each client machine.

Summary of Tivoli Disaster Recovery Manager Use

This section summarizes the use of DRM during routine operations and during disaster recovery:

Setup
  1. License DRM
  2. Ensure the device configuration and volume history files exist.
  3. Back up the storage pools.
  4. Do a full backup the database (for example, a database snapshot backup).
  5. Define site-specific server recovery instructions.
  6. Describe priority TSM client machines.
  7. Generate the disaster recovery plan.

Daily Operations
Day 1
  1. Back up client files.
  2. Back up the primary storage pools.
  3. Back up the database (for example, a database snapshot backup).
  4. Mark the backup volumes as unavailable to TSM.
  5. Send the backup volumes and disaster recovery plan file to the vault.
  6. Generate the disaster recovery plan.

Day 2

  1. Back up client files
  2. Back up the primary storage pools.
  3. Back up the database (for example, a database snapshot backup).
  4. Mark the backup volumes as unavailable to TSM.
  5. Send the backup volumes and disaster recovery plan file to the vault.
  6. Generate the disaster recovery plan.

Day 3

  1. Automatic storage pool reclamation processing occurs.
  2. Back up client files.
  3. Back up the primary storage pools.
  4. Back up the database (for example, a database snapshot backup).
  5. Send the backup volumes and a list of expired volumes to be reclaimed to the vault.
  6. The vault acknowledges receipt of the volumes sent on the previous day.
  7. Generate the disaster recovery plan.

Disaster and Recovery
Day 4
  1. The server and the client machines are destroyed.
  2. Restore the server using the latest recovery plan.
  3. Identify the top priority client nodes at the disaster site.
  4. Restore client machine files from the copy storage pools.
  5. Restore the primary storage pools.
  6. Move database backup and copy storage pool volumes to the vault.

Daily Operations
Day 5
  1. Back up client files.
  2. Back up the primary storage pools.
  3. Back up the database (for example, a database snapshot backup).
  4. Send the backup volumes and a list of expired volumes to be reclaimed to the vault.
  5. Generate the disaster recovery plan.

Tivoli Disaster Recovery Manager Checklist

The following checklist can help you set up Tivoli Disaster Recovery Manager.

Table 23. Tivoli Disaster Recovery Manager Checklist

Activity Start Date End Date Status Person Resp. Backup Person
Plan for DRM




Evaluate your disaster recovery requirements
  • What are the business priorities for recovering your clients?
  • Where is the recovery site?
  • Is the recovery site hot, warm, or cold?
  • Do the clients have connectivity to recovery server?
  • Who are the system and TSM administrators?
  • Will you need to return to the original site?
  • Where are the offsite backups stored?
  • How does the vault handle the backup media?
  • How are the backups packaged or processed?
  • Who provides the courier service?





Evaluate the current storage pool backup implementation
  • What primary storage pools are being backed up?
  • When are the backups performed?
  • Backup purpose: offsite or onsite
  • Backup media: Will snapshot database backups or full plus incremental database backups be used?
  • Naming conventions for replacement volumes for primary storage pools





Evaluate the current database backup implementation
  • When are the backups performed?
  • Backup purpose: offsite or onsite
  • Backup media
  • How long do you want to keep backup series? Review the copy storage pool REUSEDELAY value and verify that it is the same as the SET DRMDBBACKUPEXPIREDAYS value.





Determine which primary storage pools are to be managed by DRM




Determine which copy storage pools are to be managed by DRM
  • Offsite copy storage pools





Where to Save the Recovery Plan File

Stored Locally:

  • What is the recovery plan file dsname prefix?
  • How will recovery plan files be made available at the recovery site?
    • Print and store offsite
    • Tape/diskette copy stored offsite
    • Copy sent/NFS to recovery site

Stored on Another Server:

  • What server is to be used as the target server?

  • What is the name of the target server's device class?

  • How long do you want to keep recovery plan files?





Determine where you want to create the user-specified recovery instructions

What is the prefix of the instructions dsname?






Evaluate the TMS/DRM interaction options
  • Will DRM drive the backup volume movement?
  • Will TMS drive the backup volume movement?
  • How to notify the other of volume movement?
  • What TMS policies need to be created?





Analyze the sequence of steps related to the PREPARE command backup movement

Document the flow of activities and timings

  • Sending of volumes offsite
  • Return of empty volumes
  • PREPARE timing





Installation




Receive and Install the TSM code




License DRM
  • REGISTER LICENSE or
  • Update the server options





Customize DRM

The administrator with system authority issues:

  • SET DRMDBBACKUPEXPIREDAYS to define the Database backup expiration
  • SET DRMPRIMSTGPOOL to specify the DRM-managed primary storage pools
  • SET DRMCOPYSTGPOOL to specify the DRM-managed copy storage pools
  • SET DRMPLANVPOSTFIX to specify 1 character to be appended to new storage pools
  • SET DRMPLANPREFIX to specify the RPF prefix
  • SET DRMINSTRPREFIX to specify the user instruction file prefix
  • SET DRMNOTMOUNTABLENAME to specify the default location for media to be sent offsite
  • SET DRMCOURIERNAME to specify the default courier
  • SET DRMVAULTNAME to specify the default vault
  • SET DRMCMDFILENAME to specify the default file name to contain the commands specified with the CMD parameter on MOVE and QUERY DRMEDIA
  • SET DRMRPFEXPIREDAYS to specify a value other than the default of 60 days for the frequency of RPF expiration (when plan files are stored on another server)





Define the site-specific recovery instructions

Identify:

  • Target disaster recovery server location
  • Target server software requirements
  • Target server hardware requirements (storage devices)
  • TSM administrator contact
  • Courier name and telephone number
  • Vault location and contact person

Create:

  • Enter the site-specific recovery instructions data into files created in the same as specified by SET DRMINSTRPREFIX





Test Tivoli Disaster Recovery Manager




Test the installation and customization
  • Q DRMSTATUS to display the DRM setup
  • Back up the primary storage pools
  • Back up the TSM database
  • Q DRMEDIA to list the backup volumes
  • MOVE DRMEDIA to move offsite
  • PREPARE to create the recovery plan file





Examine the recovery plan file created




Test the recovery plan file break out
  • REXX exec ANRPLANX
  • Locally written procedure





Put DRM into Production




Set up the schedules for automated functions




Implement the DRM procedures





[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]