From owner-freebsd-questions Thu Jun 12 13:32:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA19245 for questions-outgoing; Thu, 12 Jun 1997 13:32:34 -0700 (PDT) Received: from ve7tcp.ampr.org (root@ve7tcp.ampr.org [198.161.92.132]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA19240 for ; Thu, 12 Jun 1997 13:32:31 -0700 (PDT) Received: from localhost.ampr.org (lyndon@localhost.ampr.org [127.0.0.1]) by ve7tcp.ampr.org (8.8.5/8.8.5) with SMTP id OAA01000; Thu, 12 Jun 1997 14:31:35 -0600 (MDT) Message-Id: <199706122031.OAA01000@ve7tcp.ampr.org> X-Authentication-Warning: ve7tcp.ampr.org: lyndon@localhost.ampr.org [127.0.0.1] didn't use HELO protocol To: Brandon Gillespie cc: freebsd-questions@freebsd.org Subject: Re: dump/restore with compression In-reply-to: Your message of "Thu, 12 Jun 1997 13:40:51 MDT." Date: Thu, 12 Jun 1997 14:31:35 -0600 From: Lyndon Nerenberg Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ -hackers dropped ... ] One option (it's a bit heavyweight I'll admit) is to install amanda and use it to run the backups. It can compress the dump sets on the way to the tape if you like. In my case, I never compress backups. If you get a single I/O error on a tape, you have almost no hope of retrieving any data stored beyond the error. Uncompressed backups in dump format can handle and recover from this. (Compression done in the tape drive includes a *lot* of redundent information to help handle recovery from bad media situations.) --lyndon