This, and the idea of a bogus ip address on the lib clients are great
ideas!

Thanks!

Rick





             Paul van Dongen
             <Paul@VANGUARD-IT
             .COM.BR>                                                   To
             Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
             Dist Stor                                                  cc
             Manager"
             <[email protected]                                     Subject
             .EDU>                     RES: audit library  problems


             06/22/2009 01:36
             PM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






Richard,

I think something quick and dirty would be changing the port numbers on
your library manager's dsmserv.opt file. No other client, STAgent or server
would contact this instance, and you could prep a modified dsm.sys/opt to
let you admin client work.

When finished, just return the correct port numbers.
___________________________________________________
Paul Gondim van Dongen
IBM Certified Advanced Deployment Professional
    Tivoli Storage Management Solutions 2006, 2007 & 2008
IBM Certified Deployment Professional - ITWS 8.2
IBM Certified Storage Administrator - ITSM V5.4
IBM Certified Solution Advisor - Tivoli Storage 2008
SNIA Certified Professional
ITIL Foundation Certified
___________________________________________________
VANguard
Value Added Network guardian
+55-81-34198094
http://www.vanguard-it.com.br
________________________________________
De: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] em Nome de Richard
Rhodes [rrhodes AT FIRSTENERGYCORP DOT COM]
Enviado: segunda-feira, 22 de junho de 2009 12:02
Para: ADSM-L AT VM.MARIST DOT EDU
Assunto: audit library  problems

This past weekend we started the process of upgrading our TSM environment
from v5.4.1 to v.5.2.2.  We have 2 dedicated library managers (3584 libs)
and 7
tsm library client instances and a bunch of storage agents.
The first step was to upgrade _one_ of the library managers.

After we upgrade this library manager instance we  hit
APAR IC59453, where drives would drop to a UKNOWN
status and become unavailable.  The library manager would
start working, then quickly degrade till it quit
servicing mounts.  IBM support had us upgrade to
patch v.5.5.2.1 to fix.

When this problem occurred the library managers view
of the library got messed up (ANR8300E) and
required a AUDIT LIBR to clean up.  And there I hit
frustration!  Audit Libr cmd requires that the library be unused - no
processes/sessions have tape mounted.  It also requires
at least one drive be online.  If you issue the cmd before
any drives are online, it's process throws an error
saying there are not online drives.

When this problem occurred and need to do a Audit,
I would change all the
drives to online=no, halt/start the library manager,
bring _one_ drive . . . and INSTANTLY a mount would
occur for a library client instance!! I would then
issue the Audit Libr cmd (which waits for the drive
to become free) and work to get the process/session that
has the mount to end.  This is SO FRUSTRATING.  I had
to do this multiple time is working through this problem.

I asked IBM support if there was any way to tell a
dedicated library manager to STOP SERVICING client
requests, and he said there isn't.

QUESTION:  How can you effectively get a audit libr
cmd to run in a busy library sharing environment?

I came up with these ideas:

1)  Drop all paths for a drive except for the
the library manager itself - giving a dedicated drive
to the library manager.

2)  Change the password on the server-to-server setup.

(wishful thinking invoked)

3)  Get IBm to add a library client library online/offline function.

4)  Get IBM to add a library manager online/offline function for servicing
mount requests.

5)  Get IBM to allow audit libr to run without a online drive.  (WHY does
an Audit need a drive online anyway?  A audit is to the SMC device for the
library proper, not a RMT drive device).



rick

(sorry . .. was venting a little)



-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.