Forum Discussion

Heart_Beats's avatar
Heart_Beats
12 years ago
Solved

Netbackup Depuplication Storage Calculation

Hi All,

I am planning to implement Netbackup Deduplicaiton pool for Backups. Currently I have Netbackup 7.5 on Windows Server 2008 R2 SP1. I was taking backups on Advance Disk and tapes and now i want to go on Deduplication Storage. I want to calculate what Storage size is required for Deduplication, details of the backups are provided below:

Backup Type: Exchange Server 2007 DB, Policy Type: Full, Size of Full backup 450 GB, Frequency: Weekly, Retention 4 Weeks. I have another schedule for Exchange DB backup which is Incremental/Differential Backup, Frequency every 3 hours, Size per incremental/Diff backup 500 MB, Retention for this 2 weeks.

Now I want to know what is the total size of storage sapce i will need for this backup on MSDP? and what is the total size of space required on Tape for the same backup?

 

Thanks

 

Backup and Recovery
Best Practice
Case Study
NetBackup
Reporting
Windows Server (2003-2008)

4 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    12 years ago

    You have a Partner badge next to your name? 

    Speak to your local Symantec SE for latest dedupe calculator.

  • teiva-boy's avatar
    teiva-boy
    Level 6
    12 years ago

    Keep in mind the sizing you want for Exchange 2007 will be almost 2X larger when/if you upgrade to Exch2010.  Plan for the future, don't plan for today.

     

  • Omar_Villa's avatar
    Omar_Villa
    Level 6
    12 years ago

    Unfortunatelly the Deduplication calculator doesnt ask how much of the data you have is DB or Plain Files, this is the main mistake on Capacity Planing for Deduplication because all DB's dont dedup at all maybe a 1:2 or 1:1.5, meaning whatever  you have in size is what it will go in to your disk, for this cases I will recommend you to split your DB's and Plain Files Backups in to different Storage Locations, you can plan a large disk for you DB's and a smaller one for all your files, configure 2 different STU's and route your policies according to the data type, this way you will have plain of space on both sides and you will not mix capacities allowing you to plan better for the future because you will be able to know the real deduplication ratio.

     

    Hope this helps.

    Regards.