Nick Webb wrote:
> Rich Rauenzahn wrote:
>> dan wrote:
>>> no, incrementals are more efficient on bandwidth. they do a less
>>> strenuous test to determine if a file has changed.
>>>
>>> at the expense of CPU power on both sides, you can compress the rsync
>>> traffic either with rsync -z
>> Have you tried rsync -z? Last I heard, BackupPC's rsync modules don't
>> support it.
>>
>> Rich
>
> Actually, if I use the -z/--compress option in rsync or use ssh
> compression BackupPC dies after a few hours (aborted by signal=PIPE).
> Any suggestions on how to figure out why this is failing. Works fine
> without compression, but takes forever...
>
> 2008-02-19 14:59:05 full backup started for directory /
> 2008-02-19 22:25:42 Aborting backup up after signal PIPE
> 2008-02-19 22:25:48 Got fatal error during xfer (aborted by signal=PIPE)
> 2008-02-19 22:25:48 Saved partial dump 43
> 2008-02-19 23:00:01 removing incr backup 27
Backuppc's perl version of rsync doesn't support the -z option.
However, it should work to add -C to ssh like this:
$Conf{RsyncClientCmd} = '$sshPath -C -l root $host $rsyncPath $argList+';
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
