Rich Rauenzahn wrote:
>
>>
>> Compression is done on the server side after the transfer. What's the
>> point of using different methods? According to the docs, compressed
>> and uncompressed files aren't pooled but different levels are. The
>> only way to get compression over the wire is to add the -C option to
>> ssh - and you'll probably want to use rsync if bandwidth matters.
>>
>
> Because if I'm transferring the backup at 40kbps/sec across the
> internet, bzip2'ing on the server isn't going to slow down the backup,
> which is the main reason for not using the higher compression.
Don't you run several concurrent backups? Unless you limit it to the
number of CPUs in the server the high compression versions will still be
stealing cycles from the LAN backups.
> I am using ssh -C as well. And see my other post about rsync --compress
> -- it is broken or something.
It is just not supported by the perl rsync version built into backuppc.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
