Partly an answer, partly a question for the group.  We have 2 masters
with 750gb and 400gb respectively.  The way we get around the catalogue
backups is to do a standard file system backup of /usr/openv/db/images/
for all client names except the master.  The master name is the only one
listed for a catalogue backup.

There are obviously some potential issues with this, image modification
during file system backup being one, but it was the best we could come
up with at the time.

Anyone have any other possibilities for enormous catalogues?

~JK

> -----Original Message-----
> From: vidit kohli [mailto:vidit_k AT hotmail DOT com]
> Sent: Monday, May 12, 2003 1:25 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] catalog size - largest
> 
> hello
> 
> Anyone  ruuning netbackup  catalog size = 150+ GB ? and How are you
> backing
> it up?
> 
> I just want to figure out whta maximun extend a catalog could grow
easily,
> 
> Ours is 135GB presently with 100% infinite retention and I'm backuping
it
> up
> using split script for images and others
> 
> cheers
> 
> vk
> 
> _________________________________________________________________
> MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
> http://join.msn.com/?page=features/virus
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu