Administrator's Guide


The Disaster Recovery Plan

The disaster recovery plan file contains the information required for recovery of a TSM server to the point in time represented by the last database backup operation that is completed before the PREPARE command is issued.

The disaster recovery plan is organized into stanzas. You can break out these stanzas into multiple files.

Breaking Out a Disaster Recovery Plan File

You can use an awk script or an editor to break out the stanzas in the disaster recovery plan file into individual files. An example 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.

Structure of the Disaster Recovery Plan File

The disaster recovery plan is divided into stanzas, which can be categorized as follows:

Command stanzas
Consist of scripts (for example, batch programs or batch files) and TSM macros. These stanzas can be viewed, printed, updated, or run as part of the disaster recovery process.
Note:The RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE and RECOVERY.SCRIPT.NORMAL.MODE stanzas contain the commands that invoke the scripts and macros contained in the other stanzas.

Instruction stanzas
Consist of recovery instructions specific to your site. They can be printed, updated, and used during server recovery.

Server requirements stanzas
Include the database and recovery log requirements, device and volume requirements, and license information. You can view or print these stanzas.

Configuration file stanzas
Consist of the volume history, device configuration, and server options files.

Machine and recovery media stanzas
Consist of machine general information, machine hardware and software characteristics, recovery media information, and machine recovery instructions. They can be printed, updated, and used during server recovery. You determine the information to rebuild the machine where the TSM server is running. The PREPARE command retrieves the information for the machine from the TSM database.

Table 31 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:In the column "Action During Setup or Periodic Updates," the "--" means that DRM automatically collects this information for the file.

Table 31. Administrative Tasks Associated with the Disaster Recovery Plan File

Stanza Name During Setup or Periodic Updates During Routine Processing During Disaster Recovery
PLANFILE.DESCRIPTION -- -- --
PLANFILE.TABLE.OF.CONTENTS -- -- --
SERVER.REQUIREMENTS -- -- --
RECOVERY.INSTRUCTIONS.GENERAL Optionally edit source file associated with stanza -- --
RECOVERY.INSTRUCTIONS.OFFSITE Optionally edit source file associated with stanza -- --
RECOVERY.INSTRUCTIONS.INSTALL Optionally edit source file associated with stanza -- --
RECOVERY.INSTRUCTIONS.DATABASE Optionally edit source file associated with stanza -- --
RECOVERY.INSTRUCTIONS.STGPOOL Optionally edit source file associated with stanza -- --
RECOVERY.VOLUMES.REQUIRED -- MOVE DRMEDIA --
RECOVERY.DEVICES.REQUIRED -- -- --
RECOVERY.SCRIPT.DISASTER. RECOVERY.MODE script -- -- Optionally edit/run
RECOVERY.SCRIPT.NORMAL.MODE script -- -- Optionally edit/run
LOGANDDB.VOLUMES.CREATE script -- -- Optionally edit/run
LOG.VOLUMES -- -- Optionally edit/copy
DB.VOLUMES -- -- Optionally edit/copy
LOGANDDB.VOLUMES.INSTALL script -- -- Optionally edit/run
LICENSE.REGISTRATION macro -- -- Optionally edit/run
COPYSTGPOOL.VOLUMES.AVAILABLE macro -- MOVE DRMEDIA Optionally edit/run
COPYSTGPOOL.VOLUMES.DESTROYED macro -- MOVE DRMEDIA Optionally edit/run
PRIMARY.VOLUMES.DESTROYED macro -- -- Optionally edit/run
PRIMARY.VOLUMES.REPLACEMENT.CREATE script -- -- Optionally edit/run
PRIMARY.VOLUMES.REPLACEMENT macro -- -- Optionally edit/run
STGPOOLS.RESTORE macro -- -- Optionally edit/run
VOLUME.HISTORY.FILE configuration file -- -- Optionally copy
DEVICE.CONFIGURATION.FILE configuration file -- -- Optionally edit/copy
DSMSERV.OPT.FILE configuration file -- -- Optionally edit/copy
LICENSE.INFORMATION -- -- --
MACHINE.GENERAL.INFORMATION Optionally issue DEFINE MACHINE ADSMSERVER=YES -- --
MACHINE.RECOVERY.INSTRUCTIONS Optionally issue INSERT MACHINE RECOVERYINSTRUCTIONS -- --
MACHINE.RECOVERY.CHARACTERISTICS Optionally issue INSERT MACHINE CHARACTERISTICS -- --
MACHINE.RECOVERY.MEDIA Optionally issue DEFINE RECOVERYMEDIA and DEFINE RECMEDMACHASSOCIATION -- --

