Some thoughts: - Have you reviewed the entire activity log since the time this volume was created (20 October, based on volume history information)? A good starting point would be to query the activity log for all messages containing that volume name. You'll also want to look for any related messages before and after messages containing that volume name.
- The QUERY VOLUME info you mentioned in a prior post shows a last read date of yesterday, about half past noon. Maybe look at the activity log in detail around that time frame to see what was going on. - Have you tried auditing the library? Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 10/25/2006 06:40:46 AM: > Richard Sims wrote: > > Regarding: > > > >> Removable volume 5009L is required for a restore request from session > >> 1444. (SESSION: 1444) > > > > Hello, Skylar - > > > > Whereas a full Query Volume shows a healthy volume, let's now look > > further... > > > > Do 'Query LIBVolume * 5009L'. If that responds with > > ANR2034E QUERY LIBVOLUME: No match found using this criteria. > > it suggests that the volume was checked out of the library. > > AFAIK, I haven't checked the volume out at all, but in any case it's > been in the library since I tried the restore. > > tsm: SHANTI>q libv * 5009L f=d > > Library Name Volume Name Status Owner Last Use Home > Device Cleanings Left Media Type > Element Type > ------------ ----------- ---------- ---------- --------- ------- > ------ -------------- ---------- > EMPIRE 5009L Private Data 4,099 > > > > Also, something that should have immediately caught my eye yesterday: > > that volume name is only five characters long, which is odd: I would > > expect it to be six characters, or 8 if the 2-char cartridge type > > appendage is observed. Research your Activity Log and see how that > > cartridge was introduced to TSM, and what has gone on with it. > > Something's not right there. > > I checked it in through our I/O port. The volume name comes from our bar > code reader, and it matches the text that's on that volume. > > -- > -- Skylar Thompson ([EMAIL PROTECTED]) > -- Genome Sciences Department, System Administrator > -- K324, (206)-685-7354 > -- University of Washington Medical Center