From owner-freebsd-isp Fri Dec 13 9:11:24 2002 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 B83BE37B404 for ; Fri, 13 Dec 2002 09:11:22 -0800 (PST) Received: from marklar.blazingdot.com (marklar.blazingdot.com [207.154.84.83]) by mx1.FreeBSD.org (Postfix) with SMTP id 4F5A043EA9 for ; Fri, 13 Dec 2002 09:11:22 -0800 (PST) (envelope-from marcus@blazingdot.com) Received: (qmail 312 invoked by uid 503); 13 Dec 2002 17:11:22 -0000 Date: Fri, 13 Dec 2002 09:11:22 -0800 From: "Marcus L. Reid" To: Simon Cc: "freebsd-isp@FreeBSD.ORG" Subject: Re: network backup Message-ID: <20021213171122.GA99250@blazingdot.com> References: <20021213142728.GA92171@blazingdot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Coffee-Level: high Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Dec 13, 2002 at 11:45:31AM -0500, Simon wrote: > > They don't change a whole lot, but they do change and new ones are > uploaded. What I'm trying to do is build massive network backup server, > backing up 6+ servers simultaneously. Each server has about 50-100gb > worth of data to be backed up daily. I did look at dump, looks great, the > only problem is that it can't backup individual directories, rather whole > filesystems, if I didn't misread something. Is there some reason that you don't want to back up all of your data? You can use tar to similar effect, but dump/restore works really well when it comes to making full backups of your system. If you use something else to back up your text files, I still recommend using dump for the rest. You are backing up the rest, aren't you? ;) A system that I've used in the past works as follows. On each machine to be backed up: The operator user (the one with read access to the /dev disk devices, can vary with Linux, etc.) on each server is given a home directory and a valid shell (just * for the password field in your passwd file though.) Place the public key of the user on the backup machine into the .ssh/authorized_keys file of the operator user. On the backup machine: Run dump remotely on the server to back up over ssh. The command looks like: ssh yourserver dump -$DUMPLEVEL -u -a -h 0 -f - /dev/$DEVICE | \ gzip > $ARCHIVES/$MACHINE-$DEVICE-$DATE-$DUMPLEVEL.dump.gz The dump output goes out stdout, through ssh, through gzip, and neatly into a file on your backup server. All diagnostic messages go out stderr and are easily mailed to you separately. The backup machine is the one that does the compression here, but that's changed by adding a \ before the |. If you've got a tape library things will look a little different, but you get the idea. > > -Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message