argh, found it.
because of using own user (not root) for backuppc, and haveing
user/rsync in sodoers ...
$Conf{RsyncClientPath} = 'sudo /usr/bin/rsync';
did finally the trick.
of corse, all the other "works" backups was also non-working at all.
(fast, but lots of access-denied)
btw.. v4 seems to be super-fast, compared to v3. :)
.ka
On 2021-08-24 23:23, klemens wrote:
hi,
I upgraded backuppc on the "server" ( the one who manages the backups
) from default-debian-repo buster to current bullseye.
(that's a 3.1.3 to 4.4.0 upgrade)
Also, I migrated all backups using the v3-to-4 script.
Running it for several clients, all work ok - except one box. ( some
clients are in local lan, some servers in internet )
This one is even in local network, 1gbit connect - but backups are
slooooow as hell.
Other systems have OS like already upgrade to debian-bullseye, still
debian-buster, suse, ...
The "broken" one is a debian-buster. ( basically, it should be the
final backup before upgrade... )
I managed to run an incremental, but a full ( that's about 100 gig )
wont run;
Here a few as-is and symptoms
- In general I use ssh/rync, an own user who's allowed via sudoers
file for rsync, ssh via sshkey; That's standard of all of the clients.
- an backup (incremental) _seems_ to work. (so doubt the ssh/rsync
setup is broken)
- when trying a full-backup, "nothing moves".
-- I see the directory / timestamps on server not moving... or just a
bit, some MB after one hour.
-- system-load on both boxes is near to zero. (no disk-io, no cpu, ...
)
-- on network ( I checked with "nethogs" ) very low traffic between
those boxes
-- the log does not show any issues
-- nothing suspect in syslog / msglog / authlog... on both boxes.
- connection is done via IP, not DNS.
- server and client was also rebooted in meantime (just in case some
update had some pending changes)
- all systems are "bored" - no io-ciritical things (raid-1 check),
have plenty of free mem, ...
- the server is rather small hardware (some 10years+ HP n40l +
software-raid-1 + LVM, ext4), but usually does it's job.
- disks are not full nor run out-of-inodes.
- for install, I accepted most of the debian-package defaults. (except
the hosts)
-- some other boxes (not as big) gets an backup.
- normal traffic between server-client ( e.g. scp, .. ) works fine
with good speed.
Currently I just run out of ideas what else could go wrong; pointing
to any direction might help.
lg
.klemens
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
