>> On Wed, 25 Jan 2006 15:29:11 -0500, Dennis Melburn W IT743 <melburn.dennis 
>> AT SIEMENS DOT COM> said:


> Our configuration manager for our group of tsm servers has gone down and
> we need to restore the database for it.  The thing is, it was backed-up
> using virtual volumes to one of the other tsm servers.  We know which
> tape it is, but are unsure of how to do the restore.

You've got the VOLHIST and the DEVCONFIG, right?  Then this is just
like any other DB restore.

here's the "procedure" (shell script) I use for one of my TSM servers,
which does its database backup to remote volumes.


dbsize=1024
lgsize=256
ppsize=64

ndb=`expr \` expr $dbsize / $ppsize \` + 1`
nlg=`expr \` expr $lgsize / $ppsize \` + 1`

echo Making DB volume in $vg: $dbsize MB, $ndb PPs
mklv -y ttestdblv_01a $vg ${ndb}

echo Making DB volume in $vg: $lgsize MB, $nlg PPs
mklv -y ttestlglv_01a $vg ${nlg}

echo dsmserv format 1 /dev/rttestlglv_01a 1 /dev/rttestdblv_01a
dsmserv format 1 /dev/rttestlglv_01a 1 /dev/rttestdblv_01a

echo dsmserv restore db TOD=TODAY TOT=NOW
dsmserv restore db TOD=TODAY TOT=NOW


Define the DB and log volumes, format them, restore.  The 'which tape'
and 'where do I get it' are taken care of by reference to the volhist
and devconfig.



I'll put in a plug here for TEST YOUR RESTORE PROCEDURES.  We're in
uniquely poor positions to be caught with our pants down on that
issue.  I aim to be able to say "If you can't script it, you don't
understand it", without shuddering inside.




- Allen S. Rout