On Friday 17 February 2006 10:18, [EMAIL PROTECTED] wrote:
> Arno Lehmann schreef:
> > Hello,
> >
> > On 2/15/2006 10:47 AM, [EMAIL PROTECTED] wrote:
> >> Hi,
> >>
> >> I'm new to bacula.
> >>
> >> I looked in the manual and the mailing list but didn't find a solution.
> >>
> >> I'm using bacula 1.36.3 on a debian sarge system.  Connected to the
> >> system is a exabyte 221L with one IBM LTO-1 drive.
> >>
> >> I got jobs scheduled which run fine.  When there is no tape in the
> >> drive it loads the tape.  But sometimes when a job starts it keeps
> >> waiting for a tape in the drive (there isn't one) and fails after a
> >> while saying:
> >> <message>
> >> BackupCatalog.2006-02-15_01.10.00 Fatal error: device.c:317 Unable to
> >> open device /dev/nst0. ERR=dev.c:289 stored: unable to open device
> >> /dev/nst0: ERR=Input/output error
> >>
> >> 15-Feb 03:07 fs2-fd: BackupCatalog.2006-02-15_01.10.00 Fatal error:
> >> job.c:1665 Bad response to Append Data command. Wanted 3000 OK data
> >> , got 3903 Error append data
> >> </message>
> >>
> >> It didn't issue the 'mtx-changer loaded' and 'mtx-changer loaded'
> >> commands, which, i think, it should have.
> >>
> >> Anyone an idea why this is done?
> >
> > That might be because you're runing a linux kernel 2.6. The tape access
> > there ahs changed quite a bit compared to 2.4 and standard unix
> > behaviour which can result in the SD not being able to access tape
> > drives without a tape loaded - just what you observe.
> >
> > If that's the reason for your problem an upgrade to 1.38.5 might be your
> > best solution. I don't know if there are debian packages available, but
> > apart from that, an upgrade will improve some functionality and result
> > in better stability in many cases.
> >
> > Arno
>
> Hi,
>
> I compiled 1.38.5 and installed it in a directory.  I changed
> bacula-sd.conf so that it used the new tapechanger resource.  I still
> have the same problem.  I must be doing something wrong, but don't know
> what.  Do you?
>
> The first job starts and when finished it unloads the tape (with
> runafterjob command)-->backup OK
> The next job starts loads the same tape and when fininshed it unloads
> the tape-->backup OK
> The next job starts loads the same tape and when fininshed it unloads
> the tape-->backup OK
> The Catalog job starts and outputs the following messages.  This time i
> got to mount the tape myself (tape VR0801L1 is in changer slot 8).
> After manually loading the tape (with mtx) and mounting the device, the
> backup is continuing and is OK.  The only problem is 'why do i have to
> load and mount the tape'.
>
> <messages for catalog job>
> 17-feb 09:30 fs2-sd: 3301 Issuing autochanger "loaded drive 0" command.
> 17-feb 09:30 fs2-sd: 3302 Autochanger "loaded drive 0", result: nothing
> loaded.
> 17-feb 09:30 fs2-sd: 3301 Issuing autochanger "loaded drive 0" command.
> 17-feb 09:30 fs2-sd: 3302 Autochanger "loaded drive 0", result: nothing
> loaded.
> 17-feb 09:30 fs2-sd: Please mount Volume "VR0801L1" on Storage Device
> "EXABYTE" (/dev/nst0) for Job BackupCatalog.2006-02-17_01.10.00
> 17-feb 09:30 fs2-sd: Please mount Volume "VR0801L1" on Storage Device
> "EXABYTE" (/dev/nst0) for Job BackupCatalog.2006-02-17_01.10.00
> </messages for catalog job>
>
> <bacula-sd.conf>
> # EXABYTE 221L tape changer with IBM LTO-1 drive
> Autochanger {
>    Name = "EXABYTE-CHANGER"
>    Device = "EXABYTE"
>    Changer Device = /dev/sg2
>    Changer Command = "/etc/bacula/scripts/mtx-changer %c %o %S %a %d"
> ##  Changer Command = "/tmp/mtx-changer %c %o %S %a %d"
> }
>
> Device {
>    Name = EXABYTE
>    Drive Index = 0
>    Media Type = LTO-1
>    Archive Device = /dev/nst0
> #  Archive Device = /dev/nrst0
> ##  AutomaticMount = yes;               # when device opened, read it
>    AutomaticMount = no;               # when device opened, read it
> ##  AlwaysOpen = yes;
>    AlwaysOpen = no;
>    RemovableMedia = yes;
>    RandomAccess = no;
>    AutoChanger = yes
>    Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
>    Maximum Changer Wait = 120 seconds
> }
> </bacula-sd.conf>
>
> <bacula-dir.conf>
> JobDefs {
>    Name = "CatalogJob"
>    Type = Backup
>    Level = Incremental
>    Client = fs2-fd
>    FileSet = "Full-Set-fs2"
>    Schedule = "WeeklyCycle"
>    Storage = EXABYTE
>    Messages = Standard
>    Pool = CatalogPool
>    Priority = 11
> }
> # Backup the catalog database (after the nightly save)
> Job {
>    Name = "BackupCatalog"
>    JobDefs = "CatalogJob"
>    Level = Full
>    FileSet="Catalog"
>    Schedule = "WeeklyCycleAfterBackup"
>    # This creates an ASCII copy of the catalog
>    RunBeforeJob = "/home/marc/bacula/etc/scripts/make_catalog_backup
> bacula2 bacula"
>    # This deletes the copy of the catalog
> ##  RunAfterJob  = "/home/marc/bacula/etc/scripts/delete_catalog_backup
> ; /home/marc/bacula/etc/scripts/mtx-changer /dev/sg2 unload -1 /dev/nst0 0"
>    RunAfterJob  = "/home/marc/bacula/etc/scripts/end_catalog_job"
>    Write Bootstrap = "/var/lib/bacula/BackupCatalog.bsr"
>    Priority = 11                   # run after main backup
> }
> </bacula-dir.conf>
>
> <end_catalog_job>
> #!/bin/sh
> /home/marc/bacula/etc/scripts/delete_catalog_backup
> /home/marc/bacula/etc/scripts/mtx-changer /dev/sg2 unload -1 /dev/nst0 0
> </end_catalog_job>

I don't know exactly why you have the mtx-changer unload command in your 
end_catalog_job script, but it will totally confuse the Storage daemon.  Once 
Bacula is using an autochanger, you cannot manually manipulate it unless you 
"unmount" it using bconsole or stop your Storage daemon.




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to