Hi,
I have SELFTUNEBUFpoolsize Yes.. shouldn't that be sufficient? - but I do
see that my Cache hit percent is low..
Cache Hit Pct.: 97.15
Cache Wait Pct.: 0.00
Does anyone have any suggestions on how much to increase the size of the
pool.
These are my current Server options: (AIX 4.3.3, TSM 4.2.1.9)
Server Option Option Setting Server Option Option Setting
----------------- -------------------- ----------------- ----------------
----
CommTimeOut 7,200 IdleTimeOut 120
BufPoolSize 65536 LogPoolSize 512
MessageFormat 1 Language en_US
MaxSessions 25 ExpInterval 0
ExpQuiet No EventServerLogg- Yes
ing
MirrorRead DB Verify MirrorRead LOG Verify
MirrorWrite DB Sequential MirrorWrite LOG Parallel
VolumeHistory /adsmlog/logs/volh- VolumeHistory
/usr/tivoli/tsm/se-
ist.txt
rver/bin/volhist.-
txt
Devconfig /adsmlog/logs/devc- Devconfig
/usr/tivoli/tsm/se-
onfig.txt
rver/bin/devconfi-
g.txt
TxnGroupMax 256 MoveBatchSize 100
MoveSizeThresh 500 StatusMsgCnt 10
RestoreInterval 1,440 UseLargeBuffers Yes
DisableScheds No NOBUFPREfetch No
AuditStorage Yes REQSYSauthoutfile Yes
SELFTUNEBUFpool- Yes SELFTUNETXNsize No
size
DBPAGEShadow No DBPAGESHADOWFile dbpgshdw.bdt
QueryAuth None LogWarnFullPerC- 90
ent
ThroughPutDataT- 0 ThroughPutTimeT- 0
hreshold hreshold
NOPREEMPT ( No ) Resource Timeout 10
TCPPort 1500 HTTPPort 1580
TCPWindowsize 65536 TCPBufsize 16384
TCPNoDelay No CommMethod TCPIP
CommMethod HTTP MsgInterval 1
Enable3590Library Yes ShmPort 1510
FileExit /var/log/dsmc/even- UserExit
t.log(APPEND)
FileTextExit AssistVCRRecovery Yes
AcsAccessId AcsTimeoutX 1
AcsLockDrive No AcsQuickInit No
SNMPSubagentPort 1521 SNMPSubagentHost 127.0.0.1
SNMPHeartBeatInt 5 TECHost
TECPort 0
%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Jane Bamberger
IS Department
Bassett Healthcare
607-547-4784
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
David Longo
Sent: Thursday, February 21, 2002 9:26 AM
To: [EMAIL PROTECTED]
Subject: Re: Expiration processing
One simple step that definitely improves expiration processing speed is
having enough BUFPOOLSIZE. do a q db f=d and see what the "cache
Hit Pct" is. Ideally is 98 % or better. If much lower, even 90% then
expire
will take longer. Also "Cache Wait Pct" should always be zero.
David Longo
>>> [EMAIL PROTECTED] 02/21/02 09:08AM >>>
Hi,
I think you might be running into the same problem we are - our expire
command never stops - but we do not see any more expired after about 1
hour.. it examines millions of files - but only expires about 20 or 30
thousand. IBM is lookining into the problem, and we have provided traces,
and tried different solutions. Right now we run the command every morning
with:
expire inventory skipdirs=yes dur=120
TSM: 4.2.1.9
AIX 433
IBM 3494 Library
We also have a terrible time with scratch tapes. Some days we have 60 then
none.
Jane
%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Jane Bamberger
IS Department
Bassett Healthcare
607-547-4784
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Tony Jules
Sent: Tuesday, February 19, 2002 12:28 PM
To: [EMAIL PROTECTED]
Subject: Expiration processing
We run expiration daily for a couple of hours, and we realized
> that we were
> not getting enough scratch tapes back. We decided to run expiration
> indefinitely until all objects that need to be expired are removed.
> Expiration is been running for a week with 9 millions objects
> expired. Is there a way to find out how many objects are eligible for
> expiration? That way, I can determine how long it is going to take.
>
> Thank you
Tony Jules
ITS / Olympus America Inc.
631-844-5887
[EMAIL PROTECTED]
"MMS <health-first.org>" made the following
annotations on 02/21/02 09:38:37
----------------------------------------------------------------------------
--
This message is for the named person's use only. It may contain
confidential, proprietary, or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it, and notify the
sender. You must not, directly or indirectly, use, disclose, distribute,
print, or copy any part of this message if you are not the intended
recipient. Health First reserves the right to monitor all e-mail
communications through its networks. Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where the
message states such views or opinions are on behalf of a particular entity;
and (2) the sender is authorized by the entity to give such views or
opinions.
============================================================================
==
