NBU Catalog Sizing 1

[cdpwin12]

I have to justify why I think the NBU catalog needs to be moved to a larger LUN and I attempted the calculation Veritas provides and it is way off. Anyone know of any good ones to use or did I possible miss something?

Veritas capacity planning:
Size of full= ###GB * backup_jobs_per_month * ret_n_months
Size of incr= ###GB * backup_jobs_per_month * ret_n_months
Total_of_two * 2% = ###GB --> estimated catalog size

I also allowed *4% for compression and my number was 100's of GB larger then it actually is now. I gathered this data for one months worth of data.

 

[Vela]

You need to justify why you need more Netbackup Catalog space? Is this a Windows master?

Beside's going 100% full on /usr/openv/ and possibly corrupting the database? That's one justification-

Next you should find out how much more you've backed up this month compared to last month. One way to do this is take the media written report-and copy that output to clipboard. Then paste it into excel. You can then total the KB written and turn it into a decimal # to get the amount of data written to tape that month.

How much diskspace are you currently using for your netbackup catalog? Do you have infinity retention backup's?

 

[cdpwin12]

I let them know what could happen if it filled up, they wanted me to "clean it up". Got to love the politics.

It is a solaris master currently it has 100GB and we are approaching 92-94GB used. We do not have any infinite retention however I convinced them to purchase NBU Vault option since starting so we can duplicate everything backed up to DSU’s and the VTL. Since this has started the catalog size has gone up nearly 10%. It’s amazing how much tier 1 data was not being sent offsite.