Veritas-bu

[Veritas-bu] Loading tapes while a backup is running

2002-10-16 16:14:40
Subject: [Veritas-bu] Loading tapes while a backup is running
From: scott.kendall AT abbott DOT com (scott.kendall AT abbott DOT com)
Date: Wed, 16 Oct 2002 15:14:40 -0500
I'm not familiar with the ldrbt script, but I have never seen this with using
just the vmupdate command.  vmupdate does a great job of injecting the tapes
(-empty_ie or -empty_map in 4.5) and doing an inventory all with one command,
and will even use the barcode rules if told to do so (-use_barcode_rules).

you might want to take a look at this command and if it meets your needs, it
might be a way around the problems this other script is giving you.


- Scott



                                                                                
                                                   
                    "jerome bauwens"                                            
                                                   
                    <jerome.bauwens AT steria DOT com>          To:     
<veritas-bu AT mailman.eng.auburn DOT edu>                               
                    Sent by:                             cc:                    
                                                   
                    veritas-bu-admin AT mailman DOT eng.        Subject:     
[Veritas-bu] Loading tapes while a backup is running         
                    auburn.edu                                                  
                                                   
                                                                                
                                                   
                                                                                
                                                   
                    10/16/2002 10:31 AM                                         
                                                   
                                                                                
                                                   
                                                                                
                                                   




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.











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