Are you using the "--partial" option for rsync? The best approach I've seen using rsync for backups uses a wrapper to setup a lock-file of sorts, kicked off [repeatedly] by a cron job... the wrapper script will not try to do 2 rsyncs at once, in short. Sticking with rsync for now... do you have any reasons other that network timeouts to desire a different solution?
Ben PS - you may also want to consider "--partial-dir" and "--delay-updates" options... and have a wrapper script setup so that you can confirm when the xfer is in fact complete. Consider recording changes via a versioning system on the receiving end, each time a transfer is noted at complete. On Mon, Mar 3, 2008 at 9:29 AM, Rob Hudson <[EMAIL PROTECTED]> wrote: > Hi LUG, > > I'm helping a friend set up a sort of backup solution. He's got a > co-located Linux web server, and a Linux file server in his office > behind a firewall. I set up an rsync script to synchronize (pull) all > the web files down at night. The problem is that it's dying about 25% > of the way through. From the log error output it appears that since > rsync can sometimes take a bit of time, something happens to the > network connection during the sync and drops the connection. This is > the closest explanation I could find: > http://www.mail-archive.com/[EMAIL PROTECTED]/msg14422.html > > So, what's a good alternate backup strategy? > > Goals are: > * Mirror the directories on remote server periodically. > * Would be nice to only pull down differences to save bandwidth but at > this point it's not a priority. > > Thanks, > Rob > _______________________________________________ > EUGLUG mailing list > [email protected] > http://www.euglug.org/mailman/listinfo/euglug > _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
