Skip to main content

Hello All.

I’m a bit confuse about the DDB usage on Cloud Archive storage. From the Cloud Storage Building Block documentation…

https://documentation.commvault.com/2022e/essential/139246_combined_storage_tier.html

https://documentation.commvault.com/2022e/essential/139247_archive_storage_tier.html

...we can see Deduped and non-deduped are allowed. But from the Cloud Storage Best Practices it is strongly not recommended:

DDB Backup on Cloud

Make sure that the cloud storage library does not have an Archive Object Storage class selected. DDB backups are not recommended on Archive Object Storage, like S3 Glacier/Deep Archive, Azure Archive and Oracle Archive.

What are the reasons behind this strong recommendation?

Tks in advance guys.

Eddiie

Hi @Eddiie 

My guess is that Glacier type storage needs time to retreive data, thus not allowing for data aging as you would want to on a “disk” library.

If you use a normal bucket then you will be fine using deduplication, keep an eye out for the block size though. 128 KB when non cloud targets as previous storage policy copies are involved and 512 KB for cloud storage only situations.

Hi @Eddiie , If the question is specifically for DDB backup then the reason is that in case of corruption, the DDB itself needs to be reconstructed. The reconstruction of the DDB needs the DDB Backup which is restored and then brought up to the current state. Hence the recommendation.

Hope that helps.

 

Deduped backups vs DDB backup are 2 different things. 

 

DDB backup is referred to protecting dedupe database files where as deduped backups refers to actual data backups (File system, databases, VMs...etc) using deduplication.

 

Archive storage is supported for deduped backups but not recommended for using it for DDB backups since these DDB backups are very short lived so it’s unnecessary to put them on the archive storage. 

Tks for the insights, guys.

Cheers.

Eddiie

Reply


Terms & ConditionsCookie settings