ADSM guru's:

We have been backing up our unix systems to ADSM incrementally and archiving
our databases into ADSM primary pools daily.  All disk pools are fully
migrated to tape pools daily.  We also backup all our primary pools to copy
pools and move the copy pool volumes offsite.  We also backup the ADSM
database to 3590 daily and move this tape offsite.

We wish to simulate a disaster without disturbing the ADSM setup too much!

We intend to restore the ADSM database from the 3590 backup, then mark all
primary volumes (disk and tape) unavailable and check in all (or perhaps
selected) copy pool volumes.  Using this restored ADSM database and copypool
volumes only we wish to restore selected  unix files and retrieve from
archive a database.

My question is: Will a restore/retrieve command use copy pool volumes if
primary pool volumes are unavailable or do we have to "restore stgpool" all
the primary pools prior issuing restore/retrieve commands for unix files.
If we have to issue "restore stgpool" that may take a while as our database
archive primary pool is over 900Gb in size!  Perhaps "restore volume" for
selected volumes (created recently in VOLHIST) would suffice?

Any gotchas to watch out for?


Ken Chamberlain
University of Toronto
Phone:(416) 978-1582
Fax:  (416) 971-2085
E-mail: ken.chamberlain AT utoronto DOT ca