you're right on both counts:

(1) bpbackupdb doesn't report how many kbytes it's writing, the best 
way to estimate that figure that is just looking to see how much 
space is occupied by /usr/openv/netbackup/db on your master server.

(2) the question of "how big can my catalog get before it will no 
longer fit on one dlt7000 tape?" relies heavily on how well that 
dlt7k compresses your catalog data.  I don't have a sample answer to 
give you from personal experience, but it wouldn't be too tough for 
you to get a crude estimate:

   -use "du -sk" to find a ~5 GB subdirectory under netbackup/db/images
   -manually mount a scratch tape (make sure to DOWN the drive...)
   -run a script that repeatedly does a "tar cf" of that dir to that tape
   -see how many times the tar runs before hitting the EOM

HTH
rob


At 2:48 PM -0800 2/19/03, Liddle, Stuart wrote:
>I need a way to find out how much data is actually being written to our
>catalog tape.  I used the following:
>
>bpbackupdb -v
>
>and looked at the /usr/openv/netbackup/logs/admin/log.<date> file
>
>It did not have the total number of bytes written to the tape anywhere in
>the output.  I'd like to know how close I'm getting to filling my catalog
>tape.
>
>Is there an easy way to determine this information, or do I have to just
>guess that since the data in the
>
>/usr/openv/netbackup/db
>
>directory is mostly text that it will get at least a 2:1 compression
>(probably closer to 4:1) and use that as a guide for how much will fit on my
>DLT7000 tapes?  Since the hardware compression will get about 70GB of
>compressed data on a tape, what's the realistic amount to expect that will
>fit on the tape?  Would I have to worry if my db directory is about 50GB?
>100GB?
>
>thanks,
>
>--stuart
>_________________________
>Stuart W. Liddle
>Amgen Corp.
>liddles AT amgen DOT com
>
>
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu