Re: [ADSM-L] Resourceutilization allows more tape mounts than

Richard,
        Thank you for your reply.
        The clients I am referring to are AIX, as my original email
indicated.  Andy's explanation is a good one, and says the same thing
that the Performance Guide says.
        Neither explains the behavior we are seeing.  Resourceutil=10
should yield a maximum of 4 consumer sessions, and therefore a maximum
of 4 tape mounts.  So if maxnummp=4, then why are we still getting the:

ANR0539W Transaction failed for session 163135 for node APLORA01. This
node has exceeded its maximum number of mount points.

messages? Are we the only site seeing this?  Am I just nuts, or is TSM
really working differently than documented?  (Or both)  I guess I will
just reduce the resourceutil parameter until the problem goes away, and
just leave it a mystery.

By the way, this is a shared library, and as per Technote #1315592,
Resetdrives=yes on our shared library.


Best Regards,

John D. Schneider 
Email:  John.Schneider AT Mercy DOT net 


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Wednesday, September 24, 2008 2:44 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Resourceutilization allows more tape mounts than

Whenever you see a Windows backup using more drives than expected, all
the implications of DIRMc should pop into consciousness.  You can
examine what's most recently going to the tapes by using Query CONtent
with a negative Count value.

And we are grateful for Andy's past illumination on RESOURceutilization:
http://www.mail-archive.com/adsm-l AT vm.marist DOT edu/msg33426.html

    Richard Sims   http://people.bu.edu/rbs/
This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR
OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the
use of the addressee(s) named above. If you are not the addressee, or the
person responsible for delivering this to the addressee(s), you are notified
that reading, copying or distributing this e-mail is prohibited. If you have
received this e-mail in error, please contact the sender immediately.