Example Disaster Recovery Plan File

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.

Description and Table of Contents Stanzas

PLANFILE.DESCRIPTION
Identifies the server for this recovery plan, and the date and time the plan is created.

PLANFILE.TABLE.OF.CONTENTS
Lists the stanzas documented in this plan.

Figure 81. Description and Table of Contents Stanzas


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
begin PLANFILE.DESCRIPTION
 
Recovery Plan for Server DESIGN_DEPARTMENT
Created by DRM PREPARE on 02/11/1999 10:20:34
DRM PLANPREFIX /prepare/
Server for Sun Solaris - Version 3, Release 7, Level x.x/x.x
 
end PLANFILE.DESCRIPTION
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 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
  LICENSE.INFORMATION
 
Machine Description Stanzas:
  MACHINE.GENERAL.INFORMATION
  MACHINE.RECOVERY.INSTRUCTIONS
  MACHINE.CHARACTERISTICS
  MACHINE.RECOVERY.MEDIA.REQUIRED
 
end PLANFILE.TABLE.OF.CONTENTS
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

Server Requirements Stanza

SERVER.REQUIREMENTS
Identifies the database and recovery log storage requirements for this server. The replacement server machine 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 machine, you must edit the plan file to account for this change.
Note: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:
  • RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE
  • LOGANDDB.VOLUMES.CREATE
  • LOGANDDB.VOLUMES.INSTALL
  • PRIMARY.VOLUMES.REPLACEMENT.CREATE

Figure 82. 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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

Recovery Instructions Stanza

The administrator enters recovery instructions into source files that the PREPARE command includes in the plan files. For more information on editing the source file, see Customizing the Site-Specific Recovery Instructions.

Note:In the following stanza descriptions, instructionsprefix represents the prefix portion of the file name. See Prefix for Recovery Instructions for details.

RECOVERY.INSTRUCTIONS.GENERAL
Identifies site specific instructions the administrator has entered in the source file identified by instructionsprefix 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.

RECOVERY.INSTRUCTIONS.OFFSITE
Contains instructions the server administrator has manually edited to the source text file identified by instructionsprefix 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).

RECOVERY.INSTRUCTIONS.INSTALL
Contains instructions the server administrator has manually edited to the source text file identified by instructionsprefix RECOVERY.INSTRUCTIONS.INSTALL. The instructions should include how to rebuild the base server machine and the location of the system image backup copies.

RECOVERY.INSTRUCTIONS.DATABASE
Contains instructions the server administrator has manually edited to the source text file identified by instructionsprefix RECOVERY.INSTRUCTIONS.DATABASE. The instructions should include how to prepare for the TSM database recovery. For example, you may want to provide instructions on how to initialize or load the backup volumes for an automated library. Please note, the following example does not contain a sample of this stanza.

RECOVERY.INSTRUCTIONS.STGPOOL
Contains instructions the server administrator has manually edited to the source text file identified by instructionsprefix 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. Please note, the following example does not contain a sample of this stanza.

Figure 83. Recovery Instructions Stanzas


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
begin RECOVERY.INSTRUCTIONS.INSTALL
 
 The base  server system is SunOS 5.5.1 running on an
 Ultra-Enterprise 4000.  The SunOS 5.5.1 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 SunOS 5.5.1 and installation
 is Fred Myers.
 
end RECOVERY.INSTRUCTIONS.INSTALL
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* 

Volume and Device Requirements Stanzas

