Re: [BackupPC-users] Issue with multiple restores

Thank you for the advice Les. I compiled rsync 2.6.9 and tried a restore with it. It seems to hang now once it's got past the last file of the restore - I've run strace against the rsync processes and I can see it close the last file and then just hang, with this sort of output:

[pid 15625] select(4, [3], [], NULL, {53, 660732} <unfinished ...>
[pid 15624] select(7, [3 6], [], NULL, NULL <unfinished ...>
[pid 15662] select(1, [0], [], NULL, {6, 915513}) = 0 (Timeout)
[pid 15662] select(1, [0], [], NULL, {60, 0} <unfinished ...>
[pid 15625] <... select resumed> ) = 0 (Timeout)
[pid 15625] select(4, [3], [], NULL, {60, 0} <unfinished ...>
[pid 15662] <... select resumed> ) = 0 (Timeout)

Do you know what that might indicate about the restore?

With regards to tar, I don't care much about the bandwidth, but the speed of rsync would be very useful for the restores. I'll have a look at how fast tar is over SSH.

Thanks again,

Andy

On 21 May 2015 at 17:25, Les Mikesell <lesmikesell AT gmail DOT com> wrote:

On Thu, May 21, 2015 at 11:08 AM, Andy Taylor <andy.taylor AT sift DOT com> wrote:
>
> 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.

Did you try going down to a 2.x version of rsync? Newer versions are
supposed to negotiate the protocol level but it looks like that isn't
happening in this situation. But, unless you care about the
bandwidth used, you could just script something around the command
line BackupPC_tarCreate tool piped though ssh to a remote extract
instead of using rysnc for this at all.

--
Les Mikesell
lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
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/

------------------------------------------------------------------------------
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/