The audit library function needs to have most all the processes quiet. In
addition, if you let it slap the tapes into drives to read the labels, it
may never finish... I have NEVER gotten that little feature to work (3.7.2
or 4.1.4.5). I do audits using the barcode reader as in: audit library
3575lib1 checklabel=barcode. This will read the last scan the library did
of its elements from memory and only mount a tape if the label is damaged.
It will NOT move from slot to slot as one would expect.
George Lesho
System/Storage Admin
AFC Enterprises
Marc Lowers
<Marc.R.Lowers@GS To: [EMAIL PROTECTED]
K.COM> cc: (bcc: George
Lesho/Partners/AFC)
Sent by: "ADSM: Subject: auditing tape libraries again
Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
04/09/02 10:32 AM
Please respond to
"ADSM: Dist Stor
Manager"
Does the size of a TSM database relate to the length in time that an AUDIT
LIBRARY will take to complete?
We have a TSM server running on Solaris software which is around 40GB in
size and have left it running for 3 days and it still failed to complete!
We had to cancel the process.
Any ideas if this is the reason it should take so long?
Marc.
