From owner-freebsd-questions@FreeBSD.ORG Wed Jan 28 23:07:26 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7437106566B for ; Wed, 28 Jan 2009 23:07:26 +0000 (UTC) (envelope-from rsk@gsp.org) Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by mx1.freebsd.org (Postfix) with ESMTP id 856098FC08 for ; Wed, 28 Jan 2009 23:07:26 +0000 (UTC) (envelope-from rsk@gsp.org) Received: from squonk.gsp.org (bltmd-207.114.25.46.dsl.charm.net [207.114.25.46]) by taos.firemountain.net (8.14.1/8.14.1) with ESMTP id n0SMoLIM010612; Wed, 28 Jan 2009 17:50:22 -0500 (EST) Received: from avatar.gsp.org (avatar.gsp.org [192.168.0.11]) by squonk.gsp.org (8.14.1/8.14.1) with ESMTP id n0SMeoML000744; Wed, 28 Jan 2009 17:40:50 -0500 (EST) Received: from avatar.gsp.org (localhost [127.0.0.1]) by avatar.gsp.org (8.14.3/8.14.3/Debian-4) with ESMTP id n0SMoFkx023363; Wed, 28 Jan 2009 17:50:15 -0500 Received: (from rsk@localhost) by avatar.gsp.org (8.14.3/8.14.3/Submit) id n0SMoFhI023362; Wed, 28 Jan 2009 17:50:15 -0500 Date: Wed, 28 Jan 2009 17:50:15 -0500 From: Rich Kulawiec To: Martin McCormick Message-ID: <20090128225015.GA22170@gsp.org> References: <200901272230.n0RMUsk7035006@dc.cis.okstate.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200901272230.n0RMUsk7035006@dc.cis.okstate.edu> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-questions@freebsd.org Subject: Re: Looking for a Good FreeBSD and General Unix Backup System X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2009 23:07:27 -0000 On Tue, Jan 27, 2009 at 04:30:54PM -0600, Martin McCormick wrote: > What we plan to do is backup a bunch of Unix systems to > one FreeBSD box and then use a commercial package to back that > box up to an enterprise-wide system we use. The archiver we need > must be able to make 1 full backup of each system like tar and > then incrementals until we are ready for another full backup. The best choice is dump, which was designed and built for exactly this purpose. (tar is fine for archives of static hierarchies, but it is not suitable for full-system backups.) Dump fully supports the concept of full/partial backups in a robust manner. (It has other useful features as well, notably its ability to deal with non-quiescent filesystems in a sensible way.) Excellent backup systems can be built with judicious use of dump -- you don't need to waste money on commercial products. [1] Depending on your specific requirements, it may be desirable to combine dump with other programs you already have (e.g., rysnc, gzip/bzip, scp, and so on). For example, I recently had occasion to build a system which backed up and replicated a multi-terabyte repository across a WAN. Using just the tools already on the system, and about 300 lines of shell (2/3 of which are comments), it wasn't that difficult to meet both requirements and do so in a way that minimized the bandwidth needed. This is really no big deal: it's just a matter of selecting the right tools and combining them -- which is the essence of the Unix philosophy. ---Rsk [1] Every commercial backup system I've evaluated for Unix -- over many, many years -- has produced inferior results. It pains me to watch people waste money on over-priced, under-performing and often-insecure commercial packages when they already have all the software they need...and just need to learn how to use it.