RECOVERY.VOLUMES.REQUIRED
Provides a list of the database backup and copy storage pool volumes required to recover the TSM 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. The location and device class names for the volumes are displayed.

If you are using a nonvirtual volume environment and issuing the MOVE DRMEDIA command for offsite recovery media management, a blank location field means that the volumes are onsite and available to the TSM server. This volume list can be used as the basis of periodic audits for the inventory of volumes at the courier and offsite 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.

RECOVERY.DEVICES.REQUIRED
Provides details about the devices needed to read the backup volumes.

Figure 84. Volume and Device Requirements Stanzas


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 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
 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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: 8MM
                        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/1997 10:18:34
 
end RECOVERY.DEVICES.REQUIRED
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* 

Disaster Recovery Mode Stanza

RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE
Contains a script with the commands needed to restore the database and restart the server. Use it as a guide and run the commands as needed from a command line, or copy it to a file, modify it and the files it refers to, and run the script. At the completion of these steps, client requests for file restores are satisfied directly from copy storage pool volumes.

The RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script often requires modification at the recovery site because of differences between the original and the replacement systems. This script provides the following:

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.DISASTER.RECOVERY.MODE don mox prodtsm

For additional information on planprefix, see Prefix for the Recovery Plan File.

Figure 85. 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/bindsmserv.optx
cp /prepare/VOLUME.HISTORY.FILE \
    /opt/tivoli/tsm/server/binvolhistory.txtx
cp /prepare/DEVICE.CONFIGURATION.FILE \
    /opt/tivoli/tsm/server/bindevconfig.txtx
 
export DSMSERV_CONFIG=/opt/tivoli/tsm/server/bindsmserv.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/bindsmserv restore db todate=08/11/1996 totime=10:20:22
 
 # Start the server.
nohup /opt/tivoli/tsm/server/bindsmserv &
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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* 

Normal Mode Stanza

RECOVERY.SCRIPT.NORMAL.MODE
Contains a script with the commands required to restore the server primary storage pools. Use it as a guide and issue the commands as needed from a command line, or you can copy it to a file, modify it and the files it references, and run it.

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 will often need modification at the recovery site because of differences between the original and the replacement systems.

This script invokes the script contained in the following stanza:

PRIMARY.VOLUMES.REPLACEMENT.CREATE

This script also invokes the TSM macros contained in stanzas:

PRIMARY.VOLUMES.REPLACEMENT
STGPOOLS.RESTORE

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 additional information on planprefix, see Prefix for the Recovery Plan File.

Figure 86. 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
 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

Create and Install Database and Recovery Log Volumes Stanzas

LOGANDDB.VOLUMES.CREATE
Contains a script with the command required to recreate the TSM database and log volumes that existed before the disaster. You can use it 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.

If you used raw partitions for log or database volumes, you must create these volumes before running the LOGANDDB.VOLUMES.INSTALL script. If you want to use regular files instead of raw partitions, you will have to modify this script to include the appropriate DSMFMT commands.

The PREPARE command assumes that the volume formatting program (DSMFMT) resides in the same directory as the server executable indicated in the stanza SERVER.REQUIREMENTS.

This script is invoked by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE 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 which will be used by the LOGANDDB.VOLUMES.INSTALL script.

DB.VOLUMES
Contains the names of the database volumes to be initialized.

The contents of this stanza must be placed into a separate file which will be used by the LOGANDDB.VOLUMES.INSTALL script.

LOGANDDB.VOLUMES.INSTALL
Contains a script with the commands required to initialize the TSM database and log volumes that existed before the disaster.

This script is invoked by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.

