I've got a user running Win7-64 with 3 large drives: C (original boot), D
(data), and G (Win7 boot). I've configured rsyncd on it to serve them as 3
modules named for the drive letters. A full backup to my CentOS 5 box
takes about 40 hours, and an incremental takes about 8, so I've
configured
On Sun, Jul 8, 2012 at 9:59 PM, Kenneth Porter sh...@sewingwitch.com wrote:
I've got a user running Win7-64 with 3 large drives: C (original boot), D
(data), and G (Win7 boot). I've configured rsyncd on it to serve them as 3
modules named for the drive letters. A full backup to my CentOS 5 box
On Monday, July 09, 2012 9:24 AM -0500 Michael Stowe
mst...@chicago.us.mensa.org wrote:
You don't say how big the drives are, but 40 hours says terabytes to me.
If that's not the case, I'd seriously consider [re]examining your rsync
version on the client. (Or perhaps beefing up your
On Mon, Jul 9, 2012 at 12:56 PM, Kenneth Porter sh...@sewingwitch.com wrote:
The total size is 0.5 TB according to the Host Summary page. The network is
100 Mbit. The server is a Dell PE2900 with 4 GB. Probably the slowest link
is the external USB drive used to hold the backup on the server,
Probably the slowest link
is the external USB drive used to hold the backup on the server, formatted
as ext3.
In that case, let me add don't do this, it's insanely slow to my list of
suggestions.
--
Live Security
On Monday, July 09, 2012 2:19 PM -0500 Les Mikesell lesmikes...@gmail.com
wrote:
See the docs about adding '--checksum-seed=32761'. It will save
reading/uncompressing the server-side copy for the next comparison,
but note that it doesn't start working until after the 2nd full run
with an
I've got a user running Win7-64 with 3 large drives: C (original boot), D
(data), and G (Win7 boot). I've configured rsyncd on it to serve them as 3
modules named for the drive letters. A full backup to my CentOS 5 box
takes about 40 hours, and an incremental takes about 8, so I've
configured
