This just happens, for a variety of reasons, ranging from human error to the normal operation of Murphy's Law.
Periodically (about once per week) I run an audit program (written in SPSS) that compares the lists of libvols, volumes, and database backup (only!) entries in volhist, just to make sure everything is OK. I don't want orphan tapes, but I realy don't want anything to be claimed twice. I investigate anything it flags. When I find what I can confirm to be an orphan tape, I usually just UPDATE LIBVOL lib vol STATUS=SCRATCH. It is not necessary to check it out and back in, unless of course the problem is that it wasn't labeled correctly in the first place. This audit procedure got a lot more complex, and also a lot more vital, after we went to a Library Manager environment. Now there are a lot more ways something could go wrong. Everybody must do a periodic audit like the one Gary Lee just did. Make sure you get it right. Cheers! Roger Deschner University of Illinois at Chicago [email protected] ================ Help stamp out and abolish redundancy. ================ On Fri, 5 Oct 2012, Bob Levad wrote: >The most obvious reasons would be a tape operator running a check-in script >instead of a label script or checking in with a status=private instead of >status=scratch. > >TSM will not initialized a tape with data it knows about, so checking them out >and labeling or checking back in as scratch (whichever is appropriate) will >work. If you check everything out with remove=no, and checkin scratch first >and then private, you should get back all the volumes that have been >initialized. If you are still missing some, they probably haven't been >initialized. > >As for the volhist, a volume isn't listed there until it is actually used for >data of some kind. > >Bob. > >-----Original Message----- >From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Lee, >Gary >Sent: Friday, October 05, 2012 1:36 PM >To: [email protected] >Subject: [ADSM-L] unaccounted for volumes > >Tsm server 6.2.2 running on RHEL v6 with a 3494 library and 8 ts1120 drives. > >Was doing some checking on tape inventory and usage for one of our tsm servers. > >A > >Select count(*) from libvolumes > >Shows 298 volumes in the library. > >Checking volhistory for database backup volumes shows 3 tapes in that capacity. > >Check of pending volumes shows 1 > >And summing up all tape pool volumes gives 118. > >A >Select count(*) from libvolumes where status='Private' > >Shows 160 >And >Select for scratch volumes gives 137. > >The upshot is that I have around 40 volumes in the libvolumes table listed as >private, but not accounted for in the volumes or volhistory? >Audit library ields no errors. > >Can I just check these out and re check them in as scratch? > >What would account for this. > >p.s. > >I have the volhist file from the moment the server was placed online. The >lost volumes do not appear there anywhere. > >Thanks for any help. > > >Gary Lee >Senior System Programmer >Ball State University >phone: 765-285-1310 > > >This electronic transmission and any documents accompanying this electronic >transmission contain confidential information belonging to the sender. This >information may be legally privileged. The information is intended only for >the use of the individual or entity named above. If you are not the intended >recipient, you are hereby notified that any disclosure, copying, distribution, >or the taking of any action in reliance on or regarding the contents of this >electronically transmitted information is strictly prohibited. >
