Believe is exerts from the log file for one of the machines...I too am puzzled�why it is so slow to get the data across. I am pulling my backup over an ADSL link - so the speeds are more like 16Mbps (http://www.speedtest.net/) for downloads - say about 2 Mega bytes per second .. which is about 7 Giga bytes per hour. So it should take approx 15 hours for a 100 Gig downloaded. I'm getting nowhere near that performance.
One machine has the following....If I look at the host status it shows the backup as being 14.2 days one old..i.e I don't believe it has added to the backup...although more disk space has been used on my backup server.
2011-03-15 19:06:52 Aborting backup up after signal INT
2011-03-15 20:00:01 full backup started for directory cDrive (baseline backup #0)
2011-03-15 23:47:03 Aborting backup up after signal PIPE
2011-03-15 23:47:04 Got fatal error during xfer (aborted by signal=PIPE)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/c:/WINDOWS/system32/dhcp/tmp.edb" (in cDrive): Device or resource busy (16)
[ skipped 6494 lines ]
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/c:/pagefile.sys" (in cDrive): Device or resource busy (16)
[ skipped 1944 lines ]
Done: 147039 files, 27635539899 bytes
full backup started for directory dDrive
Connected to rbs3.sysapps.net:873, remote version 29
Negotiated protocol version 28
Connected to module dDrive
Sending args: --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --ignore-times . .
Xfer PIDs are now 21002
[ skipped 13016 lines ]
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/CCM.LDF" (in dDrive): Device or resource busy (16)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/CCM.mdf" (in dDrive): Device or resource busy (16)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/CCMTest.mdf" (in dDrive): Device or resource busy (16)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/CCMTest_1.LDF" (in dDrive): Device or resource busy (16)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/CCMV2.mdf" (in dDrive): Permission denied (13)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/CCMV2_1.LDF" (in dDrive): Permission denied (13)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/CCMV3.mdf" (in dDrive): Device or resource busy (16)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/CCMV3_1.LDF" (in dDrive): Device or resource busy (16)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/CCMV4.mdf" (in dDrive): Device or resource busy (16)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/CCMV4_1.LDF" (in dDrive): Device or resource busy (16)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/EasyAudit.mdf" (in dDrive): Device or resource busy (16)
Remote[1]: rsync: send_files failed to open "ygdrive/c/WINDOWS/system32/d:/MSSQL2k5DATA/EasyAudit_1.ldf" (in dDrive): Device or resource busy (16)
[ skipped 41714 lines ]
Can't write 33138 bytes to socket
Read EOF:
Tried again: got 0 bytes
finish: removing in-process file backup/CCMV3/CCMV3_backup_201103140200.bak
Can't write 34674 bytes to socket
Child is aborting
Done: 42938 files, 26385343058 bytes
Got fatal error during xfer (aborted by signal=PIPE)
Backup aborted by user signal
Not saving this as a partial backup since it has fewer files than the prior one (got 189977 and 42938 files versus 219770)
On 15 March 2011 21:34, Jeffrey J. Kosowsky
<backuppc AT kosowsky DOT org> wrote:
Bowie Bailey wrote at about 16:39:59 -0400 on Tuesday, March 15, 2011:
�> On 3/15/2011 3:49 PM, David Herring wrote:
�> >
�> > I'm trying to backup windows servers with approx 3 partitions of 100G
�> > each over a WAN link. This takes 'days' to run and never successfully
�> > completes. I'm using rsyncd on the windows machines - and the backup
�> > is to a ubuntu server.
�> >
�> > So, how do you split the backups from a single machine - do you have
�> > to create multiple host entries for each machine ? Does this make
�> > restore too painful ?
�> >
�> > Is there anything else I should be doing ? MTU size ?
�>
�> You can split the backups by directories. �Just create separate backup
�> hosts that each backup some of the directories. �Give each host slightly
�> different names and use the "ClientNameAlias" setting to point them back
�> to the proper host name.
�>
�> Keep in mind that this may result in the separate backups running
�> simultaneously. �To prevent this you can use the "DumpPreUserCmd" and
�> "DumpPostUserCmd" to set and check for lock files.
�>
Bowie's suggestion is spot on.
But I'm still not sure why backup over WAN should take 'days' even for
300GB and even if this were the first time through or even if the
files changed heavily.
Assuming you have even low-end machines and a 100Mbps Internet, you
should be able to get O(5-10MBps) speeds which should complete your
backups in well under a day. Perhaps you have some large files that
are causing rsyncd timeouts? (you might want to check the 'timout'
parameter setting in rsync). Also, look at the client and server logs
to see why the backups don't complete.
