From owner-freebsd-isp Wed Dec 16 13:25:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14013 for freebsd-isp-outgoing; Wed, 16 Dec 1998 13:25:15 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14006 for ; Wed, 16 Dec 1998 13:25:13 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id NAA15388; Wed, 16 Dec 1998 13:23:50 -0800 (PST) (envelope-from dhw) Date: Wed, 16 Dec 1998 13:23:50 -0800 (PST) From: David Wolfskill Message-Id: <199812162123.NAA15388@pau-amma.whistle.com> To: gary@tbe.net, ingrid@cityscope.net Subject: Re: Backup server Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Date: Wed, 16 Dec 1998 15:53:47 -0500 (EST) >From: "Gary D. Margiotta" >We are looking into the smae thing... I believe we will be using the >'dump' command for this. It is my understanding that the commands are >simple and allow full backups of entire filesystems. Yes, that is what dump does. >I believe it uses >the r* commands, so mamke sure they are enabled, (mostly rcp). Some >people are using ssh in place of rsh, that way it is much more secure. Yes, but I encourage you to see below. >Do a man of dump, and it is pretty explanatory. (Except that historically -- not sure about the FreeBSD implementation(s) -- the relationships among the various metrics that one might think would affect how much data can actually fit on the medium of choice -- size & density -- has seemed to have a rather tenuous attachment to any sort of objective reality. In other words, the numbers need to be tweaked to meet one's expectations.) We have a rather different problem, as far as scope and all: I'm doing backups for the engineering net (servers & most of the UNIX workstations) here at Whistle. Given that, I'm using "amanda" (it's in the ports, but I built it from source, since I have a somewhat heterogeneous set of machines, and I wanted to be sure I was using the same sources for all of them). It may be configured (on a per-filesystem basis) to use "dump" or GNU tar as the program that does the actual data copying. This part of amanda runs on the host that's being backed up (generally; if you get involved in the SAMBA support, tat's a rather different matter), and sends the backup image to the amanda server (which spools the image to a "holding disk" for parallelism and to implement a speed-matching buffer); once the image has been written to the holding disk, that image is scheduled for copying to tape. Amanda uses UDP to accomplish the communication, and need not use the r* approach. I've been pretty happy with it so far. Additional information may be found at http://www.amanda.org/. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message