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.
You can use a Microsoft VBScript command procedure or an editor to break out the stanzas in the disaster recovery plan file into individual files. An example procedure, planexpl.vbs, is shipped with DRM. This is an example procedure that you can modify for your local installation. Keep a copy of the procedure offsite so it will be available at the recovery site.
Figure 89. Example of a VBScript command Procedure to Break Out the Disaster Recovery Plan File
'**************************************************************************** ' Tivoli Disaster Recovery Manager for Windows NT/2000 Sample Script ' ' Explode a recovery plan file into separate files (batch programs, ' TSM macros, TSM server options file etc.) ' ' Invoke with: ' cscript planexpl.vbs recoveryplanfilename [outputprefixname] ' where: ' recoveryplanfilename is the name of the recovery plan file created ' by the TSM PREPARE command ' outputprefixname (optional) fully qualified prefix for the files ' that will be created. If you specify this, then ' you will probably have to change the file names ' in the stanzas within the plan file since they ' contain the default. The default is the same ' prefix used to generate the plan file. Any ' directories within the prefix must already ' exist. ' ' Example usage: ' cscript planexpl.vbs c:\adsmsrv\recplans\19951115.051421 '***************************************************************************** Dim args Dim PLANFILE, OUTDIR, OUTFILE Dim STANZAS Dim VOLNAMES(100),NbrV,LOGDBVOLS Dim fso, fi, fo Dim WORDS Dim CRLF Dim RESULTS, RESULTS2 CRLF = Chr(13) & Chr(10) LOGDBVOLS = False : NbrV = 0 OUTDIR = "" : OUTFILE = "" RESULTS = "" : RESULTS2 = "" '***************************************************************************** '* Get input arguments: PLANFILE=recoveryplanfilename '* OUTDIR =outputprefixname '***************************************************************************** set args = Wscript.Arguments If args.Count < 1 Then Wscript.Echo _ "usage: cscript planexpl.vbs recoveryplanfilename [outputprefixname]" & CRLF & _ "example: cscript planexpl.vbs c:\adsmsrv\recplans\19951115.051421" Wscript.Quit(1) Else PLANFILE = args.Item(0) If args.Count > 1 Then OUTDIR = args.Item(1) End IfRESULTS = RESULTS & "Planfile: " & PLANFILE & " Outputprefix: " & OUTDIR & CRLF '**************************************************************************** ' For each recovery plan file stanza name determine the extension (if any) ' to be added to the file name created by using the stanza name and extension '**************************************************************************** Set STANZAS = CreateObject("Scripting.Dictionary") STANZAS.Add "RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE", ".CMD" STANZAS.Add "RECOVERY.SCRIPT.NORMAL.MODE", ".CMD" STANZAS.Add "RECOVERY.VOLUMES.REQUIRED" , "none" STANZAS.Add "RECOVERY.DEVICES.REQUIRED" , "none" STANZAS.Add "SERVER.REQUIREMENTS" , "none" STANZAS.Add "LOG.VOLUMES" , "none" STANZAS.Add "DB.VOLUMES" , "none" STANZAS.Add "LOGANDDB.VOLUMES.INSTALL", ".CMD" STANZAS.Add "LICENSE.REGISTRATION" , ".MAC" STANZAS.Add "COPYSTGPOOL.VOLUMES.AVAILABLE", ".MAC" STANZAS.Add "COPYSTGPOOL.VOLUMES.DESTROYED", ".MAC" STANZAS.Add "PRIMARY.VOLUMES.DESTROYED" , ".MAC" STANZAS.Add "PRIMARY.VOLUMES.REPLACEMENT.CREATE" , ".CMD" STANZAS.Add "PRIMARY.VOLUMES.REPLACEMENT" , ".MAC" STANZAS.Add "STGPOOLS.RESTORE", ".MAC" STANZAS.Add "RECOVERY.INSTRUCTIONS.GENERAL" , "none" STANZAS.Add "RECOVERY.INSTRUCTIONS.OFFSITE" , "none" STANZAS.Add "RECOVERY.INSTRUCTIONS.INSTALL" , "none" STANZAS.Add "RECOVERY.INSTRUCTIONS.DATABASE" , "none" STANZAS.Add "RECOVERY.INSTRUCTIONS.STGPOOL" , "none" STANZAS.Add "MACHINE.GENERAL.INFORMATION" , "none" STANZAS.Add "MACHINE.RECOVERY.INSTRUCTIONS" , "none" STANZAS.Add "MACHINE.CHARACTERISTICS", "none" STANZAS.Add "MACHINE.RECOVERY.MEDIA.REQUIRED", "none" STANZAS.Add "VOLUME.HISTORY.FILE" , "none" STANZAS.Add "DEVICE.CONFIGURATION.FILE" , "none" STANZAS.Add "DSMSERV.OPT.FILE" , "none" STANZAS.Add "LICENSE.INFORMATION" , "none" Set fso = CreateObject("Scripting.FileSystemObject") Set fi = fso.OpenTextFile(PLANFILE, 1, False) Do While fi.AtEndOfStream <> True '**************************************************************************** ' Read a line from the input recovery plan file '**************************************************************************** ALINE = fi.ReadLine '**************************************************************************** ' Get the first 2 words. We're looking for 'begin'/'end' and a stanza name '**************************************************************************** WORD1 = "" : WORD2 = "" : THEREST = "" If Not ALINE = "" then WORDS = Split(ALINE, " ", -1, 1) WORD1 = WORDS(0) If Ubound(WORDS) > 0 Then WORD2 = WORDS(1) if Ubound(WORDS) > 1 Then THEREST = WORDS(2) End If '**************************************************************************** ' If the first word is 'begin' and this is a stanza that we'll create a file ' for then build the output file name using the output directory. Add an ' extension if needed. Erase the previous version of the file and then ' indicate that the new file is being created. If the stanza contains the ' names of database volumes or the names of log volumes then indicate that ' these volume names need to be remembered so later checking can be done to ' determine if volumes by these names currently exist (since the volumes ' will be erased). '**************************************************************************** If WORD1 = "begin" And STANZAS.Exists(WORD2) Then OUTFILE = OUTDIR & WORD2 If Not STANZAS.Item(WORD2) = "none" Then OUTFILE = OUTFILE & STANZAS.Item(WORD2) End If Set fo = fso.OpenTextFile(OUTFILE, 2, True) RESULTS = RESULTS & "Creating file " & OUTFILE & CRLF If WORD2 = "LOG.VOLUMES" Or WORD2 = "DB.VOLUMES" Then LOGDBVOLS = True Else LOGDBVOLS = False End If '**************************************************************************** ' If the first word is 'end' and this was a stanza that we created a file ' for then close the output file. '**************************************************************************** Elseif WORD1 = "end" And STANZAS.Exists(WORD2) Then fo.close OUTFILE = "" '**************************************************************************** ' For input recovery plan file lines that are between the beginning and end ' of a stanza that we created an output file for (i.e. we have previously ' constructed an output file name) write the line to the output file. If ' processing the log volume stanza or the database volume stanza then save ' the name of the log or database volume for later checking to determine if ' a volume by the same name exists. '**************************************************************************** Elseif Not OUTFILE = "" Then fo.writeline(ALINE) If LOGDBVOLS = True Then NbrV = NbrV + 1 VOLNAMES(NbrV)= WORD1 End If '**************************************************************************** ' If the prefix for the output files was not explicitly specified and this ' is the line within the plan file that identifies the plan file prefix, ' set the prefix for the output files to the prefix that was used to build ' the plan file. '**************************************************************************** Elseif OUTDIR = "" And WORD1 = "DRM" And WORD2 = "PLANPREFIX" Then OUTDIR = THEREST If Not Right(OUTDIR,1) = "\\" Then OUTDIR = OUTDIR & "." End If RESULTS = RESULTS & "set planprefix to " & OUTDIR & CRLF End If '/* select on first word of input line from the recovery plan file */ Loop '/* do while more lines in input recovery plan file */ fi.close '**************************************************************************** ' For each log volume and database volume, determine if a volume by the same ' name currently exists. If so, then indicate that the volume is going to be ' erased. '**************************************************************************** Set fo = fso.OpenTextFile(OUTDIR & "FILES.TO.BE.ERASED", 2, True) I = 0 FOUND = False Do While I < NbrV I = I + 1 if fso.FileExists(VOLNAMES(I)) then if FOUND = False then WARNING = _ "If executed, the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE batch" & CRLF & _ "program will delete the following log and db volumes if they exist" & CRLF & _ "and then reallocate them. During a normal disaster recovery scenario" & CRLF & _ "this is not a problem since you are going to restore data to them" & CRLF & _ "from the db backup." & CRLF & CRLF fo.writeline(WARNING) RESULTS2 = RESULTS2 & CRLF & WARNING FOUND = True End If fo.writeline(VOLNAMES(I)) RESULTS2 = RESULTS2 & VOLNAMES(I) & CRLF End If '/* the file exists */ Loop '/* do while more log and database volume names */ fo.close Wscript.Echo RESULTS If FOUND = True then Wscript.Echo RESULT |
The disaster recovery plan is divided into stanzas, which can be categorized as follows:
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. |
Table 28 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 28. 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 |
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 | -- | -- |
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.
Figure 90. 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 c:\win32app\ibm\adsm\server2\prepare\
Server for Windows NT - 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
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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Figure 91. 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
Installation Directory: c:\win32app\ibm\adsm\
end SERVER.REQUIREMENTS
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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. |
Figure 92. 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 Windows NT 4.0 running on an IBM
PC-350. The Windows NT 4.0 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 Windows NT 4.0 and server installation is Fred Myers.
Following are the instructions for installation of Windows NT
4.0
and the server:
end RECOVERY.INSTRUCTIONS.INSTALL
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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.
Figure 93. 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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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.
Note: | Because this script will invoke the TSM administrative command-line client, you should ensure that the communications options in the TSM administrative command-line client options file are set to communicate with the recovered TSM server before executing this script. To review the communications options used in the recovered TSM server, see the TSM server options file in the DSMSERV.OPT.FILE stanza. |
To invoke this script, the following positional parameters must be specified:
For example, to invoke this script using an administrator ID of don and a password of mox, enter the following command:
planprefixRECOVERY.SCRIPT.DISASTER.RECOVERY.MODE don mox
For additional information on planprefix, see Prefix for the Recovery Plan File.
The following stanza contains text strings that are too long to display in the hardcopy or softcopy publications. The long text strings utilize a plus symbol (+) to indicate string continuation on the next line.
Figure 94. Disaster Recovery Mode Script
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
begin RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script
@echo off
rem Purpose: This script contains the steps required to recover the server
rem to the point where client restore requests can be satisfied
rem directly from available copy storage pool volumes.
rem Note: This script assumes that all volumes necessary for the restore have
rem been retrieved from the vault and are available. This script assumes
rem the recovery environment is compatible (essentially the same) as the
rem original. Any deviations require modification to this script and the
rem macros and scripts it runs. Alternatively, you can use this
rem script as a guide, and manually execute each step.
if not %1.==. if not %2.==. goto start
echo Specify the following positional parameters:
echo administrative client ID and password.
echo Script stopped.
goto end
:start
rem Set the server working directory.
pushd c:\win32app\ibm\adsm\server2\
rem Restore server options, volume history, device configuration files.
copy c:\win32app\ibm\adsm\server2\prepare\DSMSERV.OPT.FILE c:\win32app\ibm\adsm\server2\dsmserv.opt
copy c:\win32app\ibm\adsm\server2\prepare\VOLUME.HISTORY.FILE c:\win32app\ibm\adsm\server2\volhist.txt
copy c:\win32app\ibm\adsm\server2\prepare\DEVICE.CONFIGURATION.FILE c:\win32app\ibm\adsm\server2\devconf.txt
rem create the log and database files.
call c:\win32app\ibm\adsm\server2\prepare\LOGANDDB.VOLUMES.INSTALL.CMD 1> +
c:\win32app\ibm\adsm\server2\prepare\LOGANDDB.VOLUMES.INSTALL.LOG 2>&1
type c:\win32app\ibm\adsm\server2\prepare\LOGANDDB.VOLUMES.INSTALL.LOG
rem Restore the server database to latest version backed up per the
rem volume history file.
c:\win32app\ibm\adsm\server\dsmserv -k "Server2" restore db todate=08/11/1997 totime=10:20:22
rem Start the server.
start c:\win32app\ibm\adsm\server\dsmserv -k "Server2"
echo Wait for the server to start. Ensure that the Administrative command
echo line client option file is set up to communicate with this server, then
echo press enter to continue recovery script execution.
pause
rem Set the administrative command line client directory.
pushd c:\win32app\ibm\adsm\saclient\
rem Register Server Licenses.
dsmadmc -id=%1 -pass=%2 -ITEMCOMMIT -OUTFILE=c:\win32app\ibm\adsm\server2\prepare\LICENSE.REGISTRATION.LOG +
macro c:\win32app\ibm\adsm\server2\prepare\LICENSE.REGISTRATION.MAC
rem Tell Server these copy storage pool volumes are available for use.
rem Recovery Administrator: Remove from macro any volumes not obtained from vault.
dsmadmc -id=%1 -pass=%2 -ITEMCOMMIT -OUTFILE=c:\win32app\ibm\adsm\server2\prepare\COPYSTGPOOL.VOLUMES.AVAILABLE.LOG +
macro c:\win32app\ibm\adsm\server2\prepare\COPYSTGPOOL.VOLUMES.AVAILABLE.MAC
rem Volumes in this macro were not marked as 'offsite' at the time
rem PREPARE ran. They were likely destroyed in the disaster.
rem Recovery Administrator: Remove from macro any volumes not destroyed.
dsmadmc -id=%1 -pass=%2 -ITEMCOMMIT -OUTFILE=c:\win32app\ibm\adsm\server2\prepare\COPYSTGPOOL.VOLUMES.DESTROYED.LOG +
macro c:\win32app\ibm\adsm\server2\prepare\COPYSTGPOOL.VOLUMES.DESTROYED.MAC
rem Mark primary storage pool volumes as ACCESS=DESTROYED.
rem Recovery administrator: Remove from macro any volumes not destroyed.
dsmadmc -id=%1 -pass=%2 -ITEMCOMMIT -OUTFILE=c:\win32app\ibm\adsm\server2\prepare\PRIMARY.VOLUMES.DESTROYED.LOG +
macro c:\win32app\ibm\adsm\server2\prepare\PRIMARY.VOLUMES.DESTROYED.MAC
rem Restore the previous working directory.
popd
rem Restore the previous working directory.
popd
:end
end RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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:
This script also invokes the TSM macros contained in stanzas:
To help understand the operations being performed in this script, see Backup and Recovery Scenarios.
Note: | Since this script invokes the TSM administrative command-line client, you should ensure that the communications options in the TSM administrative command-line client options file are set to communicate with the recovered TSM server before executing this script. To review the communications options used in the recovered TSM server, see the TSM server options file in the DSMSERV.OPT.FILE stanza. |
To invoke this script, the following positional parameters must be specified:
For example, to invoke this script using an administrator ID of don and a password of mox, enter the following command:
planprefixRECOVERY.SCRIPT.NORMAL.MODE don mox
For additional information on planprefix, see Prefix for the Recovery Plan File.
The following stanza contains text strings that are too long to display in the hardcopy or softcopy publications. The long text strings utilize a plus symbol (+) to indicate string continuation on the next line.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* begin RECOVERY.SCRIPT.NORMAL.MODE script @echo off rem Purpose: This script contains the steps required to recover the server rem primary storage pools. This mode allows you to return the rem copy storage pool volumes to the vault and to run the rem server as normal. rem Note: This script assumes that all volumes necessary for the restore rem have been retrieved from the vault and are available. This script rem assumes the recovery environment is compatible (essentially the rem same) as the original. Any deviations require modification to this rem script and the macros and scripts it runs. Alternatively, rem you can use this script as a guide, and manually execute each step. if not %1.==. if not %2.==. goto start echo Specify the following positional parameters: echo administrative client ID and password. echo Script stopped. goto end :start rem Create replacement volumes for primary storage pools that use device rem class DISK. rem Recovery administrator: Edit script for your replacement volumes. call c:\win32app\ibm\adsm\server2\prepare\PRIMARY.VOLUMES.REPLACEMENT.CREATE.CMD 1 + c:\win32app\ibm\adsm\server2\prepare\PRIMARY.VOLUMES.REPLACEMENT.CREATE.LOG 2>&1 type c:\win32app\ibm\adsm\server2\prepare\PRIMARY.VOLUMES.REPLACEMENT.CREATE.LOG rem Set the administrative command line client directory. pushd c:\win32app\ibm\adsm\saclient\ rem Define replacement volumes in the primary storage pools. Must rem have different name than original. rem Recovery administrator: Edit macro for your replacement volumes. dsmadmc -id=%1 -pass=%2 -ITEMCOMMIT -OUTFILE=c:\win32app\ibm\adsm\server2\prepare\PRIMARY.VOLUMES.REPLACEMENT.LOG + macro c:\win32app\ibm\adsm\server2\prepare\PRIMARY.VOLUMES.REPLACEMENT.MAC rem Restore the primary storage pools from the copy storage pools. dsmadmc -id=%1 -pass=%2 -ITEMCOMMIT -OUTFILE=c:\win32app\ibm\adsm\server2\prepare\STGPOOLS.RESTORE.LOG + macro c:\win32app\ibm\adsm\server2\prepare\STGPOOLS.RESTORE.MAC rem Restore the previous working directory. popd :end end RECOVERY.SCRIPT.NORMAL.MODE script *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |
The contents of this stanza must be placed into a separate file which will be used by the LOGANDDB.VOLUMES.INSTALL script.
The contents of this stanza must be placed into a separate file which will be used by the LOGANDDB.VOLUMES.INSTALL script.
This script is invoked by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.
The following stanza contains text strings that are too long to display in the hardcopy or softcopy publications. The long text strings utilize a plus symbol (+) to indicate string continuation on the next line.
Figure 96. Install Database and Recovery Log Volumes Scripts
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
begin LOG.VOLUMES
c:\win32app\ibm\adsm\server2\logs\lg01x 12
c:\win32app\ibm\adsm\server2\logs\lg02x 8
end LOG.VOLUMES
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
begin DB.VOLUMES
c:\win32app\ibm\adsm\server2\dbs\db01x 12
c:\win32app\ibm\adsm\server2\dbs\db02x 8
end DB.VOLUMES
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
begin LOGANDDB.VOLUMES.INSTALL script
@echo off
rem Purpose: Create the log and database volumes.
rem Recovery Administrator: Run this to initialize a server.
rem Set the server working directory.
pushd c:\win32app\ibm\adsm\server2\
rem Attempt to erase any existing log and database volumes.
erase c:\win32app\ibm\adsm\server2\logs\lg01x
erase c:\win32app\ibm\adsm\server2\logs\lg02x
erase c:\win32app\ibm\adsm\server2\dbs\db01x
erase c:\win32app\ibm\adsm\server2\dbs\db02x
rem Create the log and database volumes.
c:\win32app\ibm\adsm\server\dsmserv -k 'Server2' install 2 FILE:c:\win32app\ibm\adsm\server2 +
\prepare\LOG.VOLUMES 2 FILE:c:\win32app\ibm\adsm\server2\prepare\DB.VOLUMES
rem Restore the previous working directory.
popd
end LOGANDDB.VOLUMES.INSTALL script
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
This macro is invoked by the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE script.
Figure 97. 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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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.
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 98. 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. */
upd vol c:\win32app\ibm\adsm\server2\stg\bk02 acc=DESTROYED wherestg=BACKUPPOOL
upd vol c:\win32app\ibm\adsm\server2\stg\bk01x acc=DESTROYED wherestg=BACKUPPOOL
upd vol c:\win32app\ibm\adsm\server2\stg\bk03 acc=DESTROYED wherestg= BACKUPPOOLF
upd vol BACK4X acc=DESTROYED wherestg=BACKUPPOOLT
end COPYSTGPOOL.VOLUMES.DESTROYED macro
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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.
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:
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.
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:
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 99. 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 c:\win32app\ibm\adsm\server2\stg\bk02 acc=DESTROYED wherestg=BACKUPPOOL
upd vol c:\win32app\ibm\adsm\server2\stg\bk01x acc=DESTROYED wherestg=BACKUPPOOL
upd vol c:\win32app\ibm\adsm\server2\stg\bk03 acc=DESTROYED wherestg= BACKUPPOOLF
upd vol BACK4X acc=DESTROYED wherestg=BACKUPPOOLT
end PRIMARY.VOLUMES.DESTROYED macro
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
begin PRIMARY.VOLUMES.REPLACEMENT.CREATE script
@echo off
rem Purpose: Create replacement volumes for primary storage pools that
rem use device class DISK.
rem Recovery administrator: Edit this section for your replacement
rem volume names. New name must be unique, i.e. different from any
rem original or other new name.
rem Set the utility directory.
pushd c:\win32app\ibm\adsm\utils\
echo Replace c:\win32app\ibm\adsm\server2\stg\bk02 DISK 16M in BACKUPPOOL
dsmfmt -data c:\win32app\ibm\adsm\server2\stg\bk02x@ 16
echo Replace c:\win32app\ibm\adsm\server2\stg\bk01x DISK 5M in BACKUPPOOL
dsmfmt -data c:\win32app\ibm\adsm\server2\stg\bk01x@ 5
rem Restore the previous working directory.
popd
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 c:\win32app\ibm\adsm\server2\stg\bk02 DISK 16M in BACKUPPOOL */
def vol BACKUPPOOL c:\win32app\ibm\adsm\server2\stg\bk02@ acc=READW
/* Replace c:\win32app\ibm\adsm\server2\stg\bk01x DISK 5M in BACKUPPOOL */
def vol BACKUPPOOL c:\win32app\ibm\adsm\server2\stg\bk01x@ acc=READW
/* Replace c:\win32app\ibm\adsm\server2\stg\bk03 FILES 4M in BACKUPPOOLF */
def vol BACKUPPOOLF c:\win32app\ibm\adsm\server2\stg\bk03@ acc=READW
/* Replace BACK4X COOL8MM 0M in BACKUPPOOLT */
def vol BACKUPPOOLT BACK4X@ acc=READW
end PRIMARY.VOLUMES.REPLACEMENT macro
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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 100. 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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
The following rules are used to determine where the volume history file is placed at restore time:
Note: | The volhprefix is set to the directory representing this "instance" of the TSM server which is typically the directory that the TSM server was originally installed from. |
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.
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 to the directory representing this "instance" of the TSM server which is typically the directory from which TSM was originally installed. |
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.
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 101. Configuration Files
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* begin VOLUME.HISTORY.FILE ***************************************************************************************************** * Tivoli Storage Manager Sequential Volume Usage History * Updated 08/11/1997 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 c:\win32app\ibm\adsm\server2\stg\bk03 * Location for volume TPBK05 is: 'Ironvault Inc.' 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 * Location for volume TPBK07 is: 'Ironvault Inc.' 1997/08/11 10:20:03 STGNEW 0 0 0 LIB8MM TPBK07 * Location for volume TPBK08 is: 'Ironvault Inc.' 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=c:\win32app\ibm\adsm\server2\stg DEFINE DEVCLASS FILESSM DEVTYPE=FILE MAXCAPACITY=100K MOUNTLIMIT=2 DIRECTORY=c:\win32app\ibm\adsm\server2\stg DEFINE DEVCLASS LIB8MM DEVTYPE=8MM FORMAT=DRIVE MOUNTLIMIT=1 MOUNTWAIT=60 MOUNTRETENTION=60 PREFIX=TIVSM LIBRARY=RLLIB DEFINE LIBRARY ITSML LIBTYPE=MANUAL DEFINE LIBRARY RLLIB LIBTYPE=MANUAL end DEVICE.CONFIGURATION.FILE *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* begin DSMSERV.OPT.FILE * Server options file located in c:\win32app\ibm\adsm\server2\dsmserv.opt TCPPort 1509 VOLUMEHISTORY c:\win32app\ibm\adsm\server2\volhist.txt DEVCONFIG c:\win32app\ibm\adsm\server2\devconf.txt end DSMSERV.OPT.FILE *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* begin DSMSERV.OPT.FILE * Server options file located in c:\win32app\ibm\adsm\server2\dsmserv.opt TCPPort 1509 VOLUMEHISTORY c:\win32app\ibm\adsm\server2\volhist.txt DEVCONFIG c:\win32app\ibm\adsm\server2\devconf.txt * The following option was added by PREPARE. DISABLESCHEDS YES end DSMSERV.OPT.FILE *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |
Figure 102. 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
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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.
This stanza is included in the plan file if the machine recovery instructions are saved in the TSM database.
This stanza is included in the plan file if the machine characteristics are saved in the TSM database.
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 103. 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.
Processor : x86 Family 5 Model 2 Stepping 11
Bus Type : AT 16-Bit bus
Keyboard Type : 101/102 Key Enhanced Keyboard
Pointer Type : PS/2 Mouse Buttons: 2
Equipment : 1 Parallel Port(s)
1 Serial Port(s)
1 Diskette Drive(s)
2 Fixed Disk(s)
Pointing Device
Math CoProcessor
Fixed Disk 1 : 609 MB
Total Physical Memory : 32,832 KB (33,619,968)
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:
end MACHINE.RECOVERY.MEDIA.REQUIRED
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-