Hi i know your problem,
The first thing i did after coming back from DR test , is that i enabled
collocation on tapepool and copypool ,
try to configure and define more drives to TSM , that is one way to go around ,
I did restore with 8-10 drives , in stk9710
2 gone bad after some time :-) but was sufficient.
Also check TCP/IP window size parameter in dsmserv.opt file if it is 0 make it
512 , recycle TSM ..That will help to
imrove performance ... .. You can start restartable restores if TSM disconnect
in between restoration.
Good luck
shekhar
Peter Koblauch <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/05/2001
07:57:32 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: how to speed up NT restore?
Hello,
I have been restoring an NT client for about 8 hours now, a bare-metal
restore.
The server is an RS/6000 at ADSM 3.10.
The problem is that it until now only some MBs have been restored and
the client
will need many GBs before it is done ... Looks like this could take
days.
The activity log and 'q session' shows that the restore session is doing
numerous
( DLT) tape mounts, and even when no mounts are outstanding very little
data is
transferred from the server to the client. Looks like the data for this
client might be spread
over hundreds of tapes. The storage pool for this client is not
collocated.
Is there a way to speed up the restore?
Would it make sense to do an "export node" to tapes followed by an
"import node" in order to force
the data to fewer tapes or would I then just be spending time in the
"export" instead?
Is there something else I can do?
--
any help would be appreciated!
thanks,
Peter Koblauch
$RFC822.eml
