From owner-freebsd-questions Mon Jan 15 6:52:28 2001 Delivered-To: freebsd-questions@freebsd.org Received: from clmboh1-smtp2.columbus.rr.com (clmboh1-smtp2.columbus.rr.com [65.24.0.111]) by hub.freebsd.org (Postfix) with ESMTP id 937CF37B698 for ; Mon, 15 Jan 2001 06:52:09 -0800 (PST) Received: from mail.iowna.com (dhcp065-024-023-038.columbus.rr.com [65.24.23.38]) by clmboh1-smtp2.columbus.rr.com (8.11.2/8.11.2) with ESMTP id f0FEnpp19131; Mon, 15 Jan 2001 09:49:52 -0500 (EST) Message-ID: <3A630DD2.26136B9@mail.iowna.com> Date: Mon, 15 Jan 2001 09:48:50 -0500 From: Bill Moran X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dave VanAuken Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Poor mans backup solution required References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dave VanAuken wrote: > Any recommendations for perhaps tar-ing the directory tree to a second > IDE drive each night, or other solutions involving the cost of adding > another $100 IDE drive. Sounds like you've answered your own question. We've even considered making a "backup server" on our network that would be used HW (old P90 or something with 16 or 32M RAM) except for a new, big HDD and just tar important stuff to an NFS share on a regular basis. A second HDD wouldn't be a bad idea either, you could even have a backup script that mounts the filesystem, does the backup and then unmounts the filesystem to keep anyone from inadvertantly messing with it. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message