Sorry. I missed that the PC ran Mint, so it should not be a buffer
issue. Are you sure data spooling is enabled for the desktop PC job?
On 11/27/25 15:10, Phil Pemberton via Bacula-users wrote:
I'll give that a shot, but both machines are running Linux.
Thanks
Phil.
On 24/11/2025 16:50, Josh Fisher via Bacula-users wrote:
In both the FD and SD config files, set Maximum Network Buffer Size =
32768. The default size of 64k is known to cause this issue in
Windows, or at least certain versions of Windows using certain NICs.
You will need to restart bacula-sd on the server and bacula-fd on the
Windows PC before testing.
On 11/21/25 09:55, Phil Pemberton via Bacula-users wrote:
Hi all,
I've been using Bacula to back up my NAS for some time, and it's
been working well. I see effective backup rates of about 30MB/s all
told (100MB+ unspooling from SSD to tape, maxing out the LTO6 drive).
Unfortunately when I added my desktop PC to the backup cycle, I
found that the effective rate dropped like a rock, to single-digit
megabytes per seconds.
The machines are both fairly fast -- the desktop machine (backup
source running the FD) is a Ryzen 5 5600X, and the server (with the
SAS SSD and tape drive) is an Intel Core i5-9400.
The network is gigabit end-to-end, and the transfer rates I'm seeing
are very poor. Other applications taking the same path are much faster.
Both systems are running Debian derivatives -- the desktop runs Mint
with Bacula 13.0.4, and the server runs Ubuntu 24.04 with the same
version of Bacula.
Is there anything I can do to improve performance backing up over
the network, before I resort to a nightly Rsync from the workstation
to the server and backing up from there?
Thanks.
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
