Hello,

Question for you all:

Has anyone had any troubles with the netbackup database size getting out
of hand and creating excessively bad performance issues?  Has anyone come
up with any intuitive solutions for how to solve this problem?

With 13TBs of data being backed up every week, our netbackup db/images
directory has grown to obscene sizes (60GB of flat-file data compressed).

Because netbackup doesn't use a real database to hold this information
(simple flatfiles..) the scalability of this design is rather weak..

these huge flatfile databases are causing us major performance problems
when trying to do simple restores..  the simple act of looking for a
single file can take several hours to complete as it chugs through all of
it's backups files.

we've indexed everything, but that doesn't seem to help..

I've heard there are tools to dump this information into an actual SQL
database which could be an extremely useful tool for hunting down the
backups for specific files..

has anyone done this?  we were thinking of possible dumping the data once
a day into a database for doing quick searches on..

I'd be curious to hear if anyone else has run into these performance
problems..

Jon


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Walt Disney Feature Animation      The Secret Lab
Senior Systems Engineer              818.526.3051
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=