Question : Formula to estimate how much space backups will consume

Hi! My organization is planning to implement DLO for the first time to backup windows xp and Windows 7 desktops and laptops. I am looking for some help on coming up with a formula to estimate how much space will backups consume (total storage space consumed) for the next 5 years.

We are using Netbackup DLO version 6.1MP5a. We plan to:
1) Store 2 revision on the filer,
2) Retention policy is 30 days
3) Using CDP to make changes after every 4 hours of a file being changed.
4) Initial size is 2.2GB
5) Average daily rate growth is 0.16%
6) Number of working days: 264
7) Number of users: 10,000

The formula I'm using to calculate storage space consumed on a yearly basis for is :
(Initial Size + (Average Daily growth * Initial Size * Revisions)* working days)) * number of users

The issue with this formula is that it doesn't take into account that older revisions will be deleted after 30 days

Answer : Formula to estimate how much space backups will consume

It's an easier problem than it seems, I think.   I've done similar spreadsheets to calculate data growth when using deduplication in virtual tape libraries.

What I would do for this is use your formula in a spreadsheet where I had one line for each day.
I would have columns for InitialSize (that day's starting size), GrowthToday, ChangeToday, and EndSize.

Each row would start at that day's InitialSize, multiply it by GrothRate to get GrowthToday, and by ChangeRate to get ChangeToday.  I then add the three together to get EndSize.    Today's EndSize becomes tomorrow's InitialSize.

Repeat 264 times.

Your required backup space on any given day will be today's EndSize plus the sum of the last 30 ChangeToday values.   Add some slack (such as for Leap Year, month-end close generating more data, unexpected data growth, etc.) and that should be your answer.

I've attached a spreadsheet with the above programmed in, for a single user with 2.2GB initial storage.  You can multiply the BackedUp column by NumberOfUsers to get an aggregate number.   You will have to figure your daily change rate.   .5% is not a bad first guess, but it depends on whether your application is doing byte-level differencing, or storing the entire changed file... especially when you're keeping a copy every four hours.

Random Solutions  
 
programming4us programming4us