Tivoli Storage Manager for Sun Solaris Administrator's Guide


Recovering From a Disaster

This section provides an overview of the tasks involved in recovering the server and clients. It also presents scenarios of both procedures.

Recovering the Server: Here are guidelines for recovering your server:

  1. Obtain the latest disaster recovery plan file.
  2. Break out the file to view, update, print, or run as macros or scripts (for example, batch programs or batch files).
  3. Obtain the backup volumes from the vault.
  4. Locate a suitable replacement machine.
  5. Restore the operating system and TSM to your replacement machine.
  6. Review the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE RECOVERY.SCRIPT.NORMAL.MODE scripts because they are important for restoring the server to a point where clients can be recovered (see Disaster Recovery Mode Stanza).

Recovering the Clients: To recover clients, do the following:

  1. Get the following information by querying the recovered database:
  2. With this information restore the client machines.

Server Recovery Scenario

Here is the procedure for a complete recovery of the server after a disaster has destroyed it. In this example virtual volumes are not used. The steps are performed by the onsite administrator unless otherwise indicated.

  1. Review the recovery steps described in the RECOVERY.INSTRUCTIONS.GENERAL stanza of the plan.
  2. Request the server backup tapes from the offsite vault.
  3. 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 or scripts.
  4. Print the RECOVERY.VOLUMES.REQUIRED file. Give the printout to the courier to retrieve the backup volumes.
  5. Find a replacement server. The RECOVERY.DEVICES.REQUIRED stanza specifies the device type that is needed to read the backups. The SERVER.REQUIREMENTS stanza specifies the disk space required.
  6. Restore the operating system and the TSM server software on the replacement server. The media names and their locations are specified in the RECOVERY.INSTRUCTIONS.INSTALL stanza and the MACHINE.RECOVERY.MEDIA.REQUIRED stanza. Ensure that the environment is the same as when the disaster recovery plan file was created. The environment includes:
  7. Review the TSM macros contained in the recovery plan.

    If, at the time of the disaster, the courier had not picked up the previous night's database and storage pool incremental backup volumes but they were not destroyed, remove the entry for the storage pool backup volumes from the COPYSTGPOOL.VOLUMES.DESTROYED file.

  8. If some required storage pool backup volumes could not be retrieved from the vault, remove the volume entries from the COPYSTGPOOL.VOLUMES.AVAILABLE file.
  9. If all primary volumes were destroyed, no changes are required to the PRIMARY.VOLUMES script and TSM macro files.
  10. Review the device configuration file to ensure that the hardware configuration at the recovery site is the same as the original site. Any differences must be updated in the device configuration file. Examples of configuration changes that require updates to the configuration information are:

    For information about updating the device configuration file, see Updating the Device Configuration File.

  11. To restore the database to a point where clients can be recovered, invoke the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script file. Enter the script file name at the command prompt. As an alternative, you can use the recovery script as a guide and manually issue the steps.

    The following are some sample steps from a recovery script:

    1. Copy the TSM server options file from the DSMSERV.OPT file to its original location.
    2. Copy the volume history file required by database restore processing from the VOLUME.HISTORY.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 database restore processing from the DEVICE.CONFIGURATION.FILE file to its original location.
    4. Create the TSM server recovery log and database volumes using DSMFMT.
    5. Issue DSMSERV FORMAT command to format the recovery log and database files.
    6. Issue the DSMSERV RESTORE DB command.
    7. Start the server.
    8. Register TSM server licenses.
    9. Mark copy storage pool volumes retrieved from vault as available.
    10. Mark copy storage pool volumes that cannot be obtained as unavailable.
    11. Mark primary storage pool volumes as destroyed.

    Notes:

    1. Due to changes in hardware configuration during recovery, you might have to update the device configuration file located in the restored TSM database (see Updating the Device Configuration File).

    2. You can mount copy storage pool volumes upon request, check in the volumes in advance, or manually place the volumes in the library and ensure consistency by issuing the AUDIT LIBRARY command.

    3. Use the AUDIT LIBRARY command to ensure that the restored TSM database is consistent with the automated library volumes.
  12. If client machines are not damaged, invoke the RECOVERY.SCRIPT.NORMAL.MODE script file to restore the server primary storage pools. If client machines are damaged, you may want to delay this action until after all clients are recovered.
    Note:This action is optional because TSM can access the copy storage pool volumes directly to restore client data. Using this feature, you can minimize client recovery time because server primary storage pools do not have to be restored first. However, in this scenario, the client machines were not damaged, so the focus of the administrator is to restore full TSM server operation.

    As an alternative, you can use the recovery script as a guide and manually run each step. The steps run in this script are :

    1. Create replacement primary volumes.
    2. Define the replacement primary volumes to TSM.
    3. Restore the primary storage pools.
  13. Collect the database backup and copy storage pool volumes used in the recovery for return to the vault. For these backup volumes to be returned to the vault using the routine MOVE DRMEDIA process, issue the following commands:
    update volhist TPBK50 devcl=lib8mm ormstate=mountable
    update volhist TPBK51 devcl=lib8mm ormstate=mountable
    

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

  14. Issue the BACKUP DB command to back up the newly restored database.
  15. Issue the following command to check the volumes out of the library:
     move drmedia * wherestate=mountable
    
  16. Create a list of the volumes to be given to the courier:
    query drmedia * wherestate=notmountable 
    
  17. Give the volumes to the courier and issue the following command:
    move drmedia * wherestate=notmountable
    
  18. Issue the PREPARE command.

Client Recovery Scenario

The following scenario demonstrates the recovery of clients.

  1. 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
    

    DRM 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, issue the following commands:
    1. Determine the location of the boot media. For example:
      query recoverymedia mksysb1
      

      The server displays the following information:

      +--------------------------------------------------------------------------------+
      |Recovery Media Name  Volume Names    Location    Machine Name                   |
      |-------------------- -----------     ----------  ----------------               |
      |MKSYSB1              vol1 vol2       IRONVAULT    POLARIS                       |
      |                      vol3                                                      |
      +--------------------------------------------------------------------------------+
    2. Determine the machine-specific recovery instructions. For example:
      query machine polaris format=recoveryinstructions
      

      The server 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. Determine the machine hardware requirements. For example:
      query machine polaris format=characteristics
      

      The server 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                       |
      +--------------------------------------------------------------------------------+
  3. With the information obtained, restore each client machine.


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