Dedupe Device - Existing Backups to Cloud - Case# 03435343

[clifton]

I am new to the cloud idea and I am playing with scenarios now. I know I can create new backup jobs to go to a new performance tier repository and then connect the performance tier repository to a cloud blob container. But, what actually happens to the existing backups as they are being pushed to the cloud? Specifically, our data on the DataDomain is backed up in non-dedupe backups because the DataDomain does hardware deduping on its own. My understanding is that those non-deduped backups will be pushed as it, non-deduped, to the cloud. So, is there a way to get the already existing non-deduped, non-compressed backup on the DataDomain into a Veeam-compressed backup to put in the cloud? Maybe a conversion program that takes a 30 day old non-deduped or compressed backup, compresses it with Veeam dedupe and compression, and then moves that backup to the cloud? Thanks.

We are using Veeam B&R 9.5.4 and Microsoft Azure blog storage.

[Gostev]

Hi, Clifton - our object storage integration already works the way you want it to work, natively. Thanks!
"get the already existing non-deduped, non-compressed backup on the DataDomain into a Veeam-compressed backup to put in the cloud"

[clifton]

So, you are saying that Veeam should automatically dedupe and compress the backup that was not deduped or compressed at the time of backup and then upload it to my Azure blob?

[Gostev]

That is correct.

[clifton]

Thank you very much. I will proceed with that then.

[Kaiutin]

I have the same exact scenario. Is there a way to configure the compression and or deduplication ratio when offloading the backups to Azure? I would assume these setting would be configured in the SOBR Offload jobs if there is a way to configure these.

[veremin]

The default compression level is used, and you cannot change it anyhow. Thanks!