Am 22.07.21 um 13:31 schrieb Stefan G. Weichinger:

Trying to tune my new 10G NICs with amanda.

So I want to switch from "auth ssh" to "auth bsdtcp" and get stuck ...

Debian Buster doesn't bring systemd-units for amanda, right?

I applied my own files now.

Edited hosts.allow

amservice succeeds.

amcheck not:

ERROR: backup: selfcheck request failed: ambind: bind failed A: Permission denied

what ...


Does someone use current Debian w/ amanda and bsdtcp?

Hints welcome.

I was able to fix it with some chown/chmod/setuid stuff, setting the Listener to a specific NIC etc ...

I am surprised that the Debian package doesn't bring working systemd-units. Do you all use "auth=ssh" ?

IMO that doesn't perform optimal, it seems that it is limited by one CPU core, right?

-

I am trying to optimize an installation and pinpoint the bottleneck.

The amanda-server has a 10GB/s NIC, and a 2TB SSD as holdingdisk.

"atop" shows the holdingdisk at ~100% while it only writes with ~100 MB/s.

In local benchmarks I am able to write with more than 220 MB/s.

OK, only one of the amanda client hosts delivers via 10 GB/s NIC as well, the others are 1 GB/s only.

-

I defined this in amanda.conf

define interface chelsio {

    comment "10G NIC"

    use 10 Gbps

}



and use it in all DLEs in the disklist ... because that NIC is running all the dumps.

-

I disabled compression for test DLE to focus on network and storage.

A 40 GB DLE gets an

Avg Dump Rate (k/s)       113744

I expect more. Any ideas?




Reply via email to