The only way to do this would be to write some logic in to your script that you
are using for the inport.
I would probably use
echo "s s" | tlxtest -r <robot>
And grep for the presence of a tape in the slot. I don't have a tld robot here
to test with, but I do believe that even when you do an s s within tldtest it
tells you that there is BARCODE blah there and where that physical tape is
there or not {YES|NO}.
Actually...wait...what ldrbt script?
If you load tapes in the mail port and do a
vmupdate -empty_ie -rn X -rt $TYPE
then it will properly move the tapes to any available slot and update the
database appropriately.
Right?
I think that's right anyway...
David
Quoting jerome bauwens <jerome.bauwens AT steria DOT com>:
> Hi,
>
> I have NB 3.4 with a solaris master and a L700 library. I'm getting a strange
> issue whenever I insert some tapes in the library while a job is running. If
> one of the new tape has been put in the slot where the media being written
> comes from, then NetBackup is enable to unload the tape when the backup is
> done. Is there a way to "lock" the slot where a tape being used come from so
> that the tapes I insert won't use that slot ? I'm using the ldrbt script to
> load the tapes which is doing an inventory when it's done. Looking at the
> "loading log" it appears as if the tape being used (ML0138) has been assigned
> to the standalone residence (which is not what I want either) but it got
> stuck in the drive.
>
> Here is the "loading log":
> Finding tapes in inport... 20 tapes
>
> Finding free slots in robot... 106 free slots
>
> Not including tapes in use - slots 999999
>
> Moving tape MR0523 from inport slot 1 to robot slot 30... done
>
>
> .....
>
> Moving tape ML0271 from inport slot 20 to robot slot 271... done
>
> Tape moves done - auto-updating the volume manager database
>
> Generating list of recommended changes ...
>
> Proposed Change(s) to Update the Volume Configuration
>
> =====================================================
>
> Logically move media ID ML0138 (barcode ML0138) from slot 30 to standalone
> residence.
>
> Logically move media ID ML0280 (barcode ML0280) from standalone to slot 71.
>
>
> ...
>
> Logically move media ID MR0523 (barcode MR0523) from standalone to slot 30.
>
> Updating volume configuration ...
>
> Processing existing media removed from or moved within the robotic library
> by
>
> logically moving media to standalone residence as follows...
>
> Media ID Slot
>
> ======== ====
>
> ML0138 30
>
> Processing existing media added to or moved within the robotic library by
>
> logically moving media as follows...
>
> Media ID Slot
>
> ======== ====
>
> ML0280 71
>
>
> ...
>
> Volume configuration successfully updated.
>
> Here is /var/adm/messages:
>
> Oct 15 15:27:50 zeus ltid[2570]: [ID 560357 daemon.notice] LTID - Sent
> ROBOTIC request, Type=3, Param2=0
>
> Oct 15 15:27:50 zeus tldd[2765]: [ID 342691 daemon.notice] TLD(0)
> DismountTape ML0138 from drive 1
>
> Oct 15 15:28:03 zeus tldcd[2777]: [ID 460425 daemon.notice] Processing
> UNMOUNT, TLD(0) drive 1, slot 30, barcode ML0138 , vsn ML0138
>
> Oct 15 15:28:03 zeus tldcd[11460]: [ID 326160 daemon.notice] TLD(0)
>
> opening robotic path /dev/sg/c3t6l0
>
> Oct 15 15:28:04 zeus tldcd[11460]: [ID 822767 daemon.error] TLD(0) cannot
> dismount drive 1, slot 30 already is full
>
> Oct 15 15:28:04 zeus tldcd[11460]: [ID 559680 daemon.notice] TLD(0)
> closing/unlocking robotic path
>
> Oct 15 15:28:04 zeus tldd[2765]: [ID 706447 daemon.notice] DecodeDismount():
> TLD(0) drive 1, Actual status: Robotic dismountfailure
>
> Oct 15 15:28:04 zeus tldd[2765]: [ID 923197 daemon.error] TLD(0) drive 1
> (device 0) is being DOWNED, status: Robotic dismount failure
>
> Oct 15 15:28:04 zeus tldd[2765]: [ID 229259 daemon.error] Check integrity of
> the drive, drive path, and media
>
> Oct 15 15:30:03 zeus ltid[2570]: [ID 560357 daemon.notice] LTID - Sent
> ROBOTIC request, Type=3, Param2=0
>
> Oct 15 15:30:03 zeus ltid[2570]: [ID 585292 daemon.notice] NOTE - Dismount
> due to RESET DEVICE
>
> Oct 15 15:30:03 zeus tldd[2765]: [ID 686714 daemon.notice] TLD(0)
> DismountTape from drive 1
>
> Oct 15 15:30:58 zeus tldcd[2777]: [ID 247841 daemon.notice] Processing
> UNMOUNT, TLD(0) drive 1, slot -1, barcode --------, vsn ******
>
> Oct 15 15:30:58 zeus tldcd[12285]: [ID 326160 daemon.notice] TLD(0) opening
> robotic path /dev/sg/c3t6l0
>
> Oct 15 15:30:59 zeus tldcd[12285]: [ID 822767 daemon.error] TLD(0) cannot
> dismount drive 1, slot 30 already is full
>
> Oct 15 15:30:59 zeus tldcd[12285]: [ID 559680 daemon.notice] TLD(0)
> closing/unlocking robotic path
>
> Oct 15 15:30:59 zeus tldd[2765]: [ID 706447 daemon.notice] DecodeDismount():
> TLD(0) drive 1, Actual status: Robotic dismountfailure
>
> Oct 15 15:30:59 zeus tldd[2765]: [ID 923197 daemon.error] TLD(0) drive 1
> (device 0) is being DOWNED, status: Robotic dismount failure
>
> Oct 15 15:30:59 zeus tldd[2765]: [ID 229259 daemon.error] Check integrity of
> the drive, drive path, and media
>
> Oct 15 15:34:29 zeus ltid[2570]: [ID 527589 daemon.notice] LTID - Sent
> ROBOTIC request, Type=1, Param2=0
>
> Oct 15 15:34:29 zeus tldd[2765]: [ID 654615 daemon.notice] TLD(0) MountTape
> ML0000 on drive 6, from slot 306
>
> Any advice will be welcomed
>
> Jerome Bauwens.
>
>
>
>
|
