Kind of a "best practice" or "common usage" query.

For those of you using vtapes, how have you chosen
to specify the size of a single vtape?

A while ago, perhaps 1-2 yrs when vtapes were starting
to be used more regularly, the comments seemed to be
"divide the available space by the number of vtapes".
This ensured that the file system would never run out
of space but meant that some available space is "wasted".

In contrast, when I 'played' with vtapes a year or more
earlier, I just specified a huge size, knowing it would
"never" be exceeded.  However a possibility was that I
would run the file system out of space if many vtapes
were pretty full.

Gene H., as I under stand it, uses a third variation.
He wants X number of vtapes and wants them pretty full.
To achieve this he adjusts the dumpcycle & runspercycle
parameters.

How are current users sizing their vtapes and what has
been their experience in disk usage?

 (: can you tell I'm thinking about using vtapes :)

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)