ADSM-L

Re: [ADSM-L] TS3500 count mismatch

2008-11-07 14:09:46
Subject: Re: [ADSM-L] TS3500 count mismatch
From: Sergio Fuentes <sfuentes AT UMD DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 7 Nov 2008 14:08:53 -0500
You can also try the show slots <lib-name> and show library <lib-name> from the
TSM server.  Compare what TSM thinks is in the library with what is really in
the library.  In my experience, if you've updated the library's physical
configuration without a reboot of the TSM Server, the TSM's library inventory
can become inconsistent with the physical library.  To circumvent the TSM
reboot, I end up having to delete drive and library paths and redefine them.

ALMS will screw up the element/phsyical slot numbers, so beware.

Also, try running inventories from both TSM and the library panel.

SF

Thomas Denier wrote:
-----Fred Johanson wrote: -----

The control panel on our TS3500 reports library full with 1408
volumes.  4 are cleaning cartridges, so there should be 1404 volumes
in TSM.  But

Select count(volume_name) from libvolumes

Returns 1381, leaving 23 unaccounted for.  The Web gui shows no
unassigned volumes, so where are the missing volumes?  We asked our
CE if there was anything he knew that could account for this.  He
said no.  We asked if there was any way we could dump the inventory
to EXCEL or something so we could compare it with the libvolumes
output. He said no.

My site has a 3494, but we will have to work with a 3584 or TS3500
at our next disaster recovery test. One of the Web sites I found
while researching 3584 behavior indicates that a Unix command like:

IBMtapeutil -f /dev/IBMchanger0 inventory

will return a human-readable list of volumes with groups of lines
like:

Slot Address 4096
Slot State ..................... Normal
ASC/ASCQ ....................... 0000
Media Present .................. Yes
Robot Access Allowed ........... Yes
Source Element Address ......... 4096
Media Inverted ................. No
Volume Tag ..................... ABA920L1

'IBMtapeutil' is the name of the mainframe Linux version of the
utility. I think it is called 'tapeutil' on some of the other
platforms for which 3584 device drivers are available.

<Prev in Thread] Current Thread [Next in Thread>