Re: [BackupPC-users] Error in rsync protocol data stream

A quick overview of my setup: I’ve got two backup servers backing up these three file servers (and others that aren’t relevant at the moment). The filesystems on these servers are split across the 2 backup servers, so each file server is serviced by each Backup server. These file servers each have 2 network interfaces, one a dedicated “backup” network, the other our main network.

Michael’s suggestion on 7/5 reminded me of the fact that I hadn’t tried to backup this server over the Main interface, I’ve had no problems since making that switch. This would lead me to believe that there’s a problem with the ‘backup’ interface, except the other Backup server has experienced no issues while using the backup interface.

It usually fails somewhere in the second filesystem (each file system is, at the moment, between 25-50 gigs), so maybe a bit much for a verbose dump, but I”ll give it a try.

we’re not using -Z:

/usr/local/bin/rsync_bpc --bpc-top-dir /export/BackupPC --bpc-host-name $HOST.backup --bpc-share-name /export/home/students/0 --bpc-bkup-num 21 --bpc-bkup-comp 3 --bpc-bkup-prevnum 20 --bpc-bkup-prevcomp 3 --bpc-bkup-inode0 272512 --bpc-attrib-new --bpc-log-level 3 -e /export/BackupPC/bin/ssh\ -l\ root --rsync-path=/usr/bin/rsync --super --recursive --protect-args --numeric-ids --perms --owner --group -D --times --links --hard-links --delete --partial --log-format=log:\ %o\ %i\ %B\ %8U,%8G\ %9l\ %f%L --stats --one-file-system --checksum-seed=32761 --timeout=36000 $HOST.backup:/export/home/students/0/ /

Thanks for your help,

Wade

From: Craig Barratt via BackupPC-users <backuppc-users AT lists.sourceforge DOT net>
Reply-To: "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Date: Sunday, July 9, 2017 at 11:13 PM
To: "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Cc: Craig Barratt <cbarratt AT users.sourceforge DOT net>
Subject: Re: [BackupPC-users] Error in rsync protocol data stream

Wade,

How far does it get when you get the error? If it doesn't get very far, you could manually run:

BackupPC_dump -f -v client

and email the output. If instead it happens a long way into the backup, please send the exact rsync_bpc command that is being run (from the XferLOG file)?

One potential issue: are you using the -z (--compress) option in RsyncArgs?

Craig

On Wed, Jul 5, 2017 at 10:56 AM, Michael Stowe <mstowe AT chicago.us.mensa DOT org> wrote:

On 2017-07-05 09:06, Jenkins, Wade William wrote:

I’ve been wrestling with a BackupPC 4 install since March (updating to each successive release as they come). All but one of my servers backs up perfectly fine. One of my 3 file servers (all software-identical) routinely encounters “rsync error: error in rsync protocol data stream (code 12) at io.c(226)” where it then sits until the timeout period has passed (though, the past few backups have hung well beyond the timeout period).

I’ve tried changing the backup method to tar from rsync, moving directories from filesystem to filesystem, and looking for/fixing messed up file attributes. These have offered temporary relief from the problem, but it seems that the second incremental backup after the ‘fix’ is attempted will hang indefinitely.

Does anyone have any thoughts about how to troubleshoot this kind of problem?

—

Wade Jenkins

rsync can be somewhat vague about what has gone wrong, especially if something is going wrong at the other end of the transaction: the first thing to note is that the BackupPC side does not have the details because it is the remote side that is encountering some kind of issue, so you'll need to engage more detailed troubleshooting on that side.

It helps to have a sense of what typically goes wrong with (a properly configured) rsync — media failure, filesystem corruption, resource exhaustion, capability/version mismatch, ssh issues, network problems, permission issues — these all fall into the generic catch-all error you're seeing on the remote end.

For troubleshooting, you can log the remote side in detail or trace it to identify what the exact issue is. Using tar implies that media failure may not be the cause, but not necessarily, as tar and rsync read files a bit differently. You'll want to look at whether the failures always occur at the same place, and if rsync itself turns up nothing obvious, the network/ssh should be examined.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/