ADSM-L

Re: [ADSM-L] 5.4 performance issues

2008-03-14 18:03:22
Subject: Re: [ADSM-L] 5.4 performance issues
From: Shawn Drew <shawn.drew AT AMERICAS.BNPPARIBAS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 14 Mar 2008 18:01:39 -0400
Since it didn't run to completion, can you tell, from the log, if it is
backing up all files again?   Or it is doing everything the same, except
it is just taking longer?


________________________________________________
Shawn Drew
Data Protection Engineer
Core IT Production
BNP Paribas RCC, Inc.




Internet
spr AT BUFFALO DOT EDU

Sent by: ADSM-L AT VM.MARIST DOT EDU
03/14/2008 05:02 PM
Please respond to
ADSM-L AT VM.MARIST DOT EDU


To
ADSM-L
cc

Subject
[ADSM-L] 5.4 performance issues





Hi All,

We recently upgraded the TSM clients on our cryus imap servers from
5.3.0.12 to 5.4.1.2 (and then 5.4.1.5), and since that upgrade, we have
seen the backups of about 4.5million files in each of our 12 spools go
from about 2.5 hours to approx. 4 days (had we let it run to completion).

Anyone else seeing issues with 5.4.x on Solaris clients with millions of
files?

Other vitals:
Server: 5.4.1.2 on AIX
Network: GB

Client OS Solaris 2.9
Filesystems are VxFS on an Hitachi 9960.

We have opened a PMR with IBM, and they want to run some traces, but we
have since reverted back to 5.3.0.12, and our 2.5hr backups.

We need to run 5.4 to stay supported, and a minimum of 5.4.1.2 for the
fix for the security issues in dsmcad, which we use for email restores on
these systems.

Thanks in advance for any insights anyone can provide.


Steve Roder
University at Buffalo
(spr AT buffalo DOT edu | (716)645-3564)


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.