When you start ADSM with the DSMSERV RESTORE DB command, ADSM looks in the
devconfig file to find the devclass definitions and looks in the
volumehistory file to find the last good backup tape.

This is VERY convenient way to recover if you have an on-site data base
failure.

However, if you are conducting an off-site disaster test and ADSM is already
installed and you KNOW what tape you want to use, you can issue the DSMSERV
RESTORE DB command and specify the correct volume on the command - this is
described in the ADMIN ref book under the DSMSERV RESTORE DB command - see
the example that says "Volume history not available".

You can also construct a devconfig and volume history file manually at the
disaster site, if you need to.

Just remember if you don't make devconfig and volumehistory available to
ADSM, YOU are responsible for keeping track of what you need to do the
recovery

***************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
***************************************************************

!




If you are conducting an of

> -----Original Message-----
> From: Joel Fuhrman [SMTP:joelf AT CAC.WASHINGTON DOT EDU]
> Sent: Wednesday, January 06, 1999 3:13 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      backup database - wish list
>
> For IBM - In order to recover from a disaster, my understanding is that in
> addition to the db-backup tape the corresponding volume history file is
> required and for it to be available, I have to back it up outside of ADSM.
> If that is true, are there any plans to improve the 'backup database'
> command to copy that file to the db-backup tape?  The device configuration
> file should also be included.  Then the recovery process would have all
> the
> information it needs to rebuild the server environment.