We have configured WORM storage lock for NetApp storage Grid bucket. As per documentation, the lifecycle policies need to be configured on storage end to remove delete markers from versioning.We have retention for 30 days.
Now the questions
->lifecycle rule to delete non-current versions after how many days ?
->Doesn’t commvault clear the versioned objects after the retention period is completed ?
->As per documentation, it was mention Deleteobjectversion permission is needed for Access keys.Does it means Commvault will auto delete the versioned objects after retention ?
For a bucket with versioning enabled, you must have the DeleteObjectVersion permission to delete versioned objects.
S3 Compatible
Same tasks as Amazon S3
Commvault uses Compliance mode with object lock on S3 Compatible.
Disable default retention when object lock is enabled or set retention days to 0.
Additionally, you should configure life cycle policy to remove delete markers.
The lifecycle rule for deleting non-current versions should be configured based on your retention requirements. Since you have a retention period of 30 days, you might consider setting the lifecycle rule to delete non-current versions shortly after this period, such as 31 days, to ensure compliance with your retention policy.
Commvault Clearing Versioned Objects:
Commvault does not automatically delete versioned objects after the retention period. The lifecycle policy on the storage side is necessary to manage the deletion of non-current versions and delete markers. This is because Commvault relies on the storage system's lifecycle policies to handle versioned objects.
DeleteObjectVersion Permission:
The DeleteObjectVersion permission is required for Commvault to delete versioned objects. This permission allows Commvault to manage the deletion of objects in a versioned bucket, but the actual deletion process is governed by the lifecycle policies configured on the storage system.
The lifecycle rule for deleting non-current versions should be configured based on your retention requirements. Since you have a retention period of 30 days, you might consider setting the lifecycle rule to delete non-current versions shortly after this period, such as 31 days, to ensure compliance with your retention policy.
Commvault Clearing Versioned Objects:
Commvault does not automatically delete versioned objects after the retention period. The lifecycle policy on the storage side is necessary to manage the deletion of non-current versions and delete markers. This is because Commvault relies on the storage system's lifecycle policies to handle versioned objects.
DeleteObjectVersion Permission:
The DeleteObjectVersion permission is required for Commvault to delete versioned objects. This permission allows Commvault to manage the deletion of objects in a versioned bucket, but the actual deletion process is governed by the lifecycle policies configured on the storage system.
