So are you saying that using Tar over ssh would be a better option in this case? (Im not sure what netcat is)
| Carl Wilhelm Soderstrom
<[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 10/03/2006 08:27 AM |
|
> On Thu, 2006-03-09 at 14:40, [EMAIL PROTECTED] wrote:
> > it just hovers at about 300kb/s.... I would expect that when the file
> > listing is sent, for there to be a heavy load on the network at that
> > time, and then some heavy cpu work, and then more load on the network
> > as it hits files that
> > needs to backup.....
rsync is surprisingly inefficient at file transfers. It's often several
times slower than even tar over ssh. try moving a big (several times larger
than RAM) over the network, using rsync, tar over ssh, and tar over netcat.
rsync will be by far the slowest.
--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
------------------------------------------------------------
Mail was checked for spam by the Freeware Edition of No Spam Today!
The Freeware Edition is free for personal and non-commercial use.
You can remove this notice by purchasing a full license! To order
or to find out more please visit: http://www.no-spam-today.com
