If you missed it maybe someone else missed it too. So I'm re-posting it to
the whole list.
Thanks to Mark for sharing knowledge.
---------------------- Forwarded by Zlatko Krastev/ACIT on 25.09.2001 00:39
---------------------------
"Remeta, Mark" <[EMAIL PROTECTED]> on 06.09.2001 18:22:36
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Archive problems
Martha, here is a response I received from Tivoli support:
Hi Mark,
I know I haven't spoken to you in a while regarding this problem,
and I apologize for that; but I have been able to determine the procedure
to help you improve your archive performance. The 3.7.2 and 4.1.2 or higher
TSM clients are designed to no longer backup duplicate directories. That
is, directories with the same name in the same path with the same
description will only have 1 copy on the TSM server. What we need to do to
ensure all old duplicates are deleted and the new, more efficient archive
tables are being used by your nodes, is run the following commands from a
TSM Admin command line:
CLEAN ARCHDIR <nodename> SHOWSTATS
DELETE ARCHDESCRIPTIONS <nodename>
CONVERT ARCHIVE <nodename> REORG=YES
Please note that the DELETE ARCHDESCRIPTIONS command DOES NOT remove
all the descriptions from your archive packages, it only deletes entries
from some of the descriptions tables. Once you run CONVERT ARCHIVE, the
description entries are rebuilt from the file data using the new, more
efficient description table, so you will still be able to access all your
archives by description. When this is completed, you can run CLEAN ARCHDIR
<nodename> SHOWSTATS again to view changes. SHOWSTATS output may still
show duplicate directories, but these are not true duplicates because they
have different descriptions, so the output is correct.
After all old nodes have been converted using this process, you should
see improved performance. New nodes using 4.1.2 and higher clients
connecting to 3.7.4 and higher or 4.1.2 and higher TSM servers will already
be using the new tables and do not need to go through the above conversion
process. Even after this conversion, as the number of archives continues
to grow, you may still experience slowdown as it becomes more and more time
consuming to query and insert new archives into the existing tables. As
you have already seen, using a new nodename for archives does workaround
this problem.
-----Original Message-----
From: Martha Musacchio [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 11:07 AM
To: [EMAIL PROTECTED]
Subject: Re: Archive problems
Valerie,
I can't find any documetation for these commands. Do you know where I can
find
it? I too have noticed the slowness on my AIX server and would like to do
as
you
suggest, but I would like to know what the commands are doing prior.
Thanks,
Martha
> MIME-Version: 1.0
> Date: Thu, 6 Sep 2001 10:29:46 -0400
> From: Valerie Fisher <[EMAIL PROTECTED]>
> Subject: Re: Archive problems
> Comments: cc: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
>
> Don't know if this would help your platform but when I upgraded from ADSM
> 3.1 on AIX to 4.1.4.0 we had the same slowness -
> were advised from the TSM support folks to execute these commands on the
TSM
> server on AIX
> and the 3 clients it serves from the dsmc prompt.
>
> clean archdir (nodename) delete duplicates
>
> convert archive (nodename) reorg=yes
>
> and it did make the archive of many files go faster.
>
> Good luck !
>
> -----Original Message-----
> From: Hunley, Ike [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 05, 2001 5:27 PM
> To: [EMAIL PROTECTED]
> Subject: Archive problems
>
>
> Hi,
>
> I hope someone else out there has had this problem. I need answers
pronto!
>
> TSM 4.3.1 is on OS/390 V2R9, AIX TSM is 3.1.06
>
> Archive is SLOW! Sometimes the process stops for no reason we can find.
> File sizes range from 80 bytes to 800MB.
>
> 5 byte file: 4.17 seconds
> 6,144,000 byte file 7.15 seconds
>
>
>
>
>
> Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
> affiliate companies are not responsible for errors or omissions in this
> e-mail message. Any personal comments made in this e-mail do not reflect
the
> views of Blue Cross Blue Shield of Florida, Inc.
Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.
"Gill, Geoffrey L." <[EMAIL PROTECTED]> on 24.09.2001 18:44:42
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Archive hangs and Poor Archive Performance at TSM 4.1.2
& 4.2
>As already Petr wrote use convert archive. This a
>half-documented command -
>it is not available (in my) Administrator's Reference but you
>can find it
>through help as you can see:
>
>tsm: PUMBA.ACIT.BG>help convert arch
>CONVERT ARCHIVE
>CONVERT ARCHIVE (Allow Clients to Query Archive Files by Description )
I've been trying to pay attention to this thread, and others, about poor
archive performance, but I haven't seen the response I'm looking for or
just
missed it. I am on AIX 4.3.3 with TSM 4.1.2. I don't see any help on this,
is it a 4.2 function or something higher than what I currently have on 4.1?
Is this a server command or client? I have strange behaviors on archives
I'd
like to fix and am wondering if this would help.
Thanks,
Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail: [EMAIL PROTECTED]
Phone: (858) 826-4062
Pager: (888) 997-9614
