WORM storage lock

Hi ​@Leixim ,

PFB details for the queries posted.

 After the retention period expires, the object version can be overwritten or deleted. However, the worm storage will not allow deletion process until the retention period is completed for the associated policy.

Document for ref:  https://documentation.commvault.com/2022e/expert/configuring_worm_storage_mode_on_cloud_storage.html

 

For cloud platforms that support object-level retention, the Commvault software uses object-level locking. For other cloud platforms, Commvault uses bucket-level or container-level locking.

The expiration date for the read-only lock is set to match the data retention time established in the storage policy copies. These jobs cannot be modified or deleted by any user or application until the specified retention date. Once the retention expires, the system deletes the jobs as part of Data Aging.
Hence in this case the data will be removed only after the expiration.

3. Does Data Aging of Jobs work when WORM storage lock is enabled?
Yes, data aging job works as expected when worm storage lock is active.
 

4. Does Commvault check if AWS S3 Object Lock is really enable or I can just activate WORM storage lock on storage without object lock?

You can enable the compliance lock at the storage level, and all associated backup destination copies will be locked and protected.

I may just add, if you all of a sudden need to delete jobs that is not marked for pruning for a storage policy copy with WORM lock, you need to contact support. You will then receive a form that the product ovner needs to sign and return to support. Then you will receive a qscript that removes WORM for the specific copy.