On 10/01/17 03:17, Kern Sibbald wrote:
> ...The one thing that does not make sense
> to me, however, is your tapeinfo did not show any Tape Alerts ...
Thanks for being thorough, Kern.
Our bacula-sd.conf's Device stanza for the autoloader did not have an
Alert Command directive. Now fixed.
--
On 09/01/17 22:39, Alan Brown wrote:
> On 09/01/17 14:47, Charles wrote:
>> ... Bacula shows the tape wth status Error (simply
>> reflecting what the autoloader has told it?).
>
> Are you sure it was the loader which had the critical error?
No
> Most "critical errors" of this kind are bacula atte
On 01/09/2017 01:55 PM, Timo Neuvonen wrote:
> I'm still wondering if this really is the
> simplest way of implementing the file storage?
>
> What would I lose if I simply had only one of the two device resources, no
> autochanger resource at all, and the jobs would refer directly to the device
>
Hello Charles,
If you do not know who Alan Brown is, I can say that he is at least 10
times more knowledgeable about the use of tape drives with Bacula than I
am, so I defer to his analysis. The one thing that does not make sense
to me, however, is your tapeinfo did not show any Tape Alerts, w
Hello,
The Autochanger definition for the SD you show below is a Virtual
Autochanger. It is anything but a dummy, though that is arguable.
If you want more information about it, there are two whitepapers
on the bacula.org web site that talk about th
On Monday 2017-01-09 09:56:54 Lloyd Brown wrote:
> On 01/09/2017 09:46 AM, Josip Deanovic wrote:
> > Hi!
> > Maybe you could make use of Verify jobs in case you are restoring the
> > most recent backup and you have fairly recent Verification job run.
>
> I considered a Verify job. I haven't done
Pasted below is a piece of the default bacula-sd.conf
My installation is from epel-bacula repo for CentOS 7, but exactly the same
conf example can be found from the latest Bacula source tarball.
Could someone explain why a file storage device is definend as an "dummy"
autochanger, and the two fil
On 09/01/17 14:47, Charles wrote:
>
> Hello bacula-users :-)
>
> Are any tools available to mend Bacula after almost certainly spurious
> errors reported by a tape autoloader?
>
> Within a few minutes of Bacula starting to use an autoloader which had
> been subject to an abrupt power outage, the au
On 01/09/2017 09:46 AM, Josip Deanovic wrote:
> Hi!
> Maybe you could make use of Verify jobs in case you are restoring the
> most recent backup and you have fairly recent Verification job run.
I considered a Verify job. I haven't done them much, but the trouble is
that my boss wants a full end-t
On Monday 2017-01-09 09:37:48 Lloyd Brown wrote:
> I hope this isn't something obvious I've missed, but ... well ... I
> missed it, at least so far. I'll keep looking but my google-fu seems to
> be missing something.
>
> Is there an easy way to run an external script (eg. a "RunAfterJob" or
> sim
I hope this isn't something obvious I've missed, but ... well ... I
missed it, at least so far. I'll keep looking but my google-fu seems to
be missing something.
Is there an easy way to run an external script (eg. a "RunAfterJob" or
similar) associated with a *restore* job? I'm trying to build a
On 09/01/17 13:45, Kern Sibbald wrote:
Hello,
The status Bacula received was -1, which means that the tape drive
reported a hardware end of tape (i.e. an end of tape marker was seen.
This can happen for the following reasons:
1. You reached the hardware end of tape marker at 150GB, but the
On 27/12/16 23:30, bacula-users-requ...@lists.sourceforge.net wrote:
> --
>
> Message: 8
> Date: Fri, 23 Dec 2016 10:13:58 +0530
> From: Charles
> Subject: [Bacula-users] How to fix Bacula after tape autoloader
> dysfunction?
> To: bacula-users@lists.sourceforge.n
Hi,
you can run bacula director in debug mode using:
"*path/to/your/bacula-dir* -f -c /*path/to/bacula-dir.conf* -d 400"
(400 is the maximal debug output, so expect quite a lot written to stdout)
Best regards,
Daniel
On 09.01.17 14:53, webmas...@peter-speer.de wrote:
Hi there.
I am on C
On Monday 2017-01-09 14:53:21 webmas...@peter-speer.de wrote:
> Hi there.
>
> I am on CentOS 7 with Bacula 7.4.4 buld from source.
> I wonder, if there is a file where I can see why i.e. bacula-dir is not
> coming up i.e. if I have a mistake in my bacula-dir.conf. Where is
> bacula logging those m
Hi there.I am on CentOS 7 with Bacula 7.4.4 buld from source.I wonder, if there is a file where I can see why i.e. bacula-dir is not coming up i.e. if I have a mistake in my bacula-dir.conf.Where is bacula logging those messages? I am not able to see anything in /var/log/messages or /opt/bacula/l
Hello,
The status Bacula received was -1, which means that the tape drive
reported a hardware end of tape (i.e. an end of tape marker was
seen. This can happen for the following reasons:
1. You reached the hardware end of tape marker at 150GB, but t
2017-01-04 12:57 GMT-03:00 Phil Stracchino :
> On 01/04/17 10:52, Martin Simmons wrote:
> >> On Fri, 30 Dec 2016 18:37:28 -0300, Sergio Belkin said:
> >>
> >> I have 4 disks:
> >>
> >> I'd want to plug every disk every monday.
> >>
> >> So, Mondays run Full Backups and the rest of the days
> >
18 matches
Mail list logo