Hi community,
we recently deleted a deduplicated storage pool which was using a S3 bucket on our NetApp Storage Grid and had WORM/object lock enabled.
This was nearly a week ago and we still see almost no space beeing cleared on the bucket.
We are seeing delete markers being set (sometimes even multiple for some reason) but older versions with actual data are not being deleted.
Also Commvault is still issuing S3 delete commands to the storage and the delete marker count is already higher than the count of actual object versions which seems weird.
We noticed a recommendation to set up a lifecycle policy on the storage to delete non-current-versions which we did and now is clearing up some more space than before but still very slowly, but this is more of a storage side issue.
Source: Configuring WORM Storage Lock
We noticed correct deletion behaviour (physical pruning) in the past on other active storage pools with S3 object lock so my question is:
Is it necessary to set up these lifecycle policies or not (especially for or NetApp Storage Grid)?
Would there be no physical pruning besides the delete markers otherwise?
Also we would be interested to know why Commvault is issuing multiple delete requests for the same object. Is this expected behaviour?
We are currently on 11.40.42
Thanks in advance!
