The following is a procedure we developed using the IBM Redbook "ADSM
Server for Windows NT Configuration and Recovery Examples"
(SG24-4878-00). We did have a successful recovery test using this
process up through recovering our disk storage pools - we didn't have a
true disaster, so we did not have any tapes that were "destroyed" and
therefore haven't tested that part of the process yet. You will want to
fill in your own device class, storage pool names, etc. where
appropriate...as always - "your mileage may vary", "this works for me
and may not for you", etc....Also, I'm sure many people are using DRM
which is another way to automate/assist with this process...
Server Backup
Configuration Data
Location of following macros/commands/procedures/lists:
On Server...C:\ADSMDRP and C:\WIN32APP\IBM\ADSM\SERVER
Created OFFSITE.MAC macro to perform configuration queries:
query option
query status
query db format=detail
query dbvol format=detail
query log format=detail
query logvol format=detail
query stgpool format=detail
query volhist type=dbb
query vol format=detail
query dbb format=detail
Created OFFSITE.CMD batch file that includes the following:
Copies DSMSERV.OPT to C:\ADSMDRP\DSMSERV.OPT
Runs OFFSITE.MAC macro with output to file
C:\ADSMDRP\SERVER.REP
Backs up volume history file to C:\ADSMDRP\VOLHIST.OUT
Backs up device configuration file to
C:\ADSMDRP\DEVCNFG.OUT
Copies the ADSMDRP directory to ADSM_UPGRADE
(secondary backup)
Created WINAT command (executed at 6am daily) to run OFFSITE.CMD
batch file
Administrative Events
Defined schedules to back up the Disk Storage Pools and
Database.
ARCHIVE_BACKUP
BACKUP_POOL_BACKUP
DB_BACKUP
EXCHANGE_BACKUP
EXCHANGE_PI_BACKUP
Defined schedules to back up the Tape Storage Pools.
ARCHIVE_SPILL_BACKUP
BACKUP_SPILL_BACKUP
EXCHANGE_SPILL_BACKUP
Defined Operations Procedure to move volumes offsite.
Server Restore
Server Recovery
Retrieve documentation/media from vault.
Install/Setup Server hardware.
Install Windows/NT Server.
Install ADSM/NT Server + Administrative Client.
Locate most recent configuration data.
DSMSERV.OPT
SERVER.REP
VOLHIST.OUT
DEVCNFG.OUT
Browse volume history file, determine latest database backup
volumes.
BACKUPFULL
BACKUPINCR
Copy volume history, device configuration and server options
files to the new ADSM
Server directory.
Copy a:VOLHIST.OUT c:\WIN32APP\IBM\ADSM\SERVER
Copy a:DEVCNFG.OUT c:\WIN32APP\IBM\ADSM\SERVER
Copy a:DSMSERV.OPT c:\WIN32APP\IBM\ADSM\SERVER
Verify DSMSERV.OPT parameters.
VOLUMEHistory
DEVCONFig
TCPSERVERADDRESS (Clients Only...DSM.OPT)
Determine size of ADSM Database and Recovery Logs.
SERVER.REP
Install and prepare the Database and Recovery Log.
(In C:\WIN32APP\IBM\ADSM\SERVER)
If recovery server has previously been installed:
delete database (DB1.DSM)
delete recovery log (LOG1.DSM)
delete DSMSERV.DSK (pointer to Log and
Database location!)
Reinstall server:
Batch file C:\adsmdrp\alloc.bat will run DSMFMT
commands to
create Storage Pool files
(remember to use new names!) plus
commands to create
directories on D drive for Log, Database
and Storage Pools.
DSMSERV FORMAT 1 d:\adsm_log\log00.dsm 1000 1
d:\adsm_db\db00.dsm 2000
(long wait after ANR0306I message, no other messages
while database is formatted!!!)
(above command takes 45 minutes to complete)
Database Recovery (ADSM NT Admin Guide pg. 396)
Confirm volumes required for restore.
DSMSERV restore db todate=today preview=yes
Obtain required volumes displayed in above command output.
Recover the database.
DSMSERV restore db todate=today
(command takes 15 minutes to complete)
Restart the Server and verify the database has been restored
correctly.
Using the ADSM Server Utilities, Start the ADSM SERVER
Service
ADSM> query node
ADSM> query volume
Storage Pool Recovery
Update Volumes...
Disk storage pools will be marked offline when Server
starts.
Change volume access mode to unavailable for lost tape
volumes.
ADSM> update volume * acc=unavailable
wheredevc=dlt7000c
Change lost scratch volumes to unavailable.
ADSM> query libvolume
ADSM> checkout libvolume stk_9710_00 000nnn
checklabel=no
force=yes
Check status and update volumes in the Disaster Recovery
Copy pool.
ADSM> query volume stgpool=dr_pwm
Update volumes not taken offsite prior to disaster.
ADSM> query volume access=readw stgpool=dr_pwm
ADSM> delete volume "volume" discarddata=yes
Change offsite volumes to onsite/mountable.
ADSM> update volume * acc=readwrite
wherestg=dr_pwm
*** At this point clients can recover data ***
*** Backup and archiving is not available ***
Restore Primary Pools...
Format volumes for disk pools (using new names for the
storage pool files!).
dsmfmt commands already done in alloc.bat above
define volume commands for the
various storage pool files as follows:
ADSM> define volume backup
d:\adsm_storage\bkup10.dsm
(where d:\dir\file is taken
from the above alloc.bat file)
Update old volumes, access mode of destroyed.
ADSM> query volume status=offline
ADSM> update volume * acc=destroyed
wherestatus=offline
Restore backup data to storage pool volumes.
ADSM> restore stgpool backup
ADSM> restore stgpool archive
ADSM> restore stgpool exchange
ADSM> restore stgpool exchange_pi
(above commands take 60 minutes to
complete)
Update primary tape pools, access mode of destroyed (for
unavailable volumes!).
ADSM> update volume * acc=destroyed
whereaccess=unavailable
Create new scratch tape volumes, place new tapes in
library.
ADSM> dsmlabel -drive=mt3.0.0.0,1032
-library=lb5.0.0.1 -search
-keep -overwrite
-keep -overwrite
(( respond to prompt for labels ))
(( respond to prompt for labels ))
Check in all scratch volumes.
ADSM> checkin libvolume stk_9710_00
status=scratch search=yes
Restore primary tape pool (if "destroyed").
ADSM> restore stgpool backup_spill
(archive_spill, exchange_spill)
Sync database and storage pools.
audit volume d:\adsm_storage\bkup00.dsm -or-
000nnn
audit library stk_9710_00
-----Original Message-----
From: Donald W. Daniels/FFIC
[SMTP:Donald_W._Daniels/FFIC AT FFIC DOT COM]
Sent: Thursday, July 02, 1998 8:31 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Bare-metal recovery of ADSM Server (WinNT
version 3)??
I would appreciate input/comments from anyone with experience in
performing
disaster recovery of a Windows NT ADSM Server. In my case, this
server is the
only ADSM Server currently installed. Following are the steps
that I think
would work:
folllowing are backed up and stored offsite:
$ Volume history file
$ Device configuration file
$ Server options file
$ Database and recovery log set up
. Full db backup and incrementals
. Copy storage pool volumes
To restore to a fresh machine:
. Install WinNT Server
. Install ADSM
. restore ADSM information using procedures defined in "6.1.7.1
Restoring a
Database to a Point in Time" of the Admin Guide.
Also, any thoughts about utilizing Forward Recovery?
Thanks,
Don
ddaniels AT ffic DOT com
|