De-duplication Veeam Backup

[monkeymagic79]

All

I wonder if anyone can answer my question, I was watching a training video online regarding Backup and Replication and it mentioned Veeam's backup deduplication methods. Now in order to get the best de-duplication should I be grouping servers of similar OS/role into one job or have I got the wrong end of the stick.

Many thanks

[tfloor]

Yes you are right. You can group vms from the Same os or template to get a better dedup ratio

[bbricker]

Not to hijack, but I was just about to post on the same topic, so I'm glad I saw this thread.

Is there any preference with VB&R for how the vm's vmdk disks are set? Does it matter if it's Thin or of it's Thick? (Lazy Zeroed or Eager Zeroed)?

Any other best practices to get the best deduplication?

[monkeymagic79]

Ok thats good currently we had multiple jobs backing up one VM at a time so essentially not getting any de-dupe, so I will now go away and group servers into backup jobs to get de-duplication. Am I right?

[J1mbo]

Yes.

[monkeymagic79]

As bbricker said earlier anyone know of any best practices regarding this i.e. better to group same OS accross the estate

[J1mbo]

The best ratios will be achieved with the most duplication within the job (the job is the dedupe database boundary). So if you had (say) two file servers with identical contents (for whatever reason) then backing up the second would be almost free in disk space terms on the Veeam server.

So if there is little duplication of data within the estate, then grouping by OS could be best, especially if many VMs are the same patch level, since de-dupe of the OS itself would be possible.

Hope that helps.

[monkeymagic79]

Thanks j1mbo much appreciated

[Vitaliy S.]

Is there any preference with VB&R for how the vm's vmdk disks are set? Does it matter if it's Thin or of it's Thick? (Lazy Zeroed or Eager Zeroed)?

I don't believe there is a difference between deduplication ratios for thin and thick disks, both types will dedupe equally well.