hi i have a 'push' type rsync script, which pushes out tar backup files to a backup repository machine that looks like
/usr/local/bin/rsync -e ssh -avz --delete --stats /usr/home/user/backupserver*tar.gz server2:/mnt/drive2/serverdailybackup/ this script rsyncs over ssh, over a short distance w t1 connections at both ends and works fine. i have a 'pull' type rsync script which pulls tar backups from the backup repository machine that looks like /usr/local/bin/rsync -e ssh -avz --delete --stats server2:/mnt/drive2/serverdailybackup/backupserverusrlocal.tar.gz /mnt/drive2/serverbackup/ this script rsyncs over ssh, over a long distance - the two machines are not in the same building, geographically like 10 miles apart. this script is pulling some large tar files, some 1-2 gig in size. it has yet to finish pulling tar files off the repository. it usually cuts off before it completes - i get: 'read from remote host host.ip.address.com: connection reset by peer rsync: connection unexpectedly closed...' any advice on how to modify either the ssh setup on either host, or the script itself, so that rsync through the secondd script would be stable enough to allow the rsync operation to finish completely? in the second script, we're doing a 'pull' rsync operation from host a (on cable modem), to host b (t1). in the first script, we're doing a 'push' rsync operation from host c (t1) to host b (t1). thanks for any advice. -- Redmond Militante Software Engineer / Medill School of Journalism FreeBSD 5.2.1-RELEASE-p10 #0: Wed Sep 29 17:17:49 CDT 2004 i386 9:45AM up 21:57, 1 user, load averages: 0.01, 0.18, 0.24
pgpos1KZNHawJ.pgp
Description: PGP signature
