Date: Thu, 12 Jun 1997 18:59:48 -0500 (CDT) From: "Jay D. Nelson" <jdn@qiv.com> To: Brandon Gillespie <brandon@ice.cold.org> Cc: Lyndon Nerenberg <lyndon@ve7tcp.ampr.org>, freebsd-questions@FreeBSD.ORG Subject: Re: dump/restore with compression Message-ID: <Pine.NEB.3.95.970612185619.378B-100000@acp.qiv.com> In-Reply-To: <Pine.NEB.3.95.970612153906.6204A-100000@ice.cold.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Use: dump 0uaf /dev/nrst0 /u1 ^ ---------------| That causes dump to write until EOT. -- Jay On Thu, 12 Jun 1997, Brandon Gillespie wrote: ->On Thu, 12 Jun 1997, Lyndon Nerenberg wrote: ->> ->> 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.) ->> -> ->Perhaps its how I'm executing dump, but when I run a tar of a filesystem, ->to tape, I can get the whole filesystem (without compression) but when I ->run dump, it asks for me to put in another tape without backing up the ->whole filesystem... I'm calling dump as: -> ->dump 0uf /dev/nrst0 /u1 -> ->-Brandon Gillespie ->
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.970612185619.378B-100000>