Figure 87. Create and Install Database and Recovery Log Volumes Scripts


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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/bindb01x.
 rm -f /opt/tivoli/tsm/server/bindb01x
 
  print Create  database volume /opt/tivoli/tsm/server/bindb01x 12M
 /opt/tivoli/tsm/server/bindsmfmt -m -db /opt/tivoli/tsm/server/bindb01x 12M
 
  print Remove database volume /opt/tivoli/tsm/server/bindb02x.
 rm -f /opt/tivoli/tsm/server/bindb02x
 
  print Create  database volume /opt/tivoli/tsm/server/bindb02x 8M
 /opt/tivoli/tsm/server/bindsmfmt -m -db /opt/tivoli/tsm/server/bindb02x 8
 
  print Remove log volume /opt/tivoli/tsm/server/binlg01x.
 rm -f /opt/tivoli/tsm/server/binlg01x
 
  print Create  log volume /opt/tivoli/tsm/server/binlg01x 12M
 /opt/tivoli/tsm/server/bindsmfmt -m -log /opt/tivoli/tsm/server/binlg01x 12M
 
  print Remove log volume /opt/tivoli/tsm/server/binlg02x.
 rm -f /opt/tivoli/tsm/server/binlg02x
 
  print Create  log volume /opt/tivoli/tsm/server/binlg02x 8M
 /opt/tivoli/tsm/server/bindsmfmt -m -log /opt/tivoli/tsm/server/binlg02x 8
 
end LOGANDDB.VOLUMES.CREATE script
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* 
begin LOG.VOLUMES
/opt/tivoli/tsm/server/binlg01x
/opt/tivoli/tsm/server/binlg02x
 
end LOG.VOLUMES
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
begin DB.VOLUMES
 
/opt/tivoli/tsm/server/bindb01x
/opt/tivoli/tsm/server/bindb02x
 
end DB.VOLUMES
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 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/bindsmserv install \
   2 FILE:/prepare/LOG.VOLUMES \
   2 FILE:/prepare/DB.VOLUMES
 
end LOGANDDB.VOLUMES.INSTALL script
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

License Registration Stanza

LICENSE.REGISTRATION
Contains a TSM macro to register your TSM server licenses.

This macro is invoked by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.

Figure 88. License Registration Macro


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* 

Copy Storage Pool Volumes Stanzas

COPYSTGPOOL.VOLUMES.AVAILABLE
Contains a TSM 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 TSM administrative commands as needed 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 moved back onsite. You should remove entries from this stanza for any missing volumes.

COPYSTGPOOL.VOLUMES.DESTROYED
Contains a TSM macro to mark copy storage pool volumes as unavailable, if the volumes were onsite at the time of the disaster. You can use the information as a guide and issue the TSM administrative commands as needed 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.

This stanza does not include copy storage pool virtual volumes. These volumes are considered offsite and have not been destroyed in a disaster.

Figure 89. Copy Storage Pool Volumes Macros


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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 Storage Volumes Stanzas

PRIMARY.VOLUMES.DESTROYED
Contains a TSM macro to mark primary storage pool volumes as destroyed when the volumes were onsite at the time of disaster. You can use the information as a guide and execute the TSM administrative commands as needed 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.DISASTER.RECOVERY.MODE script.

In the event of a disaster, 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, you should remove their entries from here.

This stanza does not include primary storage pool virtual volumes. These volumes are considered offsite and have not been destroyed in a disaster.

PRIMARY.VOLUMES.REPLACEMENT.CREATE
Contains a script with the commands required to recreate the primary disk storage pool volumes. You can use it as a guide and execute the commands as needed from a command line, or you can copy it to a file, modify it, and execute it.

If you used raw partitions for the primary storage pool volumes, you must create these replacement volumes by running the PRIMARY.VOLUMES.REPLACEMENT macro. If you want to use regular files instead of raw partitions, modify this script to include the appropriate DSMFMT commands.

The PREPARE command assumes that the volume formatting program (DSMFMT) resides in the same directory as the server executable indicated in the stanza SERVER.REQUIREMENTS.

This script is invoked by the RECOVERY.SCRIPT.NORMAL.MODE script.

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:

This stanza does not include primary storage pool virtual volumes, because these volumes are considered offsite and have not been destroyed in a disaster.

PRIMARY.VOLUMES.REPLACEMENT
Contains a TSM macro to define primary storage pool volumes to the TSM server. You can use it as a guide and execute the TSM administrative commands as needed 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 that have entries in this stanza possess at least one of the following three characteristics:

  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 attribute=no.

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:

