Hi All, Came across this thread, and all the replies were very helpful, had another question regarding DDB sealing.Why do we need to seal the DDB when using Cloud library ? And can we defer its execution as far back as possible ? Kind regards.

Why seal Cloud based DDBs?

Hello,

You don’t always have to seal the DDB when using a Cloud Library. What it really boils down to is whether the Storage supports Micro-pruning. See the documentation here for which providers and storage tiers support it - https://documentation.commvault.com/11.24/essential/9236_supported_cloud_storage_products.html

For more details on pruning and DDB sealing for Storage that does not support Micro pruning see here -

Let me know if you have any questions

Hello,

You don’t always have to seal the DDB when using a Cloud Library. What it really boils down to is whether the Storage supports Micro-pruning. See the documentation here for which providers and storage tiers support it - https://documentation.commvault.com/11.24/essential/9236_supported_cloud_storage_products.html

For more details on pruning and DDB sealing for Storage that does not support Micro pruning see here -

Let me know if you have any questions

Thanks a lot, Matt,

Our storage is a S3 Compatible Storage, and is listed under the link below :

So my guess is that our storage supports Micro-Pruning. Which also means, that we do not have to seal our DDB ?

Correct me if I am wrong.

Kind regards.

Confirmed, you do not have to regularly seal the DDB for S3 Compatible.

Thanks a lot @Matt Medvedeff for your guidance, much appreciated.