Bacula-users
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Bacula-users] unable to use dell tl4000

2009-12-24 01:35:23
Subject: Re: [Bacula-users] unable to use dell tl4000
From: Ismail OZATAY <ismail AT ismailozatay DOT net>
To: Dan Langille <dan AT langille DOT org>
Date: Thu, 24 Dec 2009 08:30:27 +0200 
Dan Langille yazmış:
> Ismail OZATAY wrote:
>>> John Drescher wrote:
>>>> On Tue, Dec 22, 2009 at 9:46 AM, Ismail OZATAY 
>>>> <ismail AT ismailozatay DOT net> wrote:
>>>>> Hello ,
>>>>>
>>>>> I bought a dell tl4000 tape libray with 2 drives. I am trying to 
>>>>> use it
>>>>> and search and applied some example configs but i get some errors. I
>>>>> have put "AutomaticMount=yes" option but it wants me to mount it
>>>>> manually.Here is my configs ;
>>>>>
>>>>> Pool {
>>>>> Name = SenelikPool
>>>>> Pool Type = Backup
>>>>> Recycle = yes
>>>>> AutoPrune = yes
>>>>> Volume Retention = 365d
>>>>> Label Format = Full-
>>>>> }
>>>>>
>>>>> bacula-sd.conf
>>>>>
>>>>> Autochanger {
>>>>> Name = delltl4000
>>>>> Device = Drive-1, Drive-2
>>>>> Changer Command = "/usr/lib64/bacula/mtx-changer %c %o %S %a %d"
>>>>> Changer Device = /dev/sg5
>>>>> }
>>>>>
>>>>> Device {
>>>>> Name = Drive-1
>>>>> Drive Index = 0
>>>>> Media Type = LTO4
>>>>> Archive Device = /dev/st0
>>>>> Changer Device = /dev/sg5
>>>>> AutomaticMount = yes;
>>>>> AlwaysOpen = yes;
>>>>> RemovableMedia = yes;
>>>>> RandomAccess = no;
>>>>> AutoChanger = yes;
>>>>> LabelMedia = yes;
>>>>> # Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
>>>>> Alert Command = "sh -c 'smartctl -H -l error %c'"
>>>>> }
>>>>>
>>>>> Device {
>>>>> Name = Drive-2
>>>>> Drive Index = 1
>>>>> Media Type = LTO4
>>>>> Archive Device = /dev/st1
>>>>> Changer Device = /dev/sg5
>>>>> AutomaticMount = yes;
>>>>> Autochanger = yes;
>>>>> AlwaysOpen = yes;
>>>>> RemovableMedia = yes;
>>>>> RandomAccess = no;
>>>>> LabelMedia = yes;
>>>>> # Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
>>>>> Alert Command = "sh -c 'smartctl -H -l error %c'"
>>>>> }
>>>>>
>>>>> When i run a job i get this error ;
>>>>>
>>>>> 22-Dec 15:22 backup-dir JobId 15: shell command: run BeforeJob 
>>>>> "/usr/lib64/bacula/make_catalog_backup bacula bacula xxx"
>>>>> 22-Dec 15:22 backup-dir JobId 15: Start Backup JobId 15, 
>>>>> Job=BackupCatalog.2009-12-22_15.22.16_42
>>>>> 22-Dec 15:22 backup-dir JobId 15: Using Device "Drive-1"
>>>>> 22-Dec 15:22 backup-sd JobId 15: Invalid slot=0 defined in catalog 
>>>>> for Volume "Full-0001" on "Drive-1" (/dev/st0). Manual load may be 
>>>>> required.
>>>>> 22-Dec 15:22 backup-sd JobId 15: Invalid slot=0 defined in catalog 
>>>>> for Volume "Full-0001" on "Drive-1" (/dev/st0). Manual load may be 
>>>>> required.
>>>>> 22-Dec 15:22 backup-sd JobId 15: 3301 Issuing autochanger "loaded? 
>>>>> drive 0" command.
>>>>> 22-Dec 15:22 backup-sd JobId 15: 3302 Autochanger "loaded? drive 
>>>>> 0", result: nothing loaded.
>>>>> 22-Dec 15:22 backup-sd JobId 15: 3301 Issuing autochanger "loaded? 
>>>>> drive 0" command.
>>>>> 22-Dec 15:22 backup-sd JobId 15: 3302 Autochanger "loaded? drive 
>>>>> 0", result: nothing loaded.
>>>>> 22-Dec 15:22 backup-sd JobId 15: Invalid slot=0 defined in catalog 
>>>>> for Volume "Full-0001" on "Drive-1" (/dev/st0). Manual load may be 
>>>>> required.
>>>>>
>>>>> Here is my device status ;
>>>>>
>>>>> [root@backup bacula]# mtx -f /dev/sg5 status
>>>>> Storage Changer /dev/sg5:2 Drives, 47 Slots ( 3 Import/Export )
>>>>> Data Transfer Element 0:Empty
>>>>> Data Transfer Element 1:Empty
>>>>> Storage Element 1:Full :VolumeTag=000049L4
>>>>> Storage Element 2:Full :VolumeTag=000046L4
>>>>> Storage Element 3:Full :VolumeTag=000042L4
>>>>> Storage Element 4:Full :VolumeTag=000047L4
>>>>> Storage Element 5:Full :VolumeTag=000048L4
>>>>> Storage Element 6:Full :VolumeTag=000041L4
>>>>> Storage Element 7:Full :VolumeTag=000045L4
>>>>> Storage Element 8:Full :VolumeTag=000050L4
>>>>> Storage Element 9:Full :VolumeTag=000029L4
>>>>> Storage Element 10:Full :VolumeTag=000038L4
>>>>> Storage Element 11:Full :VolumeTag=000035L4
>>>>> Storage Element 12:Full :VolumeTag=000032L4
>>>>> Storage Element 13:Full :VolumeTag=000030L4
>>>>> Storage Element 14:Full :VolumeTag=000039L4
>>>>> Storage Element 15:Full :VolumeTag=000036L4
>>>>> Storage Element 16:Full :VolumeTag=000033L4
>>>>> Storage Element 17:Full :VolumeTag=000028L4
>>>>> Storage Element 18:Full :VolumeTag=000040L4
>>>>> Storage Element 19:Full :VolumeTag=000037L4
>>>>> Storage Element 20:Full :VolumeTag=000034L4
>>>>> Storage Element 21:Full :VolumeTag=000005L4
>>>>> Storage Element 22:Full :VolumeTag=000002L4
>>>>> Storage Element 23:Full :VolumeTag=000018L4
>>>>> Storage Element 24:Full :VolumeTag=000015L4
>>>>> Storage Element 25:Full :VolumeTag=000004L4
>>>>> Storage Element 26:Full :VolumeTag=000020L4
>>>>> Storage Element 27:Full :VolumeTag=000017L4
>>>>> Storage Element 28:Full :VolumeTag=000014L4
>>>>> Storage Element 29:Full :VolumeTag=000003L4
>>>>> Storage Element 30:Full :VolumeTag=000019L4
>>>>> Storage Element 31:Full :VolumeTag=000016L4
>>>>> Storage Element 32:Full :VolumeTag=000001L4
>>>>> Storage Element 33:Full :VolumeTag=000027L4
>>>>> Storage Element 34:Full :VolumeTag=000025L4
>>>>> Storage Element 35:Full :VolumeTag=000021L4
>>>>> Storage Element 36:Full :VolumeTag=000008L4
>>>>> Storage Element 37:Full :VolumeTag=000026L4
>>>>> Storage Element 38:Full :VolumeTag=000024L4
>>>>> Storage Element 39:Full :VolumeTag=000010L4
>>>>> Storage Element 40:Full :VolumeTag=000007L4
>>>>> Storage Element 41:Full :VolumeTag=000022L4
>>>>> Storage Element 42:Full :VolumeTag=000023L4
>>>>> Storage Element 43:Full :VolumeTag=000009L4
>>>>> Storage Element 44:Full :VolumeTag=000006L4
>>>>> Storage Element 45 IMPORT/EXPORT:Full :VolumeTag=000013L4
>>>>> Storage Element 46 IMPORT/EXPORT:Full :VolumeTag=000012L4
>>>>> Storage Element 47 IMPORT/EXPORT:Full :VolumeTag=000011L4
>>>>>
>>>>>
>>>>> Any idea ?
>>>>>
>>>> First off do not use st0 if you can use nst0.
>>>>
>>>> Also you probably will need to modify your mtx-changer.sh script. The
>>>> reason is your OS is not waiting for your changer to actually load the
>>>> tape. I can see that from the log. The time between start of load and
>>>> failure was 0 minutes...
>>>>
>>>> Look at the comments on this script and consult the list archives for
>>>> this problem. I know this problem comes up many times a year for
>>>> different changers.
>>>
>>> What John said. Here is how I customized my mtx-changer script:
>>>
>>> http://www.freebsddiary.org/tape-library.php
>>>
>>>
>>>
>>
>
>> Hi Dan,
>>
>> Thank you for your reply. I have just tried mtx-changer script 
>> manually and everthing is working properly. I could load and unload 
>> any slots without any problem. 
>
> What about all the other mtx-changer commands as shown in the above URL?
All command are working.
>
>> Then i add "Maximum Changer Wait = 300 seconds" option in 
>> bacula-sd.conf file. But the problem is still going on :(
>>
>> 23-Dec 17:02 backup-sd JobId 20: Invalid slot=0 defined in catalog 
>> for Volume "Full-0001" on "Drive-1" (/dev/nst0). Manual load may be 
>> required.
>
> That's pretty important. see below.
>
>> 23-Dec 17:02 backup-sd JobId 20: 3301 Issuing autochanger "loaded? 
>> drive 0" command.
>> 23-Dec 17:02 backup-sd JobId 20: 3302 Autochanger "loaded? drive 0", 
>> result: nothing loaded.
>> 23-Dec 17:02 backup-sd JobId 20: 3301 Issuing autochanger "loaded? 
>> drive 0" command.
>> 23-Dec 17:02 backup-sd JobId 20: 3302 Autochanger "loaded? drive 0", 
>> result: nothing loaded.
>> 23-Dec 17:02 backup-sd JobId 20: Please mount Volume "Full-0001" or 
>> label a new one for:
>> Job: BackupCatalog.2009-12-23_16.17.53_03
>> Storage: "Drive-1" (/dev/nst0)
>> Pool: SenelikPool
>> Media type: LTO4
>>
>> How can i fix it?
>>
>> Regards,
>>
>> ismail
>>
>
> Please remember to CC the list. This allows others to help, not just me.
>
> Please reply at the bottom of the email so we can easily read through 
> what has already been said.
>
> Have you run 'update slots'?
Yes here you can see ,

*update slots
The defined Storage resources are:
1: D1
2: D2
Select Storage resource (1-2): 1
Enter autochanger drive[0]:
Connecting to Storage daemon D1 at backup:9103 ...
3306 Issuing autochanger "slots" command.
Device "Drive-1" has 47 slots.
Connecting to Storage daemon D1 at backup:9103 ...
3306 Issuing autochanger "list" command.
Volume "000049L4" not found in catalog. Slot=1 InChanger set to zero.
Volume "000046L4" not found in catalog. Slot=2 InChanger set to zero.
Volume "000042L4" not found in catalog. Slot=3 InChanger set to zero.
Volume "000047L4" not found in catalog. Slot=4 InChanger set to zero.
Volume "000048L4" not found in catalog. Slot=5 InChanger set to zero.
Volume "000041L4" not found in catalog. Slot=6 InChanger set to zero.



------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Bacula-users] unable to use dell tl4000, Dan Langille
Next by Date:  Re: [Bacula-users] unable to use dell tl4000, Ismail OZATAY
Previous by Thread:  Re: [Bacula-users] unable to use dell tl4000, Dan Langille
Next by Thread:  Re: [Bacula-users] unable to use dell tl4000, Dan Langille
Indexes:  [Date] [Thread] [Top] [All Lists]