From owner-freebsd-isp@FreeBSD.ORG Mon Jun 2 10:53:21 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3719137B417 for ; Mon, 2 Jun 2003 10:53:21 -0700 (PDT) Received: from ip68-2-98-210.ph.ph.cox.net (ip68-2-89-14.ph.ph.cox.net [68.2.89.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5996B43FAF for ; Mon, 2 Jun 2003 10:53:20 -0700 (PDT) (envelope-from joeym@ip68-2-98-210.ph.ph.cox.net) Received: (from joeym@localhost) by ip68-2-98-210.ph.ph.cox.net (8.11.6/8.11.6) id h52HxAr01064; Mon, 2 Jun 2003 17:59:10 GMT (envelope-from joeym) Date: Mon, 2 Jun 2003 10:59:09 -0700 From: Joe Miller To: Wolfpaw - Dale Corse Message-ID: <20030602175909.GL51524@joeym.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i cc: freebsd-isp@freebsd.org Subject: Re: Mirror Server X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: joeym@joeym.net List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2003 17:53:21 -0000 You can eliminate having to have a huge chunk of space available with tar by piping the tar output to another tar process that immediately writes the data to the new disk, ie: tar cvf - / | (cd /backup/disk ; tar xvf - ) -- Joe Miller On Mon, Jun 02, 2003 at 10:45:03AM -0600, Wolfpaw - Dale Corse wrote: // Hmm.. 10 gig in 1/2 hr or so.. its not wonderful, we use // something entirely different for shell servers (we have // 20 of them..). This is good for an "internal" machine, // but if your looking for fast backups, use tar with the // update flag.. it works nicely. The nice thing about // rsync is it can reproduce the entire fs as it was, // without some of the problems tar has.. such as having // to have a huge chunk of space so you can tar one // disk, and then untar onto another.. // // Anyway.. my 2 cents :) // D. // -------------------------------- // Dale Corse // System Administrator // Wolfpaw Services Inc. // http://www.wolfpaw.net // (780) 474-4095 // // > -----Original Message----- // > From: Michael DeMan [mailto:michael@staff.openaccess.org] // > Sent: Monday, June 02, 2003 10:21 AM // > To: Wolfpaw - Dale Corse; Thomas Dwyer; freebsd-isp@freebsd.org // > Subject: Re: Mirror Server // > // > // > What is your performance with this? I've seen awful // > performance with rsync // > and big file systems. We've thought of adding the flag to // > only check the // > file modification date to help reduce this. // > // > - mike // > // > On 6/2/03 8:33 AM, "Wolfpaw - Dale Corse" // > wrote: // > // > > Hi Tom, // > > // > > I use this to mirror one of our servers to another disk in // > > the same machine. How we did it was we installed FreeBSD on // > > that disk in another machine, and then put it in the main // > > server.. now we just run this script periodically, and // > > we have a backup solution :) // > > // > > Hope it helps :) // > > D. // > > // > > #!/bin/sh // > > # Rsync Backup Script // > > // > > export PATH=/usr/local/bin:/usr/bin:/bin // > > LIST="bin dev etc lib mnt sbin usr boot dbu home root tmp var" // > > // > > echo "Copying files.." // > > #Loop thru the list // > > for d in $LIST; do // > > echo -n "... COPYING: /$d/" // > > /usr/local/bin/rsync --delete -ax /$d/ /disk2/mirror/$d/ // > > echo " " // > > done // > > // > > echo "Backup Complete .. Exiting." // > > // > > -------------------------------- // > > Dale Corse // > > System Administrator // > > Wolfpaw Services Inc. // > > http://www.wolfpaw.net // > > (780) 474-4095 // > > // > >> -----Original Message----- // > >> From: owner-freebsd-isp@freebsd.org // > >> [mailto:owner-freebsd-isp@freebsd.org]On Behalf Of Thomas Dwyer // > >> Sent: Monday, June 02, 2003 8:01 AM // > >> To: freebsd-isp@freebsd.org // > >> Subject: Mirror Server // > >> // > >> // > >> Hello; // > >> // > >> I would like to setup a backup server to replace the main // > >> server should a disaster occur. I have experimented abit // > >> with rsync and it looks like it would do the job. // > >> // > >> My question is; what files or binaries should not, or // > >> cannot be replicated? Obviously the kernel should be separate. // > >> // > >> I want to be able to take the backup, plug it in where the // > >> primary was, change the IP and everything would be as it // > >> was up until the point of the last rsync. // > >> // > >> Thanks // > >> Tom // > >> _______________________________________________ // > >> freebsd-isp@freebsd.org mailing list // > >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp // > >> To unsubscribe, send any mail to // > >> "freebsd-isp-unsubscribe@freebsd.org" // > >> // > > // > > _______________________________________________ // > > freebsd-isp@freebsd.org mailing list // > > http://lists.freebsd.org/mailman/listinfo/freebsd-isp // > > To unsubscribe, send any mail to // > "freebsd-isp-unsubscribe@freebsd.org" // > > // > // > Michael F. DeMan // > Director of Technology // > OpenAccess Internet Services // > 1305 11th St., 3rd Floor // > Bellingham, WA 98225 // > Tel 360-647-0785 x204 // > Fax 360-738-9785 // > michael@staff.openaccess.org // > // > // > // > // // _______________________________________________ // freebsd-isp@freebsd.org mailing list // http://lists.freebsd.org/mailman/listinfo/freebsd-isp // To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"