The disaster recovery plan file contains the information required to recover a TSM server to the point in time represented by the last database backup operation that is completed before the plan is created. The plan is organized into stanzas, which you can break out into multiple files.
You can use an awk script or an editor to break out the stanzas into individual files. A sample procedure, planexpl.awk.smp, is shipped with DRM and is located in /opt/tivoli/tsm/server/bin/> or wherever the server resides. You can modify this procedure for your installation. Store a copy of the procedure offsite for recovery.
The disaster recovery plan is divided into the following types of stanzas:
Note: | The RECOVERY.SCRIPT.NORMAL.MODE and RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE stanzas contain the commands that invoke the scripts and macros contained in the other stanzas. |
Table 22 lists the recovery plan file stanzas, and indicates what type of administrative processing is required during set up, routine operations, and disaster recovery. The table also indicates whether the stanza contains a macro, a script, or a configuration file.
Note: | For tasks identified as During setup or periodic updates, DRM automatically collects this information for the plan. |
Table 22. Administrative Tasks Associated with the Disaster Recovery Plan File
Stanza Name | Tasks |
---|---|
PLANFILE.DESCRIPTION | -- |
PLANFILE.TABLE.OF.CONTENTS | -- |
SERVER.REQUIREMENTS | -- |
RECOVERY.INSTRUCTIONS.GENERAL | During setup or periodic updates: Edit the source file associated with the stanza (optional) |
RECOVERY.INSTRUCTIONS.OFFSITE | During setup or periodic updates: Edit the source file associated with the stanza (optional) |
RECOVERY.INSTRUCTIONS.INSTALL | During setup or periodic updates: Edit the source file associated with the stanza (optional) |
RECOVERY.INSTRUCTIONS.DATABASE | During setup or periodic updates: Edit the source file associated with the stanza (optional) |
RECOVERY.INSTRUCTIONS.STGPOOL | During setup or periodic updates: Edit the source file associated with the stanza (optional) |
RECOVERY.VOLUMES.REQUIRED | During routine processing: MOVE DRMEDIA |
RECOVERY.DEVICES.REQUIRED | -- |
RECOVERY.SCRIPT. DISASTER.RECOVERY.MODE script | During disaster recovery: Edit and run (optional) |
RECOVERY.SCRIPT. NORMAL.MODE script | During disaster recovery: Edit and run (optional) |
LOGANDDB.VOLUMES.CREATE script | During disaster recovery: Edit and run (optional) |
LOG.VOLUMES | During disaster recovery: Optionally edit/copy |
DB.VOLUMES | During disaster recovery: Optionally edit/copy |
LOGANDDB.VOLUMES.INSTALL script | During disaster recovery: Edit and run (optional) |
LICENSE.REGISTRATION macro | During disaster recovery: Edit and run (optional) |
COPYSTGPOOL.VOLUMES.AVAILABLE macro | During routine processing: MOVE DRMEDIA
During disaster recovery: Edit and run (optional) |
COPYSTGPOOL.VOLUMES.DESTROYED macro | During routine processing: MOVE DRMEDIA
During disaster recovery: Edit and run (optional) |
PRIMARY.VOLUMES.DESTROYED macro | During disaster recovery: Edit and run (optional) |
PRIMARY.VOLUMES.REPLACEMENT.CREATE script | During disaster recovery: Edit and run (optional) |
PRIMARY.VOLUMES.REPLACEMENT macro | During disaster recovery: Edit and run (optional) |
STGPOOLS.RESTORE macro | During disaster recovery: Edit and run (optional) |
VOLUME.HISTORY.FILE configuration file | During disaster recovery: Copy (optional) |
DEVICE.CONFIGURATION.FILE configuration file | During disaster recovery: Edit and copy (optional) |
DSMSERV.OPT.FILE configuration file | During disaster recovery: Edit and copy (optional) |
LICENSE.INFORMATION | -- |
MACHINE.GENERAL.INFORMATION | During setup or periodic updates: Issue DEFINE MACHINE ADSMSERVER=YES (optional) |
MACHINE.RECOVERY.INSTRUCTIONS | During setup or periodic updates: Issue INSERT MACHINE RECOVERYINSTRUCTIONS (optional) |
MACHINE.RECOVERY.CHARACTERISTICS | During setup or periodic updates: Issue INSERT MACHINE CHARACTERISTICS (optional) |
MACHINE.RECOVERY.MEDIA | During setup or periodic updates: Issue DEFINE RECOVERYMEDIA and DEFINE RECMEDMACHASSOCIATION (optional) |
This section contains an example of a disaster recovery plan file and information about each stanza. The disaster recovery plan file has been divided into separate figures that correlate to the descriptions of specific stanzas within each figure.
PLANFILE.DESCRIPTION
Identifies the server for this recovery plan, and the date and time the plan is created.
Figure 84. Description Stanza
+--------------------------------------------------------------------------------+
|begin PLANFILE.DESCRIPTION |
| |
|Recovery Plan for Server DESIGN_DEPARTMENT |
|Created by DRM PREPARE on 02/11/2000 10:20:34 |
|DRM PLANPREFIX /prepare/ |
|Server for HP-UX - Version 4, Release 1, Level x.x/x.x |
| |
|end PLANFILE.DESCRIPTION |
| |
+--------------------------------------------------------------------------------+
PLANFILE.TABLE.OF.CONTENTS
Lists the stanzas documented in this plan.
Figure 85. Table of Contents Stanza
+--------------------------------------------------------------------------------+
| begin PLANFILE.TABLE.OF.CONTENTS |
| |
|PLANFILE.DESCRIPTION |
|PLANFILE.TABLE.OF.CONTENTS |
| |
|Server Recovery Stanzas: |
| SERVER.REQUIREMENTS |
| RECOVERY.INSTRUCTIONS.GENERAL |
| RECOVERY.INSTRUCTIONS.OFFSITE |
| RECOVERY.INSTRUCTIONS.INSTALL |
| RECOVERY.VOLUMES.REQUIRED |
| RECOVERY.DEVICES.REQUIRED |
| RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script |
| RECOVERY.SCRIPT.NORMAL.MODE script |
| LOGANDDB.VOLUMES.CREATE script |
| LOG.VOLUMES |
| DB.VOLUMES |
| LOGANDDB.VOLUMES.INSTALL script |
| LICENSE.REGISTRATION macro |
| COPYSTGPOOL.VOLUMES.AVAILABLE macro |
| COPYSTGPOOL.VOLUMES.DESTROYED macro |
| PRIMARY.VOLUMES.DESTROYED macro |
| PRIMARY.VOLUMES.REPLACEMENT.CREATE script |
| PRIMARY.VOLUMES.REPLACEMENT macro |
| STGPOOLS.RESTORE macro |
| VOLUME.HISTORY.FILE |
| DEVICE.CONFIGURATION.FILE |
| DSMSERV.OPT.FILE |
| |
|Machine Description Stanzas: |
| MACHINE.GENERAL.INFORMATION |
| MACHINE.RECOVERY.INSTRUCTIONS |
| MACHINE.CHARACTERISTICS |
| MACHINE.RECOVERY.MEDIA.REQUIRED |
| |
|end PLANFILE.TABLE.OF.CONTENTS |
| |
+--------------------------------------------------------------------------------+
SERVER.REQUIREMENTS
Identifies the database and recovery log storage requirements for the server. The replacement server must have enough disk space to install the database and recovery log volumes. This stanza also identifies the directory where the server executable resided when the server was started. If the server executable is in a different directory on the replacement server, edit the plan file to account for this change.
If you use links to the server executable file, you must create the links on the replacement machine or modify the following plan file stanzas:
Figure 86. Server Requirements Stanza
+--------------------------------------------------------------------------------+
| begin SERVER.REQUIREMENTS |
| |
|Database Requirements Summary: |
| |
| Available Space (MB): 20 |
| Assigned Capacity (MB): 20 |
| Pct. Utilization: 2.2 |
|Maximum Pct. Utilization: 2.2 |
| Physical Volumes: 2 |
| |
|Recovery Log Requirements Summary: |
| |
| Available Space (MB): 20 |
| Assigned Capacity (MB): 20 |
| Pct. Utilization: 4.4 |
|Maximum Pct. Utilization: 4.8 |
| Physical Volumes: 2 |
|Server Executable Directory: /opt/tivoli/tsm/server/bin |
|end SERVER.REQUIREMENTS |
+--------------------------------------------------------------------------------+
The administrator enters recovery instructions into source files that the PREPARE command includes in the plan files. See Specifying Recovery Instructions for Your Site for details.
Note: | In the following descriptions, prefix represents the prefix portion of the file name. See Specifying Defaults for the Disaster Recovery Plan File for details. |
RECOVERY.INSTRUCTIONS.GENERAL
Identifies site-specific instructions that the administrator has entered in the file identified by prefix RECOVERY.INSTRUCTIONS.GENERAL. The instructions should include the recovery strategy, key contact names, an overview of key applications backed up by this server, and other relevant recovery instructions.
Figure 87. Recovery Instructions General Stanza
+--------------------------------------------------------------------------------+
|begin RECOVERY.INSTRUCTIONS.GENERAL |
| |
| This server contains the backup and archive data for FileRight Company |
| accounts receivable system. It also is used by various end users in the |
| finance and materials distribution organizations. |
| The storage administrator in charge of this server is Jane Doe 004-001-0006. |
| If a disaster is declared, here is the outline of steps that must be completed.|
| 1. Determine the recovery site. Our alternate recovery site vendor is IBM |
| BRS in Tampa, Fl, USA 213-000-0007. |
| 2. Get the list of required recovery volumes from this recovery plan file |
| and contact our offsite vault so that they can start pulling the |
| volumes for transfer to the recovery site. |
| 3. etc... |
| |
|end RECOVERY.INSTRUCTIONS.GENERAL |
| |
+--------------------------------------------------------------------------------+
RECOVERY.INSTRUCTIONS.OFFSITE
Contains instructions that the administrator has entered in the file identified by prefix RECOVERY.INSTRUCTIONS.OFFSITE. The instructions should include the name and location of the offsite vault, and how to contact the vault (for example, a name and phone number).
Figure 88. Recovery Instructions Offsite Stanza
+--------------------------------------------------------------------------------+
|begin RECOVERY.INSTRUCTIONS.OFFSITE |
| |
| Our offsite vaulting vendor is OffsiteVault Inc. |
| Their telephone number is 514-555-2341. Our account rep is Joe Smith. |
| Our account number is 1239992. Their address is ... |
| Here is a map to their warehouse ... |
| Our courier is ... |
| |
|end RECOVERY.INSTRUCTIONS.OFFSITE |
+--------------------------------------------------------------------------------+
RECOVERY.INSTRUCTIONS.INSTALL
Contains instructions that the administrator has entered in the file identified by prefix RECOVERY.INSTRUCTIONS.INSTALL. The instructions should include how to rebuild the base server machine and the location of the system image backup copies.
Figure 89. Recovery Instructions Install Stanza
+--------------------------------------------------------------------------------+
| begin RECOVERY.INSTRUCTIONS.INSTALL |
| |
| The base server system is HP-UX 11.00 running on an |
| HP 800/G60 9000. The HP-UX 11.00 operating system |
| and product installation media is stored at the vault. |
| There is also a copy in bldg 24 room 4 cabinet a. The system |
| administrator responsible for the HP-UX 11.00 and installation |
| is Fred Myers. |
| |
|end RECOVERY.INSTRUCTIONS.INSTALL |
+--------------------------------------------------------------------------------+
RECOVERY.INSTRUCTIONS.DATABASE
Contains instructions that the administrator has entered in the file identified by prefix RECOVERY.INSTRUCTIONS.DATABASE. The instructions should include how to prepare for the database recovery. For example, you may enter instructions on how to initialize or load the backup volumes for an automated library. No sample of this stanza is provided.
RECOVERY.INSTRUCTIONS.STGPOOL
Contains instructions that the administrator has entered in the file identified by prefix RECOVERY.INSTRUCTIONS.STGPOOL. The instructions should include the names of your software applications and the copy storage pool names containing the backup of these applications. No sample of this stanza is provided.
RECOVERY.VOLUMES.REQUIRED
Provides a list of the database backup and copy storage pool volumes required to recover the server. This list can include both virtual volumes and nonvirtual volumes. A database backup volume is included if it is part of the most recent database backup series. A copy storage pool volume is included if it is not empty and not marked destroyed.
If you are using a nonvirtual volume environment and issuing the MOVE DRMEDIA command, a blank location field means that the volumes are onsite and available to the server. This volume list can be used in periodic audits of the volume inventory of the courier and vault. You can use the list to collect the required volumes before recovering the server.
For virtual volumes, the location field contains the target server name.
Figure 90. Volume Requirements Stanza
+--------------------------------------------------------------------------------+
| begin RECOVERY.VOLUMES.REQUIRED |
| |
|Volumes required for data base restore |
| Location = OffsiteVault Inc. |
| Device Class = LIB8MM |
| Volume Name = |
| TPBK08 |
| Location = OffsiteVault Inc. |
| Device Class = LIB8MM |
| Volume Name = |
| TPBK06 |
| |
|Volumes required for storage pool restore |
| Location = OffsiteVault Inc. |
| Copy Storage Pool = CSTORAGEPF |
| Device Class = LIB8MM |
| Volume Name = |
| TPBK05 |
| TPBK07 |
| |
|end RECOVERY.VOLUMES.REQUIRED |
+--------------------------------------------------------------------------------+
RECOVERY.DEVICES.REQUIRED
Provides details about the devices needed to read the backup volumes.
Figure 91. Volume and Device Requirements Stanzas
+--------------------------------------------------------------------------------+
|begin RECOVERY.DEVICES.REQUIRED |
| |
| Purpose: Description of the devices required to read the |
| volumes listed in the recovery volumes required stanza. |
| |
| Device Class Name: LIB8MM |
| Device Access Strategy: Sequential |
| Storage Pool Count: 2 |
| Device Type: GENERICTAPE |
| Format: DRIVE |
| Est/Max Capacity (MB): 4.0 |
| Mount Limit: 2 |
| Mount Wait (min): 60 |
| Mount Retention (min): 10 |
| Label Prefix: TIVSM |
| Library: RLLIB |
| Directory: |
|Last Update by (administrator): Bill |
| Last Update Date/Time: 12/11/2000 10:18:34 |
| |
|end RECOVERY.DEVICES.REQUIRED |
+--------------------------------------------------------------------------------+
RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE
Contains a script with the commands needed to recover the server. You can use the script as a guide and run the commands from a command line. Or you can copy it to a file, modify it and the files it refers to, and run the script. You may need to modify the script because of differences between the original and the replacement systems. At the completion of these steps, client requests for file restores are satisfied directly from copy storage pool volumes.
The disaster recovery plan issues commands using the administrative client. The disaster recovery plan file issues commands using the administrative client. Ensure that the path to the administrative client is established before running the script. For example, set the shell variable PATH or update the scripts with the path specification for the administrative client.
The commands in the script do the following:
Attention: When this script runs, any log volumes or database volumes with the same names as those named in the plan are removed (see LOGANDDB.VOLUMES.CREATE under Create and Install Database and Recovery Log Volumes Stanzas). In most disaster recoveries, the TSM server is installed on a new machine. When this script is run, it is assumed that there is no TSM data in the log or database volumes. TSM installation includes the creation of database and recovery log volumes. If you have created a log volume or a database volume (for example, for testing), and you want to preserve the contents, you must take some action such as renaming the volume or copying the contents before executing this script.
To help understand the operations being performed in this script, see Backup and Recovery Scenarios.
To invoke this script, specify the following positional parameters:
Note: | The default location for dsm.sys is /opt/ivoli/tsm/client/admin/bin. |
For example, to invoke this script using an administrator ID of don, password of mox, server name of prodtsm, enter the following command:
planprefix/RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE don mox prodtsm
For more information, see the entry for the recovery plan prefix in Table 20.
Figure 92. Disaster Recovery Mode Script
+--------------------------------------------------------------------------------+
| begin RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script |
| |
|#!/bin/ksh |
|set -x |
| |
| # Purpose: This script contains the steps required to recover the server |
| # to the point where client restore requests can be satisfied |
| # directly from available copy storage pool volumes. |
| # Note: This script assumes that all volumes necessary for the restore have |
| # been retrieved from the vault and are available. This script assumes |
| # the recovery environment is compatible (essentially the same) as the |
| # original. Any deviations require modification to this script and the |
| # macros and shell scripts it runs. Alternatively, you can use this |
| # script as a guide, and manually execute each step. |
| |
|if [ -z "$1" -o -z "$2" -o -z "$3" ] |
|then |
| print "Specify the following positional parameters:" |
| print "administrative client ID, password, and server ID." |
| print "Script stopped." |
| exit |
|fi |
| # Set the server working directory |
|cd /opt/tivoli/tsm/server/bin/> |
| |
| # Restore server options, volume history, device configuration files. |
|cp /prepare/DSMSERV.OPT.FILE \ |
| /opt/tivoli/tsm/server/bin/>dsmserv.optx |
|cp /prepare/VOLUME.HISTORY.FILE \ |
| /opt/tivoli/tsm/server/bin/>volhistory.txtx |
|cp /prepare/DEVICE.CONFIGURATION.FILE \ |
| /opt/tivoli/tsm/server/bin/>devconfig.txtx |
| |
|export DSMSERV_CONFIG=/opt/tivoli/tsm/server/bin/>dsmserv.optx |
| |
|export DSMSERV_DIR=/opt/adsmserv/bin |
+--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+
| # Create and format log and database files. |
|/prepare/LOGANDDB.VOLUMES.CREATE 2>&1 \ |
|| tee /prepare/LOGANDDB.VOLUMES.CREATE.log |
| |
| # Initialize the log and database files. |
|/prepare/LOGANDDB.VOLUMES.INSTALL 2>&1 \ |
|| tee /prepare/LOGANDDB.VOLUMES.INSTALL.log |
| |
| # Restore the server database to latest version backed up per the |
| # volume history file. |
|/opt/tivoli/tsm/server/bin/>dsmserv restore db todate=08/11/2000 totime=10:20:22|
| |
| # Start the server. |
|nohup /opt/tivoli/tsm/server/bin/>dsmserv & |
|print Please start new server console with command dsmadmc -CONSOLE. |
|print Press enter to continue recovery script execution. |
|read pause |
| |
| # Register Server Licenses. |
|dsmadmc -id=$1 -pass=$2 -serv=$3 -ITEMCOMMIT |
| -OUTFILE=/prepare/LICENSE.REGISTRATION.log |
| macro /prepare/LICENSE.REGISTRATION.mac |
| |
| # Tell Server these copy storage pool volumes are available for use. |
| # Recovery Administrator: Remove from macro any volumes not obtained from vault.|
|dsmadmc -id=$1 -pass=$2 -serv=$3 -ITEMCOMMIT \ |
| -OUTFILE=/prepare/COPYSTGPOOL.VOLUMES.AVAILABLE.log \ |
| macro /prepare/COPYSTGPOOL.VOLUMES.AVAILABLE |
| |
| # Volumes in this macro were not marked as 'offsite' at the time |
| # PREPARE ran. They were likely destroyed in the disaster. |
| # Recovery Administrator: Remove from macro any volumes not destroyed. |
|dsmadmc -id=$1 -pass=$2 -serv=$3 -ITEMCOMMIT \ |
| -OUTFILE=/prepare/COPYSTGPOOL.VOLUMES.DESTROYED.log \ |
| macro /prepare/COPYSTGPOOL.VOLUMES.DESTROYED |
| # Mark primary storage pool volumes as ACCESS=DESTROYED. |
| # Recovery administrator: Remove from macro any volumes not destroyed. |
|dsmadmc -id=$1 -pass=$2 -serv=$3 -ITEMCOMMIT \ |
| -OUTFILE=/prepare/PRIMARY.VOLUMES.DESTROYED.log \ |
| macro /prepare/PRIMARY.VOLUMES.DESTROYED |
| |
|end RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script |
+--------------------------------------------------------------------------------+
RECOVERY.SCRIPT.NORMAL.MODE
Contains a script with the commands needed to restore the server primary storage pools. You can use the script as a guide and run the commands from a command line. Or you can copy it to a file, modify it and the files it refers to, and run the script. You may need to modify the script because of differences between the original and the replacement systems.
The disaster recovery plan issues commands using the administrative client. The disaster recovery plan file issues commands using the administrative client. Ensure that the path to the administrative client is established before running the script. For example, set the shell variable PATH or update the scripts with the path specification for the administrative client.
At the completion of these steps, client requests for file restores are satisfied from primary storage pool volumes. Clients should also be able to resume file backup, archive, and migration functions.
This script invokes the script contained in the PRIMARY.VOLUMES.REPLACEMENT.CREATE stanza: It also invokes the macros contained in the following stanzas:
To help understand the operations being performed in this script, see Backup and Recovery Scenarios.
To invoke this script, the following positional parameters must be specified:
For example, to invoke this script using an administrator ID of don, password of mox, server name of prodtsm, enter the following command:
planprefix/RECOVERY.SCRIPT.NORMAL.MODE don mox prodtsm
For more information, see the entry for the recovery plan prefix in Table 20.
Figure 93. Normal Mode Script
+--------------------------------------------------------------------------------+
|begin RECOVERY.SCRIPT.NORMAL.MODE script |
|#!/bin/ksh |
|set -x |
| |
| # Purpose: This script contains the steps required to recover the server |
| # primary storage pools. This mode allows you to return the |
| # copy storage pool volumes to the vault and to run the |
| # server as normal. |
| # Note: This script assumes that all volumes necessary for the restore |
| # have been retrieved from the vault and are available. This script |
| # assumes the recovery environment is compatible (essentially the |
| # same) as the original. Any deviations require modification to this |
| # script and the macros and shell scripts it runs. Alternatively, |
| # you can use this script as a guide, and manually execute each step. |
| |
|if [ -z "$1" -o -z "$2" -o -z "$3" ] |
|then |
| print "Specify the following positional parameters:" |
| print "administrative client ID, password, and server ID." |
| print "Script stopped." |
| exit |
|fi |
| |
| # Create replacement volumes in the primary storage pools (If any |
| # are implemented as disk but not logical volume.) |
| # Recovery administrator: Edit script for your replacement volumes. |
|/prepare/PRIMARY.VOLUMES.REPLACEMENT.CREATE 2>&1 \ |
|| tee /prepare/PRIMARY.VOLUMES.REPLACEMENT.CREATE.log |
| |
| # Define replacement volumes in the primary storage pools. Must |
| # have different name than original. |
| # Recovery administrator: Edit macro for your replacement volumes. |
|dsmadmc -id=$1 -pass=$2 -serv=$3 -ITEMCOMMIT \ |
| -OUTFILE=/prepare/PRIMARY.VOLUMES.REPLACEMENT.log \ |
| macro /prepare/PRIMARY.VOLUMES.REPLACEMENT |
| |
| # Restore the primary storage pools from the copy storage pools. |
|dsmadmc -id=$1 -pass=$2 -serv=$3 -ITEMCOMMIT \ |
| -OUTFILE=/prepare/STGPOOLS.RESTORE.log \ |
| macro /prepare/STGPOOLS.RESTORE |
| |
|end RECOVERY.SCRIPT.NORMAL.MODE script |
+--------------------------------------------------------------------------------+
LOGANDDB.VOLUMES.CREATE
Contains a script with the commands needed to recreate the database and log volumes. You can use the script as a guide and issue the commands as needed from a command line, or you can copy it to a file, modify it, and run it. This script is invoked by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.
The plan assumes that the volume formatting command (DSMFMT) resides in the same directory as the server executable indicated in the stanza SERVER.REQUIREMENTS.
Figure 94. Create Database and Recovery Log Volumes Stanza
+--------------------------------------------------------------------------------+
|begin LOGANDDB.VOLUMES.CREATE script |
|#!/bin/ksh |
|set -x |
| # Purpose: Create log and database volumes. |
| # Recovery Administrator: Run this to format server log and |
| # database volumes. |
| print Remove database volume /opt/tivoli/tsm/server/bin/>db01x. |
| rm -f /opt/tivoli/tsm/server/bin/>db01x |
| |
| print Create database volume /opt/tivoli/tsm/server/bin/>db01x 12M |
| /opt/tivoli/tsm/server/bin/>dsmfmt -m -db /opt/tivoli/tsm/server/bin/>db01x 12M|
| |
| print Remove database volume /opt/tivoli/tsm/server/bin/>db02x. |
| rm -f /opt/tivoli/tsm/server/bin/>db02x |
| |
| print Create database volume /opt/tivoli/tsm/server/bin/>db02x 8M |
| /opt/tivoli/tsm/server/bin/>dsmfmt -m -db /opt/tivoli/tsm/server/bin/>db02x 8 |
| |
| print Remove log volume /opt/tivoli/tsm/server/bin/>lg01x. |
| rm -f /opt/tivoli/tsm/server/bin/>lg01x |
| |
| print Create log volume /opt/tivoli/tsm/server/bin/>lg01x 12M |
| /opt/tivoli/tsm/server/bin/>dsmfmt -m -log /opt/tivoli/tsm/server/bin/>lg01x 12|
| |
| print Remove log volume /opt/tivoli/tsm/server/bin/>lg02x. |
| rm -f /opt/tivoli/tsm/server/bin/>..lg02x |
| |
| print Create log volume /opt/tivoli/tsm/server/bin/>lg02x 8M |
| /opt/tivoli/tsm/server/bin/>dsmfmt -m -log /opt/tivoli/tsm/server/bin/>lg02x 8 |
| |
|end LOGANDDB.VOLUMES.CREATE script |
+--------------------------------------------------------------------------------+
LOG.VOLUMES
Contains the names of the log volumes to be initialized. The contents of this stanza must be placed into a separate file to be used by the LOGANDDB.VOLUMES.INSTALL script.
Figure 95. Recovery Log Volumes Stanza
+--------------------------------------------------------------------------------+
|begin LOG.VOLUMES |
|/opt/tivoli/tsm/server/bin/>lg01x |
|/opt/tivoli/tsm/server/bin/>lg02x |
| |
|end LOG.VOLUMES |
+--------------------------------------------------------------------------------+
DB.VOLUMES
Contains the names of the database volumes to be initialized. The contents of this stanza must be placed into a separate file to be used by the LOGANDDB.VOLUMES.INSTALL script.
Figure 96. Database Volume Stanza
+--------------------------------------------------------------------------------+
|begin DB.VOLUMES |
| |
|/opt/tivoli/tsm/server/bin/>db01x |
|/opt/tivoli/tsm/server/bin/>db02x |
| |
|end DB.VOLUMES |
| |
+--------------------------------------------------------------------------------+
LOGANDDB.VOLUMES.INSTALL
Contains a script with the commands required to initialize the database and log volumes. This script is invoked by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.
Figure 97. Install Database and Recovery Log Volumes Stanza
+--------------------------------------------------------------------------------+
| begin LOGANDDB.VOLUMES.INSTALL script |
| |
|#!/bin/ksh |
|set -x |
| |
| # Purpose: Initialize the log and database volumes. |
| # Recovery Administrator: Run this to initialize an server. |
| |
| /opt/tivoli/tsm/server/bin/>dsmserv install \ |
| 2 FILE:/prepare/LOG.VOLUMES \ |
| 2 FILE:/prepare/DB.VOLUMES |
| |
|end LOGANDDB.VOLUMES.INSTALL script |
+--------------------------------------------------------------------------------+
LICENSE.REGISTRATION
Contains a macro to register your server licenses. This macro is invoked by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.
Figure 98. License Registration Macro Stanza
+--------------------------------------------------------------------------------+
|begin LICENSE.REGISTRATION macro |
| |
| /* Purpose: Register the Server licenses by specifying the names */ |
| /* of the enrollment certificate files necessary to recreate the */ |
| /* licenses that existed in the server. */ |
| /* Recovery Administrator: Review licenses and add or delete licenses */ |
| /* as necessary. */ |
| |
|register license file(50client.lic) |
|register license file(network.lic) |
|register license file(drm.lic) |
| |
|end LICENSE.REGISTRATION macro |
+--------------------------------------------------------------------------------+
COPYSTGPOOL.VOLUMES.AVAILABLE
Contains a macro to mark copy storage pool volumes that were moved offsite and then moved back onsite. This stanza does not include copy storage pool virtual volumes. You can use the information as a guide and issue the administrative commands, or you can copy it to a file, modify it, and run it. This macro is invoked by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.
After a disaster, compare the copy storage pool volumes listed in this stanza with the volumes that were moved back onsite. You should remove entries from this stanza for any missing volumes.
Figure 99. Copy Storage Pool Volumes Available Stanza
+--------------------------------------------------------------------------------+
|begin COPYSTGPOOL.VOLUMES.AVAILABLE macro |
| |
| /* Purpose: Mark copy storage pool volumes as available for use in recovery. */|
| /* Recovery Administrator: Remove any volumes that have not been obtained */|
| /* from the vault or are not available for any reason. */|
| /* Note: It is possible to use the mass update capability of the */|
| /* UPDATE command instead of issuing an update for each volume. However, */|
| /* the 'update by volume' technique used here allows you to select */|
| /* a subset of volumes to be processed. */|
| |
| upd vol TPBK05 acc=READW wherestg=CSTORAGEPF |
| upd vol TPBK07 acc=READW wherestg=CSTORAGEPF |
| |
|end COPYSTGPOOL.VOLUMES.AVAILABLE macro |
+--------------------------------------------------------------------------------+
COPYSTGPOOL.VOLUMES.DESTROYED
Contains a macro to mark copy storage pool volumes as unavailable if the volumes were onsite at the time of the disaster. This stanza does not include copy storage pool virtual volumes. These volumes are considered offsite and have not been destroyed in a disaster. You can use the information as a guide and issue the administrative commands from a command line, or you can copy it to a file, modify it, and run it. This macro is invoked by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.
After a disaster, compare the copy storage pool volumes listed in this stanza with the volumes that were left onsite. If you have any of the volumes and they are usable, you should remove their entries from this stanza.
Figure 100. Copy Storage Pool Volumes Destroyed Stanza
+--------------------------------------------------------------------------------+
|begin COPYSTGPOOL.VOLUMES.DESTROYED macro |
| |
| /* Purpose: Mark destroyed copy storage pool volumes as unavailable. */ |
| /* Volumes in this macro were not marked as 'offsite' at the time the */ |
| /* PREPARE ran. They were likely destroyed in the disaster. */ |
| /* Recovery Administrator: Remove any volumes that were not destroyed. */ |
| |
| |
|end COPYSTGPOOL.VOLUMES.DESTROYED macro |
+--------------------------------------------------------------------------------+
PRIMARY.VOLUMES.DESTROYED
Contains a macro to mark primary storage pool volumes as destroyed if the volumes were onsite at the time of disaster. You can use the information as a guide and run the administrative commands from a command line, or you can copy it to a file, modify it, and run it. This macro is invoked by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.
During recovery, compare the primary storage pool volumes listed in this stanza with the volumes that were onsite. If you have any of the volumes and they are usable, remove their entries from the stanza.
This stanza does not include primary storage pool virtual volumes. These volumes are considered offsite and have not been destroyed in a disaster.
Figure 101. Primary Storage Volumes Destroyed Stanza
+--------------------------------------------------------------------------------+
|begin PRIMARY.VOLUMES.DESTROYED macro |
| |
| /* Purpose: Mark primary storage pool volumes as ACCESS=DESTROYED. */ |
| /* Recovery administrator: Delete any volumes listed here */ |
| /* that you do not want to recover. */ |
| /* Note: It is possible to use the mass update capability of the */ |
| /* UPDATE command instead of issuing an update for each volume. However*/ |
| /* the 'update by volume' technique used here allows you to select */ |
| /* a subset of volumes to be marked as destroyed. */ |
| |
| upd vol /opt/tivoli/tsm/server/bin/>bk02 acc=DESTROYED wherestg=BACKUPPOOL |
| upd vol /opt/tivoli/tsm/server/bin/>bk01x acc=DESTROYED wherestg=BACKUPPOOL |
| upd vol /opt/tivoli/tsm/server/bin/>bk03 acc=DESTROYED wherestg= BACKUPPOOLF |
| upd vol BACK4X acc=DESTROYED wherestg=BACKUPPOOLT |
| |
|end PRIMARY.VOLUMES.DESTROYED macro |
+--------------------------------------------------------------------------------+
PRIMARY.VOLUMES.REPLACEMENT.CREATE
Contains a script with the commands needed to recreate the primary disk storage pool volumes. You can use the script as a guide and run the commands from a command line, or you can copy thew script to a file, modify it, and run it. This script is invoked by the RECOVERY.SCRIPT.NORMAL.MODE script.
The plan file assumes that the volume formatting program (DSMFMT) resides in the same directory as the server executable indicated in the stanza SERVER.REQUIREMENTS.
The SET DRMPLANVPOSTFIX command adds a character to the end of the names of the original volumes listed in this stanza. This character does the following:
Notes:
This stanza does not include primary storage pool virtual volumes, because these volumes are considered offsite and have not been destroyed in a disaster.
Figure 102. Primary Storage Volumes Replacement Stanza
+--------------------------------------------------------------------------------+
|begin PRIMARY.VOLUMES.REPLACEMENT.CREATE script |
| |
|#!/bin/ksh |
|set -x |
| |
| # Purpose: Create replacement volumes for primary storage pools that |
| # use device class DISK. |
| # Recovery administrator: Edit this section for your replacement |
| # volume names. New name must be unique, i.e. different from any |
| # original or other new name. |
| |
| print Replace /opt/tivoli/tsm/server/bin/>bk02 DISK 16M in BACKUPPOOL |
| /opt/tivoli/tsm/server/bin/>dsmfmt -m -data /opt/tivoli/tsm/server/bin/>bk02@ 1|
| |
| print Replace /opt/tivoli/tsm/server/bin/>bk01x DISK 5M in BACKUPPOOL |
| /opt/tivoli/tsm/server/bin/>dsmfmt -m -data /opt/tivoli/tsm/server/bin/>bk01x@ |
| |
|end PRIMARY.VOLUMES.REPLACEMENT.CREATE script |
+--------------------------------------------------------------------------------+
PRIMARY.VOLUMES.REPLACEMENT
Contains a macro to define primary storage pool volumes to the server. You can use the macro as a guide and run the administrative commands from a command line, or you can copy it to a file, modify it, and execute it. This macro is invoked by the RECOVERY.SCRIPT.NORMAL.MODE script.
Primary storage pool volumes with entries in this stanza have at least one of the following three characteristics:
The SET DRMPLANVPOSTFIX command adds a character to the end of the names of the original volumes listed in this stanza. This character does the following:
Notes:
This stanza does not include primary storage pool virtual volumes. These volumes are considered offsite and have not been destroyed in a disaster.
Figure 103. Primary Storage Volumes Replacement Stanza
+--------------------------------------------------------------------------------+
|begin PRIMARY.VOLUMES.REPLACEMENT macro |
| |
| /* Purpose: Define replacement primary storage pool volumes for either: */ |
| /* 1. Original volume in a storage pool whose device class was DISK. */ |
| /* 2. Original volume in a storage pool with MAXSCRATCH=0. */ |
| /* 3. Original volume in a storage pool and volume scratch=no. */ |
| /* Recovery administrator: Edit this section for your replacement */ |
| /* volume names. New name must be unique, i.e. different from any */ |
| /* original or other new name. */ |
| |
| /* Replace /opt/tivoli/tsm/server/bin/>bk02 DISK 16M in BACKUPPOOL */ |
| def vol BACKUPPOOL /opt/tivoli/tsm/server/bin/>bk02@ acc=READW |
| |
| /* Replace /opt/tivoli/tsm/server/bin/>bk01x DISK 5M in BACKUPPOOL */ |
| def vol BACKUPPOOL /opt/tivoli/tsm/server/bin/>bk01x@ acc=READW |
| |
| /* Replace /opt/tivoli/tsm/server/bin/>bk03 FILES 4M in BACKUPPOOLF */ |
| def vol BACKUPPOOLF /opt/tivoli/tsm/server/bin/>bk03@ acc=READW |
| |
| /* Replace BACK4X COOL8MM 0M in BACKUPPOOLT */ |
| def vol BACKUPPOOLT BACK4X@ acc=READW |
| |
|end PRIMARY.VOLUMES.REPLACEMENT macro |
+--------------------------------------------------------------------------------+
STGPOOLS.RESTORE
Contains a macro to restore the primary storage pools. You can use it as a guide and execute the administrative commands from a command line. You can also can copy it to a file, modify it, and execute it. This macro is invoked by the RECOVERY.SCRIPT.NORMAL.MODE script.
This stanza does not include primary storage pool virtual volumes. These volumes are considered offsite and have not been destroyed in a disaster.
Figure 104. Storage Pools Restore Stanza
+--------------------------------------------------------------------------------+
|begin STGPOOLS.RESTORE macro |
| |
|/* Purpose: Restore the primary storage pools from copy storage pool(s). */ |
|/* Recovery Administrator: Delete entries for any primary storage pools */ |
|/* that you do not want to restore. */ |
| |
| restore stgp ARCHIVEPOOL |
| restore stgp BACKUPPOOL |
| restore stgp BACKUPPOOLF |
| restore stgp BACKUPPOOLT |
| restore stgp SPACEMGPOOL |
| |
|end STGPOOLS.RESTORE macro |
+--------------------------------------------------------------------------------+
VOLUME.HISTORY.FILE
Contains a copy of the volume history information when the recovery plan was created. The DSMSERV RESTORE DB command uses the volume history file to determine what volumes are needed to restore the database. It is used by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.
The following rules determine where to place the volume history file at restore time:
Note: | The volhprefix is set based on the following:
|
If a fully qualified file name was not specified in the server options file for the VOLUMEHISTORY option, the server adds it to the DSMSERV.OPT.FILE stanza.
Figure 105. Volume History File Stanza
+--------------------------------------------------------------------------------+
| begin VOLUME.HISTORY.FILE |
| |
|************************************************************************* |
|* |
|* Tivoli Storage Manager Sequential Volume Usage History |
|* Updated 02/11/2000 10:20:34 |
|* |
|* Operation Volume Backup Backup Volume Device Volume |
|* Date/Time Type Series Oper. Seq Class Name Name |
|************************************************************************* |
| 2000/08/11 10:18:43 STGNEW 0 0 0 COOL8MM BACK4X |
| 2000/08/11 10:18:43 STGNEW 0 0 0 FILES BK03 |
| 2000/08/11 10:18:46 STGNEW 0 0 0 LIB8MM TPBK05 |
|* Location for volume TPBK06 is: 'Ironvault Inc.' |
| 2000/08/11 10:19:23 BACKUPFULL 1 0 1 LIB8MM TPBK06 |
| 2000/08/11 10:20:03 STGNEW 0 0 0 LIB8MM TPBK07 |
| 2000/08/11 10:20:22 BACKUPINCR 1 1 1 LIB8MM TPBK08 |
| |
|end VOLUME.HISTORY.FILE |
+--------------------------------------------------------------------------------+
DEVICE.CONFIGURATION.FILE
Contains a copy of the server device configuration information when the recovery plan was created. The DSMSERV RESTORE DB command uses the device configuration file to read the database backup volumes. It is used by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.
At recovery time, you may need to modify this stanza. You must update the device configuration information if the hardware configuration at the recovery site has changed. Examples of changes requiring updates to the configuration information are:
For details, see Updating the Device Configuration File.
The following rules determine where the device configuration file is placed at restore time:
Note: | The devcprefix is set based on the following:
|
If a fully qualified file name was not specified for the DEVCONFIG option in the server options file, the server adds it to the stanza DSMSERV.OPT.FILE.
Figure 106. Device Configuration File Stanza
+--------------------------------------------------------------------------------+
|begin DEVICE.CONFIGURATION.FILE |
| |
|/* Tivoli Storage Manager Device Configuration */ |
|DEFINE DEVCLASS COOL8MM DEVTYPE=GENERICTAPE FORMAT=DRIVE MOUNTLIMIT=1 MOUNTWAIT=|
|MOUNTRETENTION=60 PREFIX=TIVSM LIBRARY=ITSML |
|DEFINE DEVCLASS FILES DEVTYPE=FILE MAXCAPACITY=4096K MOUNTLIMIT=2 + |
|DIRECTORY=/opt/tivoli/tsm/server/bin/> |
|DEFINE DEVCLASS FILESSM DEVTYPE=FILE MAXCAPACITY=100K MOUNTLIMIT=2 + |
|DIRECTORY=/opt/tivoli/tsm/server/bin/> |
|DEFINE DEVCLASS LIB8MM DEVTYPE=8MM FORMAT=DRIVE MOUNTLIMIT=1 MOUNTWAIT=60+ |
|MOUNTRETENTION=60 PREFIX=TIVSM LIBRARY=RLLIB |
|end DEVICE.CONFIGURATION.FILE |
+--------------------------------------------------------------------------------+
DSMSERV.OPT.FILE
Contains a copy of the server options file. This stanza is used by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.
Note: | The following figure contains text strings that are too long to display in hardcopy or softcopy publications. The long text strings have a plus symbol (+) at the end of the string to indicate that they continue on the next line. |
The disaster recovery plan file adds the DISABLESCHEDS option to the server options file and sets it to YES. This option disables administrative and client schedules while the server is being recovered. After the server is recovered, you can enable scheduling by deleting the option or setting it to NO and then restarting the server.
Figure 107. Server Options File Stanza
+--------------------------------------------------------------------------------+
|begin DSMSERV.OPT.FILE |
| |
|* Server options file located in /opt/tivoli/tsm/server/bin/>dsmserv.optx |
|TCPPort 1509 |
|VOLUMEHISTORY /opt/tivoli/tsm/server/bin/>volhistory.txtx |
|DEVCONFIG /opt/tivoli/tsm/server/bin/>devconfig.txtx |
|* The following option was added by PREPARE. |
|DISABLESCHEDS YES |
| |
|end DSMSERV.OPT.FILE |
+--------------------------------------------------------------------------------+
Figure 108. License Information Stanza
+--------------------------------------------------------------------------------+
|begin LICENSE.INFORMATION |
| Last License Audit: 12/30/2000 10:25:34 |
| Registered Client Nodes: 1 |
| Licensed Client Nodes: 51 |
| Are network connections in use ?: Yes |
| Are network connections licensed ?: Yes |
|Are Open Systems Environment clients registered ?: No |
| Are Open Systems Environment clients licensed ?: No |
| Is space management in use ?: No |
| Is space management licensed ?: No |
| Is disaster recovery manager in use ?: Yes |
| Is disaster recovery manager licensed ?: Yes |
| Are Server-to-Server Virtual Volumes in use ?: No |
| Are Server-to-Server Virtual Volumes licensed ?: Yes |
| Is Advanced Device Support required ?: No |
| Is Advanced Device Support licensed ?: No |
| Server License Compliance: Valid |
| |
|end LICENSE.INFORMATION |
+--------------------------------------------------------------------------------+
MACHINE.GENERAL.INFORMATION
Provides information for the server machine (for example, machine location). This stanza is included in the plan file if the machine information is saved in the database using the DEFINE MACHINE with ADSMSERVER=YES.
Figure 109. Machine General Information Stanza
+--------------------------------------------------------------------------------+
|begin MACHINE.GENERAL.INFORMATION |
|Purpose: General information for machine DSMSRV1. |
| This is the machine that contains DSM server DSM. |
| Machine Name: DSMSRV1 |
| Machine Priority: 1 |
| Building: 21 |
| Floor: 2 |
| Room: 2749 |
| Description: DSM Server for Branch 51 |
| Recovery Media Name: DSMSRVIMAGE |
| |
|end MACHINE.GENERAL.INFORMATION |
| |
+--------------------------------------------------------------------------------+
MACHINE.RECOVERY.INSTRUCTIONS
Provides the recovery instructions for the server machine. This stanza is included in the plan file if the machine recovery instructions are saved in the database.
Figure 110. Machine Recovery Instructions Stanza
+--------------------------------------------------------------------------------+
|begin MACHINE.RECOVERY.INSTRUCTIONS |
| Purpose: Recovery instructions for machine DSMSRV1. |
| |
|Primary Contact: |
| Jane Smith (wk 520-000-0000 hm 520-001-0001) |
|Secondary Contact: |
| John Adams (wk 520-000-0001 hm 520-002-0002) |
| |
|end MACHINE.RECOVERY.INSTRUCTIONS |
+--------------------------------------------------------------------------------+
MACHINE.RECOVERY.CHARACTERISTICS
Provides the hardware and software characteristics for the server machine.This stanza is included in the plan file if the machine characteristics are saved in the database.
Figure 111. Machine Recovery Characteristics Stanza
+--------------------------------------------------------------------------------+
|begin MACHINE.CHARACTERISTICS |
|Purpose: Hardware and software characteristics of machine TSMSRV1. |
| /tsm (/dev/vg00/lvol9 ): 804700 blocks 79851 i-nodes|
| /cdrom (/dev/dsk/c1t6d0 ): 0 blocks 0 i-nodes|
| /home (/dev/vg00/lvol4 ): 35694 blocks 3434 i-nodes|
| /opt (/dev/vg00/lvol5 ): 184268 blocks 30670 i-nodes|
| /tmp (/dev/vg00/lvol6 ): 55042 blocks 15220 i-nodes|
| /usr (/dev/vg00/lvol7 ): 78476 blocks 39644 i-nodes|
| |
|end MACHINE.CHARACTERISTICS |
+--------------------------------------------------------------------------------+
MACHINE.RECOVERY.MEDIA
Provides information about the media (for example, boot media) needed for rebuilding the machine that contains the server.This stanza is included in the plan file if recovery media information is saved in the database and it has been associated with the machine that contains the server.
Figure 112. Machine Recovery Media Stanza
+--------------------------------------------------------------------------------+
|begin MACHINE.RECOVERY.MEDIA.REQUIRED |
| Purpose: Recovery media for machine DSMSRV1. |
| Recovery Media Name: DSMSRV |
| Type: Other |
| Volume Names: |
| Location: IRONMNT |
| Description: Server Installation CD |
| Product: |
| Product Information: |
| |
| Recovery Media Name: HPOPSYS |
| Type: Other |
| Volume Names: |
| Location: IRONMNT |
| Description: HP-UX 11.00 Installation CD |
| Product: |
| Product Information: |
|end MACHINE.RECOVERY.MEDIA.REQUIRED |
+--------------------------------------------------------------------------------+