Restore Speed

[Xenocide911]

What is it that a node can backup at 6,000 kb/sec and only restore at 80 kb/sec. It's not tape reads either, I did this with a node that backs-up to a storage pool before migration occurred. Server and Client version 5.3.2

 

[Mag0007]

do you have co-location enabled? This can improve restore speeds by a LOT!

 

[Xenocide911]

No, but as mentioned this was comming from a disk pool. Also it's only with the GUI, I get great speed through the command line restore.

 

[Mag0007]

so, when you do via GUI you get slow speeds?
But when you do dsmc -res you get good speeds?

 

[Yrrk]

Xeno - try FTP'ing a 100MB+ file to/from the TSM server and client with the problem and confirm you get the expected throughput rate.

 

[Xenocide911]

I can get the expected speed. It will back-up between 5,000 and 6,000 kb/sec. On the restore with the command line I got a restore rate of 5,200 kb/sec. When I used the GUI I got a restore speed of 72 kb/sec.

 

[Yrrk]

ah, i missed the above where you mentioned the cmdline speed is decent.

Is this a file system backup/restore?
What OS is the client, windows 2000/2003?
What version of the baclient?
default install or have you tweaked any of the settings under preferences in the baclient GUI?
what are you restoring? how much data in GB and files?

 

[Xenocide911]

Yeah, I'm practicing restoring a server. So I've got a base install of W2K3 and I'm laying down the rest of the C:, which is about 20,000 objects and 2gigs. The server and client are at 5.3.2. Opt file:
NODENAME TAP01
PASSWORDACCESS GENERATE
TCPSERVERADDRESS 10.7.3.166
MANAGEDSERVICES WEBCLIENT
schedmode prompted
ERRORLOGRETENTION 5
SCHEDLOGRETENTION 5
RESOURCEUTILIZATION 2
TCPPORT 1502

 

[Xenocide911]

I added an option to my dsm.opt file that appears to make the GIU as fast as the command line.

TESTFLAG DISABLENQR

I'm not sure what this flag does. Does anyone have an explanation?