Andrew Raibeck <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
03/31/2005 10:36 AM
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L@VM.MARIST.EDU
cc:
Subject:Re: Archive very, very slow
I doubt very much that tracing di
I doubt very much that tracing did anything to improve the performance. If
anything, it impedes performance. There is most likely something else
going on in the environment, though what I do not know.
The data transfer time of 323 seconds suggests that it took TSM 5 minutes
and 23 seconds to move
> We recently migrated from a locally attached 3590 E11 tape drive to two
> 3592 tape drives in a 3494 tape library. We installed TSM 5.2.4.0 on a
> p5 570 lpar running AIX 5.3. Our data is on an IBM ESS 800. Every day
> we quiese the application and flash copy it then mount the flash copy
> vol
I turned on tracing and ran an archive with the following command:
dsmc archive -traceflag=service,memory
-tracefile=/tmp/tsm/trace/dbext_trace.out -tracemax=5000 -verbose
-desc="Old IDX Tape Backups for /restore/dbext - 2005Mar30"
-filelist=/tmp/tsm/archive_list_dbext_2005Mar30 -archmc=AIX-1YEAR
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Galloway, Gary M
>COMMMethod is set to SHAREDMEM and has been that way from the start.
>I'm got tracing turned on now so we will see if that reveals anything.
>Here is the summary of our archive from last night. Network(FIBER)
COMMMethod is set to SHAREDMEM and has been that way from the start.
I'm got tracing turned on now so we will see if that reveals anything.
Here is the summary of our archive from last night. Network(FIBER)
throughput seems to be ok but the Aggregate is abysmal. Compression is
also turned off si
We also recently migrated from SCSI attached 3590E drives to SAN
attached 3592 drives (both in a 3494 library).
Unfortunately, we only saw an increase in the performance with
the new tape drives.
As Richard mentioned, it may be an issue with the mounting of
the data on th
On Mar 30, 2005, at 2:14 PM, Miller, Ila wrote:
...The data is mounted to the TSM server so
the TSM server is also the client and the data should not be going over
the network at all. ...
Just a minor thought: Your COMMMethod is probably TCPIP, meaning that
the I/O would be going through the TCP/IP
