FWIW: There is virtually no benefit in network compression for link
speeds of 1Gb/s or faster.
It's a net benefit on WAN links or on 100Mb/s networks, but I found it
had a tendency to slow things down (and use a lot of CPU!) on 1Gb/s
networks vs letting the networking traffic run
Message transféré
Sujet : Re: [Bacula-users] Bandwidth in Bacula (slow rate)
Date : Wed, 22 Mar 2017 14:57:11 +0100
De :Norbert Gomes
Pour : Josh Fisher
Hi
I've been confronted at the same situation, and that
> On Wed, 22 Mar 2017 13:52:50 +0300, Konstantin Khomoutov said:
>
> On Wed, 22 Mar 2017 12:07:55 +0300
> Konstantin Khomoutov wrote:
>
> [...]
> > Here, the job starts at 338:1 and ends at 339:10868, how do I write
> > out the bootstrap file's data to cover
On Wednesday 2017-03-22 12:07:55 Konstantin Khomoutov wrote:
> For instance, here's a fragment from the real output for one of my
> volumes (elided a bit for terseness):
>
> Begin Job Session Record: File:blk=338:1 SessId=142 \
>SessTime=1427996423 JobId=5007
>
On Wed, 22 Mar 2017 12:07:55 +0300
Konstantin Khomoutov wrote:
[...]
> Due to the uniqueness + tiny size + large quantities property of these
> data, we have decided to keep only the information on the last few
> backup session in the database to keep its size
On Wed, 22 Mar 2017 10:31:16 +0100
Andreas Nastke wrote:
> how about archiving the 'tiny' items into larger tar- or zip-files
> on a regular basis (say every 15 minutes) and then only backup the
> archives.
The thing is that having "low-level addressing" data in a
Hi There,
I have a bit of an issue with one of my Laptap backups. The user did not
plug in his laptop as often as required and he has now lost over 2 months'
worth of important data. There is two incomplete backups which has got
recent data, but it never completed successfully.
I have
how about archiving the 'tiny' items into larger tar- or zip-files
on a regular basis (say every 15 minutes) and then only backup the
archives.
Konstantin Khomoutov schrieb:
> Hi!
>
> I have a somewhat unusual Bacula setup as we're backing call records
> produced by a call-center software -- so
Hi!
I have a somewhat unusual Bacula setup as we're backing call records
produced by a call-center software -- so the files are tiny in size,
there is very large number of them produced daily, they are all unique
and we have to keep them for several years as required by the local
law.
Due to the