The master size can become an issue.  At around 20GB, it can take an
hour or so to backup (or restore), and during that time no backups can
be initiated.   When it gets to the point where it will no longer fit
on a single tape, you have to add a second step to the database backup
process.  

The layout of the "database" is just a hierarchy of files.  There are
of course a few which are critical in that they affect the whole
system, but the vast majority (both in size and number) have no
dependence on each other.  They're just files, and if one gets dinged
you can restore it from backup, or scan the tape, etc.

You've got a long time before you have anything to worry about.
Personally, I'd take some time to walk through the DR process (chap 5,
troubleshooting guide) and make sure your catalog backups are
configured correctly and restorable, and document the process in your
own words.

chad.haywood AT storability DOT com writes:
> Hi,
> 
> As someone familiar with Legato Networker 5.x index stability issues, I 
> was concerned to learn that a Netbackup 3.4 master server I recently 
> assumed responsibility for has a master server catalog size of 1.6 Gig due 
> to NFS mounted backups.   In a Networker environment I would have made 
> shrinking this a major priority to avoid likely headaches should a DR 
> situation arise.  From those of you with more Netbackup experience, is the 
> master catalog size a major issue in a DR situation?  Obviously it will 
> impact the time needed to recover the master's catalog, but how likely is 
> it to cause difficult to resolve issues due to corruption or other 
> problems?
> 
> Thanks,
> Chad
> 
> Chad Haywood
> Senior Solutions Engineer
> Storability, Incorporated
> www.storability.com
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-- 
Larry Kingery 
                 It's not if, it's when and how hard