Veeam Vault replacing Virtual Data Domain

If I am understanding correctly, you have remote sites with source backup data that needs to be copied to a offsite location. 

This is what I was able to find. Regarding the cost line, you may want to reach out to your finance department to find out if they prefer to have more Capital Expenses (DataDomain+Hardware) or Operational Expenses (VDC Vault)

I would also recommend reaching out to a Veeam Service Provider, as they may have a solution even more tailored to your needs.

Hi Tommy

Thanks for the information
I was more looking for experiences.

In my lab I’ve integrated VDC Vault, and it’s pretty straight foward to get connected up. One thing to be aware of is backups going to vault need to be encrypted, so there is additional CPU overhead on your end to do that.

Remembering that VDC Vault is backed by Azure storage, what’s your connectivity like from your remote sites to Azure? Because this will be the limiting factor. If you’re running Data Domain (Virtual or Physical) at your remote sites and copying to a central data domain today, then you’re potentially getting some WAN optimization if you’re using native Data Domain mtree copying, which won’t be there if you’re copying to VDC Vault. On the other hand, if you’re backing up directly from a remote site to a central data domain, if the remote site is connecting directly to the Data Domain over DDBoost then again there is some source side dedupe optimization that happens thanks to DDBoost that won’t be present when backing up to VDC.

What sort of experience feedback are you looking for? Happy to share screenshots or the likes.