With 12 different AIX production ADSM servers I have one small
     dedicated AIX server for dealing with all the production ADSM servers.

     On this box I have scripts that go out to the other servers and
     automatically ftp the volhist and devconfig files daily. I keep 7 days
     worth and save them with a server name prefix and a weekday suffix. (7
     copies is just so I don't automatically suck in a bad file and overlay
     a good one just prior to being notified a server is having problems)

     I also go out to each adsm server and query volhist t=dbb and stash
     that away in a file for quick access.

     Other helpful things are to know everything about every disk volume
     (storage, db, & log).

     Actually if you take a spare box, install adsm, lay down the volhist
     and devconfig, restore the db, AND THEN TRY TO START ADSM... you will
     learn about everything you currently don't have that you need to
     recover the environment.  It is a very big learning experience.

     later,
           Dwight


______________________________ Reply Separator _________________________________
Subject: Re: backup database - wish list
Author:  Chris.J.Roelofs (Chris.J.Roelofs AT MAIL.ING DOT NL) at unix,mime
Date:    1/6/99 9:56 AM


     Yes, that would be nice, but...

     The restore db process needs the volumehistory to determine which
     tape(s) is/are needed for the restore, and it needs the device
     configuration information to determine how to find and drive your
     hardware.

     This is typical bootstrapping, you can't restore a backup if
     information needed to read the backup is contained only within the
     backup.

     I once heard this explained like: You can never call your friend if
     only he knows his own phone number.

     Regards,

     Chris Roelofs
     Mainland Sequoia




______________________________ Reply Separator _________________________________
Subject: backup database - wish list
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at inet-1
Date:    06/01/1999 12:13 AM


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.