S3 Object Locking + Deduplication + Extended Retentions

Question

Hi guys,We are currently on the proccess of configuring WORM S3 Object Locking + Commvault 11.36 + Deduplication.The requirements is to enable WORM on the following JOBS:4 weekly Fulls24 monthy Fulls5 Yearly FullsThe thing is that we are not able (we dont know if we are doing something wrong) on applying Extended Retentions on Deduplicated S3 Object Lock Storage pools. (If we disable deduplication is posible to configure Extended Retentions).That means we have to have 3 different buckets 1 for each retention.If we sum the periodically sealing of DDB (yearly or less..) that means HUGE space needed with this configuration. Do you know if it’s possible to apply extended retention on deduplicated S3 object Lock configured Storage Pools?Thanks!!

sbhatia · Accepted Answer

Hi ​@gfcSince 11.36, when you use S3 Object Lock (WORM) with deduplication, you can’t apply Extended Retention on a single deduplicated storage pool. This is because enabling WORM on a deduplication-enabled pool switches pruning from micro-pruning to macro-pruning, which means Commvault has to keep all jobs in that backup cycle immutable until the very last job in the cycle hits its expiry. That automatically rules out the option of keeping just a few specific jobs for a longer period without holding on to the rest.What this ends up meaning in practice is that if you have different retention needs -say weekly, monthly, and yearly full backups - they can’t all sit in the same deduplicated WORM pool if you also want Extended Retention. You’ll need to create separate buckets or storage pools for each.You have rightly mentioned, the catch is that each of these has its own Deduplication Database (DDB), which will periodically get sealed based on your settings, and those seals will add to your overall storage usage over time.Note: Pre 11.36, it was possible to apply Extended Retention, although never recommended.

gfc · Answer

Thanks sbhatia for your response, all clear :)

Hi @gfc
Since 11.36, when you use S3 Object Lock (WORM) with deduplication, you can’t apply Extended Retention on a single deduplicated storage pool. This is because enabling WORM on a deduplication-enabled pool switches pruning from micro-pruning to macro-pruning, which means Commvault has to keep all jobs in that backup cycle immutable until the very last job in the cycle hits its expiry. That automatically rules out the option of keeping just a few specific jobs for a longer period without holding on to the rest.

What this ends up meaning in practice is that if you have different retention needs - say weekly, monthly, and yearly full backups - they can’t all sit in the same deduplicated WORM pool if you also want Extended Retention. You’ll need to create separate buckets or storage pools for each.

You have rightly mentioned, the catch is that each of these has its own Deduplication Database (DDB), which will periodically get sealed based on your settings, and those seals will add to your overall storage usage over time.

Note: Pre 11.36, it was possible to apply Extended Retention, although never recommended.

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded