I would do the audit first. Otherwise you may checkout a volume TSM
still thinks is checked in.
The Audit is the simplest and quickest way to verify inventory (if you
use the "checklabel=barcode" option)
See Ya'
Howard
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Bob Levad (641-585-6770)
> Sent: Thursday, September 04, 2008 8:28 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Incorrect volume being mounted for reclamation
>
> checkout libv ltolib2 100562 checklabel=no remove=bulk
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Timothy Hughes
> Sent: Thursday, September 04, 2008 7:37 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Incorrect volume being mounted for reclamation
>
> Thanks Howard and Kelly!.
>
> Before I try the Audit Library is there any other option that I could
> try?
> Are there any command (s) to specifically check the label of volume
> 100562 and if it is incorrect then correct that tape with a command?
>
> Thanks again I appreciate your responses!
>
> Tim
>
>
> Howard Coles wrote:
>
> >Thanks Kelly,
> >Not sure about anyone else's Outlook client but mine thoroughly hosed
> >up those three commands to look like:
> >
> > "audit library libname checklabel=barcode checkin libvol libname
> > search=yes checklabel=barcode status=scratch checkin libvol libname
> > search=yes checklabel=barcode status=private"
> >
> >So here they are spread out:
> >
> >audit library libname checklabel=barcode
> >
> >checkin libvol libname search=yes checklabel=barcode status=scratch
> >
> >checkin libvol libname search=yes checklabel=barcode status=private
> >
> >See Ya'
> >Howard
> >
> >
> >
> >
> >>-----Original Message-----
> >>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf
> >>Of Kelly Lipp
> >>Sent: Wednesday, September 03, 2008 4:00 PM
> >>To: ADSM-L AT VM.MARIST DOT EDU
> >>Subject: Re: [ADSM-L] Incorrect volume being mounted for reclamation
> >>
> >>Howard is right on. I'd add a couple more commands to his audit to
> >>"synchronize" the library completely:
> >>
> >>Tsm> audit library libname checklabel=barcode checkin libvol libname
> >>Tsm> search=yes checklabel=barcode
> >>status=scratch
> >>Tsm> checkin libvol libname search=yes checklabel=barcode
> >>status=private
> >>
> >>These three command will ensure that your library inventory is
> >>
> >>
> >accurate
> >
> >
> >>and that all tapes in the library are checked in properly. The
audit
> >>library command will check tapes out that are not found. For
> >>
> >>
> >instance,
> >
> >
> >>if TSM thinks that tape 100087 is in the library, but the audit
> >>determines that it isn't, it will be removed from the TSM library
> >>inventory. However, if the audit finds tape 100088 that TSM doesn't
> >>think is in the library, it won't automatically check it in. The
two
> >>checkin libvol commands fix that up as well. Note the order: you
> want
> >>to do the scratch tapes first.
> >>
> >>Thanks,
> >>
> >>Kelly Lipp
> >>CTO
> >>STORServer, Inc.
> >>485-B Elkton Drive
> >>Colorado Springs, CO 80907
> >>719-266-8777
> >>www.storserver.com
> >>
> >>
> >>-----Original Message-----
> >>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf
> >>Of Howard Coles
> >>Sent: Wednesday, September 03, 2008 2:54 PM
> >>To: ADSM-L AT VM.MARIST DOT EDU
> >>Subject: Re: [ADSM-L] Incorrect volume being mounted for
reclaimation
> >>
> >>Stop all processes, unmount all tapes and audit the library.
> >>
> >>It looks like TSM thinks tape 100562 is in the slot currently
> occupied
> >>by 100617 instead.
> >>
> >>Either the paths are wrong for the drives, (which I doubt) or the
> >>library's inventory is a little off.
> >>
> >>To verify, do a q libv, determine which slot TSM "thinks" the tape
is
> >>in, and then open up your library and see if they match. You may
> have
> >>to actually take the tape out, and then back in again.
> >>
> >>I would try the audit first, then check TSM's list-o-tapes. IF the
> >>tape your needing doesn't show up there may be other problems. Such
> >>as
> >>
> >>
> >tape
> >
> >
> >>stuck in picker, not in library at all (mistakenly sent offsite),
> etc.
> >>
> >>See Ya'
> >>Howard
> >>
> >>
> >>
> >>
> >>>-----Original Message-----
> >>>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> >>>
> >>>
> >Behalf
> >
> >
> >>>Of Timothy Hughes
> >>>Sent: Wednesday, September 03, 2008 3:48 PM
> >>>To: ADSM-L AT VM.MARIST DOT EDU
> >>>Subject: [ADSM-L] Incorrect volume being mounted for reclaimation
> >>>
> >>>Hello all,
> >>>
> >>>I'm reaching at for any help on this.
> >>>
> >>><>We have a tape that needs to be reclaimed but it keeps being set
> >>>
> >>>
> >to
> >
> >
> >>>"unavailable" during reclamation.
> >>>
> >>>
> >>>When I update the tape by doing the following using the GUI
> >>>
> >>>ANR2017I Administrator xxxxx issued command: UPDATE
> >>>
> >>> VOLUME 100562 ACCESS=READWRITE
> >>>WHERESTGPOOL=LTOPOOL
> >>>
> >>> WHEREDEVCLASS=LTOCLASS (SESSION: 138535)
> >>>
> >>><>
> >>>
> >>> It changes back to available, however as soon as reclamation calls
> >>>
> >>>
> >>for
> >>
> >>
> >>>the tape it changes back to "unavailable" The TSM Server log with
> >>>messages are below can anyone give me suggestions/help on the best
> >>>
> >>>
> >>way
> >>
> >>
> >>>to correct the issue?
> >>>
> >>>Thanks for any help in advance!
> >>>
> >>>
> >>>ANR2017I Administrator xxxxx issued command: UPDATE
> >>>
> >>> VOLUME 100562 ACCESS=READWRITE
> >>>WHERESTGPOOL=LTOPOOL
> >>>
> >>> WHEREDEVCLASS=LTOCLASS (SESSION: 138535)
> >>>
> >>>09/03/08 07:37:40 ANR2207I Volume 100562 updated. (SESSION:
> >>>
> >>>
> >>138535)
> >>
> >>
> >>>09/03/08 09:00:00 ANR1044I Removable volume 100562 is required
> >>>
> >>>
> >>for
> >>
> >>
> >>>space
> >>>
> >>> reclamation. (PROCESS: 946)
> >>>
> >>>09/03/08 09:00:36 ANR8356E Incorrect volume 100617 was mounted
> >>>instead of
> >>>
> >>> volume 100562 in library LTO_LIB. (PROCESS:
> >>>
> >>>
> >>947)
> >>
> >>
> >>>09/03/08 09:01:01 ANR8381E LTO volume 100562 could not be
> >>>
> >>>
> >mounted
> >
> >
> >>>in drive
> >>>
> >>> RMT3 (/dev/rmt3). (PROCESS: 947)
> >>>
> >>>09/03/08 09:01:01 ANR1402W Mount request denied for volume
> >>>
> >>>
> >100562
> >
> >
> >>-
> >>
> >>
> >>>volume
> >>>
> >>> unavailable. (PROCESS: 947)
> >>>
> >>>09/03/08 09:01:01 ANR1410W Access mode for volume 100562 now
set
> >>>
> >>>
> >>to
> >>
> >>
> >>> "unavailable". (PROCESS: 947)
> >>>
> >>>09/03/08 09:25:50 ANR1420W Read access denied for volume 100562
> >>>
> >>>
> >-
> >
> >
> >>>volume
> >>>
> >>> access mode = "unavailable". (PROCESS: 946)
> >>>
> >>><> 09/03/08 13:00:38 ANR2017I Administrator XXXXX issued
> >>>command: UPDATE
> >>>
> >>> VOLUME 100562 ACCESS=READWRITE
> >>>WHERESTGPOOL=LTOPOOL
> >>>
> >>> WHEREDEVCLASS=LTOCLASS (SESSION: 143639)
> >>>
> >>>09/03/08 13:00:38 ANR2207I Volume 100562 updated. (SESSION:
> >>>
> >>>
> >>143639)
> >>
> >>
> >>>09/03/08 13:42:54 ANR1044I Removable volume 100562 is required
> >>>
> >>>
> >>for
> >>
> >>
> >>>space
> >>>
> >>> reclamation. (PROCESS: 961)
> >>>
> >>>09/03/08 14:08:30 ANR8356E Incorrect volume 100617 was mounted
> >>>instead of
> >>>
> >>> volume 100562 in library LTO_LIB. (PROCESS:
> >>>
> >>>
> >>961)
> >>
> >>
> >>>09/03/08 14:08:55 ANR8381E LTO volume 100562 could not be
> >>>
> >>>
> >mounted
> >
> >
> >>>in drive
> >>>
> >>> RMT4 (/dev/rmt10). (PROCESS: 961)
> >>>
> >>> reclamation. (PROCESS: 965)
> >>>
> >>>09/03/08 14:10:12 ANR1420W Read access denied for volume 100617
> >>>
> >>>
> >-
> >
> >
> >>>volume
> >>>
> >>> access mode = "unavailable". (PROCESS: 965)
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>09/03/08 13:42:54 ANR1044I Removable volume 100617 is required
> >>>
> >>>
> >>for
> >>
> >>
> >>>space
> >>>
> >>> reclamation. (PROCESS: 962)
> >>>
> >>>09/03/08 13:42:54 ANR8312E Volume 100617 could not be located
in
> >>>library
> >>>
> >>> LTO_LIB. (PROCESS: 962)
> >>>
> >>>09/03/08 13:42:54 ANR8381E LTO volume 100617 could not be
> >>>
> >>>
> >mounted
> >
> >
> >>>in drive
> >>>
> >>> RMT5 (/dev/rmt4). (PROCESS: 962)
> >>>
> >>>09/03/08 13:42:59 ANR1402W Mount request denied for volume
> >>>
> >>>
> >100617
> >
> >
> >>-
> >>
> >>
> >>>volume
> >>>
> >>> unavailable. (PROCESS: 962)
> >>>
> >>>09/03/08 13:42:59 ANR1410W Access mode for volume 100617 now
set
> >>>
> >>>
> >>to
> >>
> >>
> >>> "unavailable". (PROCESS: 962)
> >>>
> >
> >
> >
>
> 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.
|