This stanza does not include primary storage pool virtual volumes. These volumes are considered offsite and have not been destroyed in a disaster.

Figure 90. Primary Storage Volumes Macro and Script


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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/binbk02 acc=DESTROYED wherestg=BACKUPPOOL
 upd vol /opt/tivoli/tsm/server/binbk01x acc=DESTROYED wherestg=BACKUPPOOL
 upd vol /opt/tivoli/tsm/server/binbk03 acc=DESTROYED wherestg= BACKUPPOOLF
 upd vol BACK4X acc=DESTROYED wherestg=BACKUPPOOLT
 
end PRIMARY.VOLUMES.DESTROYED macro
 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* 
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/binbk02 DISK 16M in BACKUPPOOL
 /opt/tivoli/tsm/server/bindsmfmt -m -data /opt/tivoli/tsm/server/binbk02@ 16
 
   print Replace /opt/tivoli/tsm/server/binbk01x DISK 5M in BACKUPPOOL
 /opt/tivoli/tsm/server/bindsmfmt -m -data /opt/tivoli/tsm/server/binbk01x@ 5
 
end PRIMARY.VOLUMES.REPLACEMENT.CREATE script
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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/binbk02 DISK 16M in BACKUPPOOL */
 def vol BACKUPPOOL /opt/tivoli/tsm/server/binbk02@ acc=READW
 
   /* Replace /opt/tivoli/tsm/server/binbk01x DISK 5M in BACKUPPOOL */
 def vol BACKUPPOOL /opt/tivoli/tsm/server/binbk01x@ acc=READW
 
   /* Replace /opt/tivoli/tsm/server/binbk03 FILES 4M in BACKUPPOOLF */
 def vol BACKUPPOOLF /opt/tivoli/tsm/server/binbk03@ acc=READW
 
   /* Replace BACK4X COOL8MM 0M in BACKUPPOOLT */
 def vol BACKUPPOOLT BACK4X@ acc=READW
 
end PRIMARY.VOLUMES.REPLACEMENT macro 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* 

Storage Pools Restore Stanza

STGPOOLS.RESTORE
Contains a TSM macro to restore the primary storage pools. You can use it as a guide and execute the TSM administrative commands as needed from a command line, or optionally 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 91. Storage Pools Restore Macro


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

Configuration Stanzas

VOLUME.HISTORY.FILE
Contains a copy of the server volume history information reflecting current history at the time of disaster recovery plan creation. The DSMSERV RESTORE DB command uses the volume history file to determine what volumes are required to restore the database. It is referenced by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.

The following rules are used to determine where the volume history file is placed at restore time:

Note:The volhprefix is set based on the following:

  • If the environmental variable DSMSERV_DIR has been defined, it is used as the volhprefix.

  • If the environmental variable DSMSERV_DIR has not been defined, the directory where the TSM server is started from is used as the volhprefix.

If a fully qualified file name was not specified in the server options file for the VOLUMEHISTORY option, the PREPARE command adds it to the DSMSERV.OPT.FILE stanza.

DEVICE.CONFIGURATION.FILE
Contains a copy of the server device configuration information reflecting current history at the time of disaster recovery plan creation. The DSMSERV RESTORE DB command uses the device configuration file to read the database backup volumes. It is referenced by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.

At recovery time, the contents of this stanza may need to be modified. 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 information about updating the device configuration file, see Updating the Device Configuration File.

The following rules are used to determine where the device configuration file is placed at restore time:

Note on the devcprefix:The devcprefix is set based on the following:

  • If the environmental variable DSMSERV_DIR has been defined, it is used as the devcprefix.

  • If the environmental variable DSMSERV_DIR has not been defined, the directory where the TSM server is started from is used as the devcprefix.

If a fully qualified file name was not specified for the DEVCONFIG option in the server options file, PREPARE adds it to the stanza DSMSERV.OPT.FILE.

DSMSERV.OPT.FILE
Contains a copy of the server options file.

