DDB Space Reclamation use case

Hi ​@PPC 

You can refer to this doc for space reclamation on cloud storage

https://documentation.commvault.com/2024e/expert/running_space_reclamation_operations_on_cloud_storage.html

Also you can check if your S3 compatible vendor is listed here

https://documentation.commvault.com/2024e/expert/supported_cloud_storage_s3_compatible_object_storage_vendors.html

sorry, that doesn’t answer my question. I have referred to all those documents already. I want to know how data aging is different from space reclamation for a cloud library and when should we run them?

Hi PPC,

the sparse support for disk libraries is used to carry out the mirco-pruning.

In the books online you will find the S3-vendors that support micro-pruning on S3. If micro-pruning is available for your S3 vendor your should have no need to run the space reclamation.

https://documentation.commvault.com/2024e/expert/configuring_micro_pruning.html

If micro-pruning is not available for your S3 vendor (or your type of S3 storage) you might need to think about space reclamation. S3 space reclamation is needed when you are not able to overwrite an existing S3-object. In this case you have to read the old object, extract the data that is still valid and write a new (smaller) object … and remove the old object. In this situation you gain some free space.

Please keep in mind

1.) that you have to read and write some amounts of data. This might lead to egress-costs, if the pruning MA is not located in the cloud.

2.) that you have to be able to delete the old object to gain some free space. In the case of an immutable S3 storage (object lock) or a glacier-type storage class this might not be possible. Therefore you would increase your storage comsumption by running a space reclamation form a storage perspective though Commvault uses lesser storage space.

I hope this helps.

Regards.

Michael

hi Michael, thanks for the explanation. Now ours, according to the document, do support micro pruning. 

then that means space reclamation is not required but like I said before, sometimes only after running space reclamation we are seeing the expected free space on the bucket even though data aging runs every day. 

I understand your statement - “S3 space reclamation is needed when you are not able to overwrite an existing S3-object. In this case you have to read the old object, extract the data that is still valid and write a new (smaller) object … and remove the old object. In this situation you gain some free space”

but i am wondering if that is the concept of micro pruning then why our environment responses better only after space reclamation

75% of the time space reclamation helps in a situation like where we manually delete some backup jobs in order to clean up storage. In situation like this where data gets deleted in unnatural ways does space reclamation work rather than data aging?

Hello PPC -

Can you tell me if you have space updates for cloud libraries enabled or disabled. I am curious if the scan phase is actually updating the volumes more than reclaiming any space. At some point in time, Commvault had the default disabled, however enabled is now our default.

https://documentation.commvault.com/2024e/essential/media_management_configuration_parameters.html

it is enabled