S3 governance mode

​@Michael.B this is already supported as this is a setting that is applied on bucket level. From a Commvault perspective the configure retention mode is something that it takes for Commvault granted.

Hi Onno

But what does this in the docs mean:
Commvault uses Compliance mode with object lock on S3 Compatible.
https://documentation.commvault.com/2024e/essential/configuring_worm_storage_lock_01.html

I created a test bucket with Object Lock enabled in Governance mode. In Commvault, I then created a WORM storage pool using this bucket.
When I check the properties of the items written to the bucket, their retention mode is set to Compliance.

Is it possible that I have misconfigured something?

No, you are right. I vastly misread something crucial. I have no idea why they do not offer an option to switch is to Governance mode. I would open a ticket and ask if there is an hidden key to unlock it and/or open a CMR to have this option added. 

Answer from support case:
 

Commvault does not support Governance Mode for S3 Object Lock. It supports Compliance Mode.
Unfortunately, there is no any additional or other setting or configuration to enable Governance Mode within Commvault currently.

Can I really be the first one with this requirement? Does no one use WORM, or is it just naively implemented with compliance lock?

I think one of the big drawbacks about enabling WORM in Commvault is the DDB Sealing combined with the 2.5x / 3x capacity requirements for storage.

Now, I believe Commvault partnership with certain vendors will allow you to choose between Compliance Mode or Governance Mode. An example is documented here https://www.dell.com/support/kbdoc/en-us/000218278/data-domain-ddboost-best-practices-and-media-agent-sizing-guidelines-for-commvault-v11 and here https://documentation.commvault.com/v11/essential/enabling_worm.html

You're absolutely right about the increased storage requirements when enabling WORM in Commvault -it's definitely something to consider carefully.

In our case, the bigger issue isn't just the 2.5x/3x capacity overhead, but rather the impact on DDB sealing. We're using Hyperscale X, and the SSD size is a limiting factor. 

We've already raised this with Commvault support, and unfortunately, there's no workaround at the moment. They’ve confirmed the limitation and opened a CMR.