This stanza is referenced 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.

Figure 92. Configuration Files


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 begin VOLUME.HISTORY.FILE
 
*************************************************************************
*
*               Tivoli Storage Manager Sequential Volume Usage History
*                                     Updated 02/11/1999 10:20:34
*
*     Operation         Volume   Backup Backup Volume Device      Volume
*     Date/Time          Type    Series Oper.   Seq   Class Name  Name
*************************************************************************
 1997/08/11 10:18:43  STGNEW          0      0      0 COOL8MM     BACK4X
 1997/08/11 10:18:43  STGNEW          0      0      0 FILES       BK03
 1997/08/11 10:18:46  STGNEW          0      0      0 LIB8MM      TPBK05
* Location for volume TPBK06 is: 'Ironvault Inc.'
 1997/08/11 10:19:23  BACKUPFULL      1      0      1 LIB8MM      TPBK06
 1997/08/11 10:20:03  STGNEW          0      0      0 LIB8MM      TPBK07
 1997/08/11 10:20:22  BACKUPINCR      1      1      1 LIB8MM      TPBK08
 
end VOLUME.HISTORY.FILE
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
begin DEVICE.CONFIGURATION.FILE
 
/* Tivoli Storage Manager Device Configuration */
DEFINE DEVCLASS COOL8MM DEVTYPE=8MM FORMAT=DRIVE MOUNTLIMIT=1 MOUNTWAIT=60
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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
begin DSMSERV.OPT.FILE
 
* Server options file located in /opt/tivoli/tsm/server/bindsmserv.optx
TCPPort 1509
VOLUMEHISTORY /opt/tivoli/tsm/server/binvolhistory.txtx
DEVCONFIG     /opt/tivoli/tsm/server/bindevconfig.txtx
* The following option was added by PREPARE.
DISABLESCHEDS YES
 
end DSMSERV.OPT.FILE
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* 

License Information Stanza

LICENSE.INFORMATION
Contains a copy of the latest license audit results and the server license terms.

Figure 93. License Information


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
begin LICENSE.INFORMATION
                               Last License Audit: 12/30/1999 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 Files Stanza

MACHINE.GENERAL.INFORMATION
Provides information for the machine that contains the TSM server (for example, machine location).

This stanza is included in the plan file if the machine information are saved in the TSM database using the DEFINE MACHINE with the ADSMSERVER parameter set to YES.

MACHINE.RECOVERY.INSTRUCTIONS
Provides the recovery instructions for the machine that contains the TSM server.

This stanza is included in the plan file if the machine recovery instructions are saved in the TSM database.

MACHINE.RECOVERY.CHARACTERISTICS
Provides the hardware and software characteristics for the machine that contains the TSM server.

This stanza is included in the plan file if the machine characteristics are saved in the TSM database.

MACHINE.RECOVERY.MEDIA
Provides information about the media (for example, boot media) needed for rebuilding the machine that contains the TSM server.

This stanza is included in the plan file if recovery media information is saved in the TSM database and it has been associated with the machine that contains the TSM server.

Figure 94. Machine Stanzas


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
 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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
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 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
begin MACHINE.CHARACTERISTICS
Purpose: Hardware and software characteristics of machine DSMSRV1.
  Filesystem            kbytes    used   avail capacity  Mounted on
  /dev/dsk/c0t3d0s0      69191   33036   29245    53%    /
  /dev/dsk/c0t3d0s6     214143  162727   30006    84%    /usr
  /proc                      0       0       0     0%    /proc
  fd                         0       0       0     0%    /dev/fd
  swap                  225520      32  225488     0%    /tmp
  /dev/dsk/c0t3d0s7     288391  237438   22123    91%    /opt
 
end MACHINE.CHARACTERISTICS
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
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: SUNOPSYS
                 Type: Other
         Volume Names:
             Location: IRONMNT
          Description: SunOS 5.5.1 Installation CD
              Product:
  Product Information:
end MACHINE.RECOVERY.MEDIA.REQUIRED
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-

 


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