Hello everyone,
Sorry I am a few days late on this, but attached is a script called
"bacula_warn_on_zero-20171116.sh"
It takes one to three command line parameters:
USE:
./bacula_warn_on_zero-20171116.sh jobid [debug] [zero_incremental_ok]
A jobid is required, debug just logs everything to
> On Mon, 13 Nov 2017 08:33:26 -0700, Bill Arlofski said:
>
> On 11/13/2017 03:49 AM, Martin Simmons wrote:
>
> > Why not take this info from the job table, rather than having to parse it
> > from
> > the joblog?
> >
> > __Martin
>
>
> Hi Martin,
>
> I usually try to avoid directly
On 11/13/2017 03:49 AM, Martin Simmons wrote:
> Why not take this info from the job table, rather than having to parse it from
> the joblog?
>
> __Martin
Hi Martin,
I usually try to avoid directly accessing the catalog if possible. In this
case, what I am looking for is so simple to get from
Hello,
>From Bacula point of view a zero files / zero bytes backup size is
perfectly fine unless no errors detected during backup (i.e. permission is
denied) which Bacula should show in the job log.
So, an extreme specific conditions and requirements, should be handled
outside Bacula, as it
Hello Alan,
No, nothing gets written to storage. Yes, there are database entries
written for the job.
Best regards,
Kern
On 11/13/2017 01:04 PM, Alan Brown wrote:
On 11/11/17 17:26, Kern Sibbald wrote:
Yes, that is one of the reasons why I am not very enthusiastic about
it because it
On 11/11/17 17:26, Kern Sibbald wrote:
Yes, that is one of the reasons why I am not very enthusiastic about
it because it will require yet another directive :-(
Kern, please clarify:
If a backup is 0bytes/0files, does anything actually get written to
storage (tape or disk), or is it just a
> On Sun, 12 Nov 2017 10:43:47 -0700, Bill Arlofski said:
>
> The idea:
>
> - Call this script from a RunScript (RunsWhen = after) "Command ="
> - Pass the script the current jobid (%i) and a few other variables:
> - allow_zero_files
> - allow_zero_bytes
> - zero_incremental_ok
>
>
Hi everyone,
Personally I think this is something that should be kept out the core code of
Bacula, but the topic interested me so last night I emailed Jim directly (off
list) and then wrote a script.
I have the script mostly completed which I will release shortly. I am just
working out the
On Saturday 2017-11-11 12:21:22 Phil Stracchino wrote:
> If implemented at all it should be implemented as an option, because
> there are many kinds of possible admin jobs (and even incremental
> backups) for which it is *perfectly normal* to complete with 0 files/0
> bytes backed up.
If
[mailto:k...@sibbald.com]
Sent: Saturday, November 11, 2017 6:42 AM
To: Jim Richardson <j...@securit360.com>; bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Feature Request - job complete status of with
warnings on zero files zero bytes
Hello Jim,
You can submit it as a f
> On Nov 9, 2017, at 3:35 PM, Jim Richardson wrote:
>
>
> Any chance I can get a feature request in? I would like to have all jobs
> that complete with zero files and / or zero bytes to complete with Backup OK
> – with warnings. Currently these jobs complete with Backup
Yes, that is one of the reasons why I am not very enthusiastic about it
because it will require yet another directive :-(
On 11/11/2017 06:21 PM, Phil Stracchino wrote:
On 11/11/17 07:41, Kern Sibbald wrote:
Hello Jim,
You can submit it as a feature request, but I am not really inclined to
On 11/11/17 07:41, Kern Sibbald wrote:
> Hello Jim,
>
> You can submit it as a feature request, but I am not really inclined to
> implement it, because it is a very special case, and it is very easy for
> anyone to look at the number of files backed up that is produced in the
> job report.
>
>
Hello Jim,
You can submit it as a feature request, but I am not really
inclined to implement it, because it is a very special case, and
it is very easy for anyone to look at the number of files backed
up that is produced in the job report.
Best regards,
14 matches
Mail list logo