Re: restore directly from copy pool tapes

2006-08-09 14:04:45
Subject: Re: restore directly from copy pool tapes
From: William Boyer <bjdboyer AT COMCAST DOT NET>
Date: Wed, 9 Aug 2006 14:05:29 -0400
Only thing I would disagree with is the order of your checkins. Maybe for an 
actual disaster, but for a D/R test where you have your
copypool tapes shipped to the recovery center, depending on the timing of the 
dbbackup you'll be restoring and those tapes, there
could actually be "live" tapes that your restored DB doesn't know about if they 
were created and shipped after your restore point.
Those "live" tapes will then be checked in a scratch, possibly overwritten 
depending on what you do at D/R. If they need to be used
later, they are now no good.

I always load all my copypool tape in the library and do a checkin search=yes 
stat=private. Then if I have any scratch tapes I want
to use, I'll check them in search=bulk. That way I won't accidentially 
overwrite good data.

Just my $.02 worth...and that may even be over-priced!

Bill Boyer
"Law of Cybernetic Entomology - There is always another bug." - ??

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Kauffman, Tom
Sent: Wednesday, August 09, 2006 11:31 AM
Subject: Re: restore directly from copy pool tapes

No problem.

Rebuild (from mksysb) your TSM server.

Restore your TSM database (you'll need the current TSM device config file and 
volume history file, with the device config file
changed to match the proper rmt names for the tape drives) --

OR -- we have a custo D/R device config file that defines the library as type 
manual, not SCSI, with one tape drive and path. We
update the path to match the machine's tape drive definition for the first LTO 
Then we restore the TSM database, specifying the volume number, and mount the 
tape manually.

Once TSM is up, delete the paths and re-define them to match the new 

Then 'upd vol * acce=unav whereacce=reado,readw" to mark all the primary tapes 

And 'upd vol * acce=reado whereacce=of' to mark all the off-site tapes 

File the library, if you haven't already done so, and then:
'audit libr <your name> checklabel=barcode'
'checkin libv <your library> search=yes stat=scr checklabel=barcode' to check 
in any scratch tapes 'checkin libv <your library>
search=yes stat=pri checklabel=barcode' to check in all the data tapes.

Run the checkins in that order; if you do stat=pri first you won't have any 
scratch tapes (we keep 20 initialized tapes off-site as
available scratch tapes to carry us through the first 48 hours of recovery).

Don't forget to disable or delete your scheduled events until you've got most 
of your recovery done -- a lot of your archival data
is going to expire on you fairly quickly if you're recovering from an older 
database backup.

We've been doing this for nearly seven years now, with no problems.

Tom Kauffman

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Richard Hammersley
Sent: Wednesday, August 09, 2006 10:40 AM
Subject: restore directly from copy pool tapes

I'm working on a disaster recovery scenario where our TSM server (AIX) and tape 
library (3584)that has 90 LTO tapes in tape pools is
destroyed and several other servers are destroyed.  We have approx. 85 copy 
pool tapes off site.

Our thought is to recreate the TSM server via mksysb, restore the TSM database, 
etc.  Then get several of our critical other systems
up and restore their data by using the copy pool tapes and then recreate the 
tapes in the tape pools in the tape library.

How does one set up the recreated TSM server so that it does not think that the 
tape pool tapes are in the tape library ?

How does one restore from copy pool tapes ?

Are we going about this in a realistic way ?

Thank you.

CONFIDENTIALITY NOTICE:  This email and any attachments are for the exclusive 
and confidential use of the intended recipient.  If
you are not the intended recipient, please do not read, distribute or take 
action in reliance upon this message. If you have
received this in error, please notify us immediately by return email and 
promptly delete this message and its attachments from your
computer system. We do not waive attorney-client or work product privilege by 
the transmission of this message.