I'm really confused as to how a company plans for VB&R storage.

If so, how does Server2012 dedup come into play when we are planning the physical storage for this? Will that yearly 5.34TB be deduped 50% (conservative estimate) and require that I have a minimum of 2.67TB of storage for a year just for GFS? Or will dedup do a better job on all these vbk's because they contain similar data? If I look at my repo for a particular job and see a size for my latest VBK, I can add up the restore points to keep, multiply by the size of the latest VBK and that will give me my GFS storage requirements?ĭoes it follow that for a year the GFS retention will equal 3+11+1*365GB/1024=5.34TB? And double that for 2 years? So, again in your case it will be 15 restore points, that is 7,5 TB for GFS. Looking forward to hearing from you and thank you for your support!įor GFS retention this is more simple, you simply count 500Gb and multiply it for the number of restore points, since all of them are fulls. I would have though Veeam have already done that but my searches are proving useless in this area. I would really like to write a program so I can input a few values in and it can calculate or estimate these storage requirements for me. The disk in the repo is either Windows dedup enabled or not How do I put all that together to know how much storage I will need available for 12 months, 24 months, 36 and so on? I have a VM, VeeamOne reports the change rate, VMWare tells me the VM size, I get to decide how many RP's I want to keep, the type of backup it will be and the archival retention. Is there a utility out there that one can use to determine how much space would be required over time in a backup-copy repo? What is the formula for any given scenario? All of the forum posts that I have read seem only intelligible to those who have asked their specific questions based on their specific configurations. I can't seem to find anything truly useful and I am surprised that I can't, especially considering how widely used this product is. I have been searching for the definitive way to calculate how much storage I need for backup copies.

R = number of rollbacks (or increments) according to retention policy (14 by default)ĭ = average amount of VM disk changes between cycles in percentĭata=11TB and will grow to 22TB in 3 years How many full backups wil I have? It's important to know to calculate the required disk space by using this formula:ĭata = sum of processed VMs size (actually used, not provisioned)Ĭ = average compression/dedupe ratio (depends on too many factors, compression and dedupe can be very high, but we use 50% – worst case)į = number of full backups in retention policy (1, unless backup mode with periodic fulls is used) We use Veeam 7, and thanks to the new backup copy job feature we can use GFS-rotation, but I'm wondering how many full backups the backup copy job will create in the folowing situation:

Calculator veeam