I have a Win2k box running the rsyncd package. It is over an 802.11g link (about 1MB/s throughput when copying via windows shares manually, but over rsync it's getting closer to 350k). Thus it takes about 40 or so hours to backup the system. I've taken to excluding tons of stuff just to get a full backup to complete, then for each incremental, I remove one or two directories from the exclude paths to introduce the files to the backup pool. Painful.
Well, I put in a directory with a few very large files in it and it started failing to backup at around the 23 hour mark. Mind, I've extended the ClientTimeout to 720000. Here's what the rsyncd.log has on it: 2006/12/05 08:37:42 [6824] rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Connection reset by peer (104) 2006/12/05 08:37:42 [6824] rsync error: error in rsync protocol data stream (code 12) at io.c(1119) [sender=2.6.8] 2006/12/05 08:56:25 [6900] connect from backup.flaredev.com (192.168.0.196) 2006/12/05 08:56:27 [6900] rsync on . from [EMAIL PROTECTED] (192.168.0.196) 2006/12/05 09:05:41 [6900] rsync: writefd_unbuffered failed to write 4 bytes [sender]: Software caused connection abort (113) 2006/12/05 09:05:41 [6900] rsync error: error in rsync protocol data stream (code 12) at io.c(1119) [sender=2.6.8] The server status says the program was interrupted by sig=ALRM, which I'm assuming is the client timeout. Any ideas? Thanks, JH ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
