ADSM-L

Novell disaster - large restore

2000-03-07 11:00:51
Subject: Novell disaster - large restore
From: Julie Phinney <jphinney AT HUMANA DOT COM>
Date: Tue, 7 Mar 2000 11:00:51 -0500
We have to do a recovery of a large Novell server (100GB).   We have TSM
3.7 running on the OS/390 server.  We are going to put TSM on the client
before we start the restore  (installing it now).    (The backups were done
via ADSM 3.1.0.6)
I'm going to recommend   RESOURCEUTILIZATION 10.
Speed is the highest priority right now.   I did a select from volumeusage
to get a tape list, and it looks like 600 tapes...  though I suppose all of
them don't have active versions.
We are going to be doing a simultaneous restore using Arcserve on another
box,  then using ADSM with the -IFN option     and will cancel the first
restore on the first box if it appears to be very slow,  so it won't fight
with the 2nd ADSM restore which will probably start in a few days.
My question is    for PROCESSORUTILIZATION    there is no maximum?   I
haven't fooled with that parm much before.    Do any of you have a
recommendation?
The restore will be of extreme priority,  nothing else should be running on
this machine.
We're intending to do a RES   DATA:*     -SU=Y
anything else that could make it faster?
Is there any reason -REP=ALL  would be valuable?    I'm told it should be
an empty drive.   For restart purposes, maybe?
Does -REP=ALL    slow things down?
May be worth it to be safe and just specify it.     I wouldn't want to be
waiting on a prompt.
I thought there were times before when restoring to a supposedly empty
drive, that we got prompted for replacement  (very old versions of ADSM
though)
Thanks for any suggestions!
Julie
<Prev in Thread] Current Thread [Next in Thread>