[Cialug] rsnapshot problem with compression

[Tom Pohl]

Do you have the same version of rsync on both sides of the connection?

I've run into issues with mismatched versions of rsync.  The other thing I've found is that even with really fast CPUs on both ends, unless you have a relatively small pipe between the two servers, you'll slow down the transfer by turning on compression.

-Tom


On Jun 14, 2010, at 9:11 PM, Josh More wrote:

> Could the built-in OpenSSH compress be conflicting with rsync's?
> 
> Try running the server in debug mode and see where it dies.
> 
> 
> -Josh More, CISSP, GIAC-GSLC, GIAC-GCIH, RHCE, NCLP
> morej at alliancetechnologies.net
> 515-245-7701
> 
> ________________________________________
> From: cialug-bounces at cialug.org [cialug-bounces at cialug.org] on behalf of L. V. Lammert [lvl at omnitec.net]
> Sent: Monday, June 14, 2010 21:06
> To: Central Iowa Linux Users Group
> Subject: [Cialug] rsnapshot problem with compression
> 
> Trying to get compression working on one of our backup jobs, .. but it
> seems to be choking as soon as I add the --compress:
> 
> /usr/local/bin/rsync -a --delete --numeric-ids --relative
> --delete-excluded \
>    --compress --exclude=/dev/ --exclude=/mnt --exclude=/sys/ \
>    --exclude=.gvfs/ --exclude=/lost+found/ --exclude=/media/ \
>    --exclude=/proc/ --exclude=/tmp/ --exclude=/u/VM/ --exclude=.Trash* \
>    --exclude=/u/Downloads/ --exclude=/u/VBoxBackup/ --rsh="/usr/bin/ssh
> ..
> 
> received request to transfer non-regular file: 3286 [receiver]
> rsync error: protocol incompatibility (code 2) at rsync.c(336)
> [receiver=3.0.6]
> rsync: writefd_unbuffered failed to write 4 bytes to socket [generator]:
> Broken pipe (32)
> rsync error: error in rsync protocol data stream (code 12) at io.c(1525)
> [generator=3.0.6]
> 
> Does anyone have a suggestion as to why compression is blowing up the
> 'conversation' and/or how to get it working properly? The backup DOES work
> without compression, but it ran a week [plain DSL] without completing the
> bacukp (it DID get about 40GB), so the only way to get a snapshot is to
> get compression working.
> 
>        Lee
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug