I agree with Dwight.
When going to a cold DR site (i.e., one that has a bare host OS, not one that 
belongs to you and can be pre-configured), 
I tell my customers not to mess with trying to update the devconfig and prepare 
scripts, on V5 or V6.

Just go ahead and install the TIP with the TSM server.
Use the TIP to define the library and 1 drive, any libname you want.
Check in your DB tape.
Restore your data base.
Use the TIP to update the (newly restored) library and drive paths to match the 
DR site library (assuming SANDISCOVERY doesn't patch it for you).

I know that seems counterintuitive, but the time to install the TIP is pretty 
short now on decent-capacity hardware.
And it makes library/drive definition so easy, it takes less time than 
untangling the messes I've seen some people get into trying to tweak a 
devconfig if they don't have experience with it.

W  



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Dwight Cook
Sent: Tuesday, August 13, 2013 10:37 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] DR with automated library

Well, all you have to do is start a bare TSM server and define your library, 
check in your DBB tape, halt TSM, and then do your restore.
I like doing it that way rather than using OS commands to mount a tape on a 
drive and then classify that as a ~manual library~ in order to do my restore.
All of my DR tests have been with 3494's, 3584's or 3576's being used as 
"automated" libraries. (and been doing them for about 16 years...)

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Ehresman,David E.
Sent: Tuesday, August 13, 2013 9:06 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] DR with automated library

Has anyone successfully done a DR (test) using an automated library (as opposed 
to defining a manual library)?  If so, what are the needed changes to devconfig?

David