I just got through with a DR test where the only entry in my volhist was the
single dbb entry I wanted it to use to recover with.
Worked like a champ after I figured out that async I/O wasn't activated at
the AIX level... that killed me for hours :-(
I also totally change around my devconfig because at the DR I had a 3494 but
in production I have a 3584.
So you can jack around the files just like in V5, you just have to know how
to structure it.  With my volhist, I just took everything including the
**********************************************
Lines around the dbb entry.

Just make sure you email out or get your drm file off your server daily...
It has the critical info you need and you can cut it down to a manageable
size when DR'ing.

Dwight

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
TSM
Sent: Thursday, March 24, 2011 2:09 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Question about TSM 6 server desaster recovery

Hello,

we have no actual desaster, but we have a question about TSM 6 server
desaster recovery.

For a TSM server desaster recovery with TSM version < 6 it was possible to
modify older devconfig and volhist files before running a TSM db restore.
(devconfig: library-slot of cartridge;
 volhist: cartridge label, any new date and time, devclass).
Now with TSM version 6 there are more data for every TSM db backup in the
volhist file. Do we really need these data with a TSM db desaster recovery
or is it possible to set dummy numbers?

Have you any experience with this?

Thanks in advance
Andreas.