I went through this problem a while ago. Turns out that the DAT drives are
helical. This means that the *effective* length of the tape is calculated
based on the density of a helical stripe on the tape multiplied by the
number of stripes that fit on the tape.
[What the hell is he talking about?]
The practical solution is to run your dump with a tape length set to
something like 67000 meters. Maybe less for a 90 m tape, but that's the
sort of number I use for a 120. Sorry I don't have the exact number on me,
as my 'puter is at home.
--
----------Time flies like the wind. Fruit flies like a banana.----------------
--------Stranger things have happened but none stranger than this.-------------
Steven W. Orr [EMAIL PROTECTED] <site of former bang addr:-)>
---------------"Listen to me! We are all individuals."-------------------------
On Tue, 4 Jan 2000, Matthew Saltzman wrote:
=>Backup gurus-
=>
=>I was trying to use dump for a rudimentary backup with a 4mm DAT
=>drive. The drive capacity is 4-8G and the tape capacity is 2-4G (90
=>meters, I believe). I have about 1-2G to back up. But if I run dump
=>with the default settings, only a small amount of data is written
=>before dump requests a new volume.
=>
=>So my question is: What are the right settings for the dump parameters
=>-B (records), -b (blocksize), -d (density), and/or -s (feet) for this
=>configuration? (Also, am I correct in assuming that this has nothing
=>to do with the drive capacity and everything to do with the tape
=>capacity?)
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
