> Spooling can reduce overall throughput because the data is
> sequentially written to disk and then read back.
This is what got me. I thought it was a buffer to ride out variations
in disk read speed (like the mbuffer program) but it's not. The
purpose is to get data off clients as fast as
Thanks, pmset was the missing piece. I put together a pair of shell
one-liners that saves the current setting in Before, and restores it in
After. The real test will be when it runs overnight, but so far it looks
promising.
On Wed, Feb 6, 2019 at 2:57 PM Dimitri Maziuk via Bacula-users <
On 2/6/19 4:14 PM, David Brodbeck wrote:
> I think I'm barking up the wrong tree and the ClientBeforeJob functionality
> just isn't meant for this sort of thing. I gather from earlier conversation
> that it was only working for me in 7.4.x because of a bug.
From a brief look at google it seems
I used "at" on High Sierra, but on Mojave it no longer works.
Disappointing, but not terribly surprising since it's been deprecated for
years. It might be possible to make it work on Mojave if I disabled system
protection, but I'm trying to avoid that if at all possible.
Your disown suggestion
Spooling can reduce overall throughput because the data is sequentially
written to disk and then read back.
To see how fast bacula copied the spool file to tape, which is the critical
thing to avoid shoe shining, look in the log for lines like this:
Despooling elapsed time = ..., Transfer rate =
Hello Steven,
In the next week or two, there will very likely be binary versions for
your OS. When those are available you can use them.
Best regards,
Kern
On 2/6/19 5:39 PM, Steven Hammond wrote:
> We are using Ubuntu 18.04 LTS so the bacula version is like 9.0.X. Is
> there a way to upgrade
If you are using scheduled jobs then you can also vary the pool in the
Schedule directive to match the pool used for the main backups, e.g.
# Use this schedule for the catalog backup.
Schedule {
Name = "FullAlwaysCycle"
Run = Level=Full Pool=MonthlyPool FullPool=MonthlyPool 1st sun at 2:05
Indeed it looks like my 2x 1tb mirror is bottle necking. I looked back at
an older job I ran when I had data spooling off and it saved 930gb at a
rate of 67.0 mb/s and then the same job ran again later with spooling on at
a rate of 46.0 mb/s. Both these rates are much lower than the theoretical
We are using Ubuntu 18.04 LTS so the bacula version is like 9.0.X. Is
there a way to upgrade WITHOUT have to compile it from sources? I.e.,
some PPA available?
Steven Hammond
Cleburne, TX
On 2/6/2019 3:33 AM, Kern Sibbald wrote:
Hello,
We are pleased to announce the release of Bacula
Hi
I write my backups to LTO 7 tape. I have 3 sets of tapes which i rotate
every month. I run one full backup at the start of the month and then
incrementals for the rest of the month.
I've been running these jobs for a few months now and have never seen this
problem.
This month the full
Thanks Martin, I will add the max clients jobs directive. That is a good
question regarding the mirror throughput, I’ll look into testing it. I wonder
if I could spool on a ramdisk (the bacula server has 32gb) since the other
server which is backed up is faster (raidz2 of 8x4tb 7200rpm drives
> On Wed, 6 Feb 2019 00:05:21 -0500, Nate K said:
>
> I've tried to figure this out on my own with searches and going through the
> manual and I need some clarification. I've included the relevant section
> of the bacula-sd.conf file below. I'm confused because I think this should
> work
Hello,
We are pleased to announce the release of Bacula version 9.4.2. It is
already released to Source Forge and bacula.org. Binaries for selected
should be available in the near future.
This is a bug fix release to the prior version (9.4.1) that includes a
number of bug fixes and patches.
13 matches
Mail list logo
