Storage recommendation

[atta]

Hi,
It should be nice if someone can give a few tips about this. I want to know how much disk space on SAN should I leave if I gave 3.5 TB of data or 10 VM's. In DPM is 1,5 X total VM size. How about Veeam? What are recommendations (from real scenarios).

Best Regards

[foggy]

Atta, this is actually covered in the sticky FAQ topic:

Q: What are the typical data reduction ratios?
A: Compression and deduplication ratios up to 10x and more of the original size can be achieved, but this depends on too many factors, such as amount of VMs in the job, similarity of those VMs, content of virtual disks, etc.

As a rough estimation, you can use 50% data reduction ratio with default compression and dedupe levels.

[veremin]

What backup mode you're going to use? How many restore points you're going to store? Also, I assume 3.5 TB is the space consumed by 10 VMs, right? Thanks.

[atta]

I will use full + incremental. Yes those 10 VMs consumed 3,5 TB. So my question was how much should be available on SAN if I have 3,5 TB of data? I dont want to change this later coz this should be long-term (3 years if it's possible)

[atta]

For some servers I will have recovery point for every day.

[veremin]

So, you're going to specify 7 as the job retention period, right? Thanks.

[atta]

Yes, that is true? So how much should I have on SAN if I have 3,5 TB of data? Can you please help with this?

[veremin]

Assuming that you're going to run full backup on weekly basis, the number of restore points stored at each point in time will vary.

In your case, this number will be somewhere between 7 at 13 with two of restore points being full backup. For full backup you can use 50% as a data reduction ratio (compression + dedupe), because typically you won't see ratios less than that. So, the corresponding full backup should be approximately equal to 1.7 TB.

As to increments, they are equal to 5-10% size of full backup, depending mostly on amount of changes produced between backup cycles. For highly transactional VMs, such as Exchange, SQL, etc., the number can be up to 15-30% due to transaction logs activity.

Taking all of this numbers into account, you can roughly estimate the amount of space needed in your scenario.

Thanks.

[atta]

Okej, thank you for info. One more question. If we should replicate those 10 VMs to another server shall we use same method (mean here on storage calculation) when we taking backup or? We want to save replica 7 days.

[foggy]

Hyper-V replica restore points are stored as rollback files (.vrb), while full VM replica is a set of VM configuration files and virtual disks (native format).

[atta]

Okej, thank you for your help Foggy and Eremin

[yizhar]

Hi.

> I want to know how much disk space on SAN
Let's get it straight - are you planning to store your backups/replica on the same SAN device used for production?
Or is this a separate SAN device?
Please clarify.
If you're asking about the production SAN - then the answer is 0. You should store backups on different system and device.

Yizhar