Ed,

I know the general rules, but... Another challenge for me is to estimate 
disk space for NetBackup catalog where total amount of data under 
NetBackup protection is 3.6 PB (peta bytes) with ability to grow to 8.5 
PB in the future.

The difference between 1% and 2% of total amount of protected data for 
catalog does matter. The difference vary from 36 TB to 85 TB in case of 
1% difference. I need to be more precise. If I will say to my customer 
that they have to buy 255 TB (3% of total amount of data in the future) 
for NetBackup catalog, I have to be 100% sure what I'm talking about.

I called Symantec and with that big data volume they are not 100% sure 
about space size for NetBackup catalog.

In this case "size" does matter ;-) Small mistake can cost a lot of money.

regards,

Darek

Ed Wilts wrote:
> On Fri, Mar 28, 2008 at 3:52 AM, Dariusz Klar <Dariusz.Klar AT sun DOT com 
> <mailto:Dariusz.Klar AT sun DOT com>> wrote:
>
>     Recently I noticed that indexes are consuming a lot of disk space.
>     Does
>     anyone know the rule, how to plan space for indexes? Looks like
>     something has changed since older versions of NetBackup.
>
>  
> I don't think anything has changed.  The challenge in planning is that 
> the catalog size is based on number of files you're backing up, not 
> the size of the files.  If you back up a lot of small files, your 
> catalog will be much larger than the site that backs up the same 
> amount of disk space containint large databases.  The longer the 
> retentions, the more likely it is that you'll need a larger catalog 
> for backing up the same amount of disk space.
>  
> The golden rule to remember is to never, ever fill your catalog disk.  
> Use a different file system for your logs since they're the most 
> likely thing to fill the disk.
>  

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu