I had a similar problem recently though BackupPC displayed a different
error message. It managed to backup a 1.3TB file the first time it
tried but rsync failed miserably when trying to back it up again on a
subsequent occasion.
Quite a job tracking down the file in the pool and flushing it cleanly.
Paul
On 23/07/2024 20:37, G.W. Haywood wrote:
Hi there,
On Tue, 23 Jul 2024, Les Mikesell wrote:
On Mon, Jul 22, 2024 at 9:54?AM Johnny PINSON wrote:
> yes, the two servers used to be backup up by a backuppc server but,
due
> to raid's controller issue, it can no longer.
>
> I tried the keepalive trick :
> ...
> But it did not fix the issue.
> ...
I no longer have a working system to test, but I think adding -o
ServerAliveInterval=60 after $sshPath in $Conf{RsyncClientCmd} should
work. Is there some sort of error listed in your Xferlog for the
failed backups? Another somewhat remote possibility is that you have
some sort of file corruption on the clients causing the remote rsync
to hang up.
IIRC a while back when I had an X server go off the reservation and it
produced multi-gigabyte dot-error files, something similar happened.
The fix was to fix the server and delete the junk files of course.
If there are huge files to be backed up that might be an issue in any
case. For example I wouldn't recommend using BackupPC for things like
VM disk images.
_______________________________________________
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/
