Joni --

I can't help with the DR Manager because we don't use it -- back in the
ADSM 2.x days it seemed to pricey to us and I couldn't see anything it
was doing (then) that we couldn't do on our own. I haven't looked at it
since, as our processes work.

But -- there is a bit of prep work required before you're ready to use
the DR Manager at D/R, and I can help with some of that.

First you need to restore the TSM environment. To assist in this, I have
a /DR directory on my root volume. Once a week I snapshot my TSM volume
group info to this directory: lsvg adsmvg >/DR/adsmvg.vglst and lsvg -l
adsmvg >/DR/adsmvg.lvlst. These allow rebuilding the volume group from
scratch if the automated process fails. I also run a savevg: savevg4vp
-I -e -f /DR/backup.adsmvg adsmvg. The exclude file ('-e' option)
contains /* -- exclude everything -- so all that gets created is the
contains /* -- exclude everything -- so all that gets created is the
meta-data for the vg. Now, when we run our weekly mksysb, we have
captured the data required to recreate the TSM volume group.

Now - at D/R.

Restore the AIX environment. We boot to service mode from CD and select
'restore system from a backup tape'; this will 'clone' the system,
getting any additional device drivers required for the hardware from the
CD. Then do a restore of the tsm vg: restvg4vp -f /DR/backup.adsmvg
<list of hdisks to use>. (The '4vp' is because we run SSD and multiple
paths to our ESS).

And now you're ready to recover your device config and volume history,
make any changes required to the device config, and restore the TSM
database. These are covered (IIRC) in the DR Manager scripts and
procedures, so someone else needs to step in here :-)

Tom Kauffman
NIBCO, Inc