BackupPC-users

Re: [BackupPC-users] Issue with multiple restores

2015-05-21 12:10:37
Subject: Re: [BackupPC-users] Issue with multiple restores
From: Andy Taylor <andy.taylor AT sift DOT com>
To: backuppc-users AT lists.sourceforge DOT net
Date: Thu, 21 May 2015 17:08:33 +0100
After a bit more digging I've managed to get a bit more information out of the logs:

2015/05/21 15:15:09 [14010] Invalid remainder length 467096064 [receiver]
2015/05/21 15:15:09 [14010] rsync error: protocol incompatibility (code 2) at io.c(1352) [receiver=3.0.9]
2015/05/21 15:15:09 [14010] [receiver] _exit_cleanup(code=2, file=io.c, line=1352): about to call exit(2)
2015/05/21 15:15:09 [14010] rsync: connection unexpectedly closed (1022021 bytes received so far) [generator]
2015/05/21 15:15:09 [14010] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [generator=3.0.9]
2015/05/21 15:15:09 [14010] [generator] _exit_cleanup(code=12, file=io.c, line=605): about to call exit(12)

Does anyone have any idea what this might be? It seems the protocol incompatibility error can sometimes be down to the version of rsync you are using, but I have tried a few different versions with no success.

Andy Taylor
Operations Engineer

Bridge House, 48-52 Baldwin Street, Bristol, BS1 1QB
direct:+44 (0)1179158634 | mob: +44 (0)7730 019316
www.sift.com | digital thinking
Sift Ltd is registered in England and Wales no. 3230061

On 14 May 2015 at 16:09, Andy Taylor <andy.taylor AT sift DOT com> wrote:
Hello,

I'm currently looking at regularly restoring files out of BackupPC to a central location on our network for some of our users to have as a reference. I'm going to run this restore on a daily basis to ensure that the files are up to date.

This seems to work fine for all of our hosts except for one. The first restore works fine, but any subsequent restores fail right at the end with this error:

Remote[1]: Invalid remainder length 467096064 [receiver]
exiting after signal PIPE
restore failed: aborted by signal=PIPE

It only happens on this one host, and it only seems to happen at the very end of the restore. Has anyone seen anything like this before?

The only way I've managed to get around it is by adding --ignore-existing or --whole-file as extra RsyncRestoreArgs. This would seem to imply to me that rsync is failing when it tries to compare/overwrite a file on the receiver, but I'm not really sure.

Thanks,

Andy

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
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/