S %a %d"
Changer Device = /dev/sg3 # already set in the device resource. both
are possibles
}
As you can see, I played a bit with the storage parameters, tried
Hardware End of medium = No, Fast Forward Space File = No (which raises
another error), TWO EOF (btape complains that he
as soon I put a 2nd backup
on them. Last time I rebooted it was for the firware upgrade that I did,
a few weeks ago.
Mailing wrote:
> yvan wrote:
>> Hi the list !
>>
>> I need your help !
>> I'm trying to setup bacula working with our Dell Autochanger TL2000 (24
>>
RR=dev.c:1354 ioctl MTFSF
error on "IBMLTO4" (/dev/nst0). ERR=Input/output error.
Strange that it works for you then ... I issued all the "mt" commands
you wrote. Tapeinfo gives me the samed infos as you have, but it's MTFSF
error or MTEOM ...
Regards
Yvan Broccard
> I als
orgot to mention I'm running Bacula version 2.2.6 on RHEL4 and
> 2.4.3 on RHEL5.2.
>
> HTH,
> Win
>
>
>> Message: 7
>> Date: Mon, 04 May 2009 13:13:45 +0200
>> From: yvan
>> Subject: Re: [Bacula-users] Tape MTEOM error with Dell TL2000 (IBM
>>
or "Random Access" (= no, for tapes) ... maybe
it's that ?
Le 06.05.2009 19:18, Hayden Katzenellenbogen a écrit :
Yvan,
I see that you are running a TL2000 have you run the btape fill test on
your system. If you have did you get any errors?
I seem to be getting the following
quot;No"
Volume Poll Interval = 300 # Poll the drive to seek the status
}
Autochanger {
Name = TL2000
Device = IBMLTO4
Changer Command = "/etc/bacula/scripts/mtx-changer %c %o %S %a %d"
Changer Device = /dev/sg3 # already set in the device resource. bo
en I can
maybe just dump the local filesystem on 2 tapes (i need 1.5Tb for every
full backup, so it means 2x LTO4 800Gb-1.6TB).
For Hayden : the "cap" is a command of the "btape" utility, that shows
every configuration option set in the storage config file for that
device.
, then the autochanger switched to the 2nd one to finish the
job. Happy that at least that is working as intended.
Le 12.05.2009 15:10, Win Htin a écrit :
> Hi Yvan,
>
> If it is of any consolation, it took me one whole month to make Bacula
> work but at the end of the day, it was time
FreeBSD 7.1-RELEASE-p4
Bacula 3.0.0
I had bacula running well for a long time. A couple of weeks ago it stopped
working. The sd and fd are running ok.
This is what I get when I start the director:
bacula# /usr/local/etc/rc.d/bacula-dir start
Starting bacula_dir.
bacula-dir: dird.c:177-0 Debug le
I think that's normal. The state file is only created when bacula-dir exits
normally, and it hasn't done that in a while.
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: April 15, 2009 11:06 AM
To: Yvan Rodrigues; bacula-users
Subject: Re: [Bacula-use
10 matches
Mail list logo