Hi all,
We find that our bacula catalog database can handle more concurrent backup
jobs than it can verify catalog jobs. We'd therefore like to have a lower
concurrency limit for verify catalog jobs, but I cannot see an obvious way
to do this.
One way would be to run two director/catalog pai
We're on a more recent version of bacula, but we reload our config quite
frequently and have never needed to restart bacula-dir to get it to work.
Best wishes,
Mark
On Wed, 2 Feb 2022, Shaligram Bhagat, Yateen (Nokia - IN/Bangalore) wrote:
[EXTERNAL EMAIL]
Hi all,
In the Bacula 9.4.4 main r
On Fri, 17 Dec 2021, Phil Stracchino wrote:
...
I've been running my Bacula jobs in parallel for literally decades now
and have never seen it result in a duplicate Path or Filename warning.
And they ARE only warnings.
I would not worry about it as long as it is only a warning. You could
manuall
Hi all,
I find the verify job feature of bacula really useful to see what has
changed since the last verifyinit job, but the job output is becoming
difficult to read as it's clustered with lots and lots of messages of the
form:
17-Dec 18:28 foo-dir JobId 67663: Warning: sql_get.c:186 More th
Hi Martin,
Thanks for the reply, glad to know that it's not just me. They're
InitCatalog Verify jobs. Going to SQL feels a bit hairy, as we'd have to
be careful to cascade the delete to at least the File and Log tables.
As prune (unfortunately) only lets you work on a single client at a time,
Hi all,
I use bacula to backup my data, but also find verify jobs to be extremely
useful.
However, after checking my bacula database, I noticed that none of the old
verify jobs have been pruned, which is making the catalog quite big.
Actual backup jobs are happily being automatically pruned.
Hi Josh,
Many thanks for your advice, good points all - I'll continue to play.
Best wishes,
Mark
On Tue, 28 Apr 2020, Josh Fisher wrote:
...
Yes. I believe the client is multi-threaded in that multiple commands can be
issued and they will each be handled in a separately spawned thread. Howeve
p from
the client.
On Mon, Apr 27, 2020 at 9:34 AM Mark Dixon
wrote:
Hi all,
Am I right in thinking that a single bacula job can only back up each file
in its fileset sequentially - there's no multithreading available to back
up multiple files at the same time in order to leverage the clie
Hi all,
Am I right in thinking that a single bacula job can only back up each file
in its fileset sequentially - there's no multithreading available to back
up multiple files at the same time in order to leverage the client CPU?
I'm a relatively long-term user of bacula (thanks!) who has been
