Kern - thanks. Perhaps foolishly I didn't try any "one file test" jobs;
my comfort level with installing bacula on this distro with these tape
drives has become second-nature to the point that I didn't feel the need
(so I got bit), and of course with the weekend, trying to get it running
to
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
Hello Ted,
This is probably perfectly normal if you have not yet finished any
jobs. By default the Filename entries are put in the catalog at the end
of each Job. The one entry you did find is a "blank" filename which is
used when putting Directory entries into the catalog (i.e. for a
Greets - I have a new installation of Bacula on Debian Jessie
(5.2.6+dfsg-9.3) with a postgres backend. This is not my first bacula
installation (I have 5 other separate instances running on different
tape units, some single TL2000, some library changers - all happy) --
except for this new one
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
