Hello,
I let know that I released Baculum version 7.2.1-0. In this release I
focused on performance improvements. Despite the fact that it is minor
release, in the version has been included numerous features. Below I
added changes list.
>From version 7.2.1-0 are prepared binary packages for: Cen
Oh boy!
I change bacula version to 7.2.0, set net keepalive to 60, set Spool Size,
like this
Maximum Spool Size = 500G
Maximum Block Size = 1032192
Maximum Network Buffer Size = 65536
Spool Directory = /var/spool/bacula
in bacula-sd.conf, but still get the error bellow:
17-Dec 16:30 stor
I will try update bacula to 7.2...
Somebody know where I can find deb package for Debian??
Thanks a lot
2015-12-17 15:20 GMT-02:00 Gilberto Nunes :
> Well...
> If the situation was that, I agreed with you, but that is not the case
> I have several clients...
> And one of them the bacula clie
> hello bacula users...
> Suddenly, bacula return me this error:
> Packet size too big from client
> This error happens just from one server.
> The server is Linux Debian 64 bits.
> I already down firewall for a while, just to check... No effect.
> Change the network interface and cable, to
Well...
If the situation was that, I agreed with you, but that is not the case
I have several clients...
And one of them the bacula client is the exactly same version of bacula
directory: 5.2.6...
And I get the exactly the same error
2015-12-17 15:12 GMT-02:00 Heitor Faria :
> hello
Hi again
I note that this trouble occurs just with Incremental backups.
I turn back to my old configuration with Diff backups and everythins to be
ok...
I will go forward to Diff's backups...
Thanks
2015-12-17 14:41 GMT-02:00 Gilberto Nunes :
> Hello bacula users...
>
> Suddenly, bacula return
Hello bacula users...
Suddenly, bacula return me this error:
Packet size too big from client
This error happens just from one server.
The server is Linux Debian 64 bits.
I already down firewall for a while, just to check... No effect.
Change the network interface and cable, to isolate bacul
We got approx 80 mio entries in the file table and I confirm Alan.
Before, we had MySQL 5.5 with 24GB buffer ram, but attribute insertions took
ages.
Then we migrated the DB to PostgreSQL and the issue resolved.
1 year ago, we migrated the physical backup Server to a vCenter VM and lowered
the
On Tue, Dec 15, 2015 at 05:16:42PM +, Alan Brown wrote:
>
> MySQL works ok for small sites but doesn't scale well. PostgreSQL is a
> heavy load on small installations but will keep running long after MySQL
> has decided to use all your system ram and swap too. The breakeven point
> is about
