On Sun, Aug 30, 2009 at 2:13 PM, Jeffrey J. Kosowsky
<backu...@kosowsky.org>wrote:
> dan wrote at about 14:00:43 -0600 on Sunday, August 30, 2009:
> > I personally think that using ssh compression is the better method. I
> say
> > this because running rsync through ssh encrypts the data and compresses
> > it(optionally). Unless you plan to run rsync in the clear then the
> built in
> > compression isnt needed.
>
> ssh adds overhead with its encryption. Of course, I was referring to
> the case when you are comfortable running rsync/rsyncd in the clear.
>
> sure ssh adds some overhead, but how much are you talking and where? It is
really just adding cpu overhead as ssh's compression more than compensates
for added data transmitted between hosts.
to reduce the encryption overhead you could do ssh -c blowfish which is much
faster (10x) than the default cypher of 3des.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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/
