Dedupe on backup servers using VDO
VDO is now supported as a production feature as of RHEL 7.5. Including it in the cloudboot images would provide native filesystem level dedupe for backup servers, which is a feature that's desperately needed. As VMs are built of a small set of templates, dedupe of the vdisks should have a huge effect on storage requirements. Can you please look at including VDO support in 6.0 LTS.
AdminRoman Strazhnyk
(Product Manager, OnApp)
shared this idea
I have discussed this one with our investigations team. While we see several enhancements with this feature we think that the drawbacks are more serious so we are not consider implementing this features.
We might change our minds later.
We can configure VDO on new backup servers as part of our PS services.
3 comments
-
david.hughes
commented
You do not have incremental backups for windows VMs. So without dedup there is no reasonable way to handle a decent rotation period without building out a huge amount of backend storage.
Telling our customers to add a host based solution like R1 is not an acceptable solution for an IAAS offering. They want block level backups handled by their hosting provider. Adding dedup is at least some help. We use VDO for other applications and will be implementing it ourselves on our new OnApp backup servers. It'd be nice to see it supported because the current backup functionality is really very primitive.
-
steven
commented
I would like this feature in onapp storage for deduplication for storage of VMs disks
-
We have incremental backups and backup plugins that reduce backup space consumption and extend functionality. In the case when only vdo and kmod-kvdo need to be added to cloudboot images then we can add this in off the upcoming releases. In other cases we would like to hear more feedback regarding the implementation and management of VDO Volumes.