ADSM-L

Re: [ADSM-L] Restore performance puzzler

2008-06-25 17:57:17
Subject: Re: [ADSM-L] Restore performance puzzler
From: "Ribeiro, Ricardo" <Ricardo.Ribeiro AT SCHWAB DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 25 Jun 2008 14:55:50 -0700
Shawn,
Based on this information it appears that the VTL is only attached to
the TSM server correct? So, the data to the client is not going to be as
fast as restoring to the TSM server. Things to consider are...
What is the LAN speed and duplex settings for the client?
How is the LAN traffic when you are trying to restore? 
Is compression enabled on the TSM client side?
How many channels/threads/mount points are you allowing the client to
use?
What type of data are you restoring, compress, database data, etc?
Can you ping the TSM server from the client?
Can you ping the Client from the TSM server?

Anyway, I hope this helps!

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Shawn Drew
Sent: Wednesday, June 25, 2008 2:47 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Restore performance puzzler

5.4.1 AIX Server
5.3.4 AIX 5.1 Client

Performing a 12 gB restore.  (6x2gB files) The restore is performing at
a rate of about  250-500 KB/s with bursts up to a whopping 750KB/s
(Looking at the VTL drive monitor)

If we perform the restore locally to the TSM server's file system, it is
fast. (20-30 MB/sex) We can FTP the data to the client fast as well,
10-15MB/sec

A restore of the same files performed at the client crawls.   We are
upgrading to 5.3.6, which looks to be the newest AIX 5.1 client we can
use.  Any ideas?


Regards,
Shawn


This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in
error, please delete it and immediately notify the sender. Any use not
in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can
not guarantee the integrity of this message. BNP PARIBAS (and its
subsidiaries) shall (will) not therefore be liable for the message if
modified. Please note that certain functions and services for BNP
Paribas may be performed by BNP Paribas RCC, Inc.