Hello @Jass Gill 

Commvault does collect metadata from S3. We use the cURL API code and send GET requests.

Is there a specific “query” you are referring to? Or any issue you are seeing?

Thank you,
Collin

@Collin Harper  we have an issue where some directories are left behind on S3 storage post pruning (after retention expiration) which have objects inside them. Only some of them are left behind while major amount of Data does get pruned. We were wondering if this was anyhow related to metadata query API being enabled/disabled on that specific bucket.

Hello @Jass Gill 

It sounds more like DDB Baseline (unique data written for deduplocation). We don’t prune Baseline data even if it’s past retention. We only prune the data once all jobs referencing it have also aged. Since deduplication builds references off of written data to save space on future backups, we cannot prune the physical data until the jobs no longer reference it. You can refer to the link below for more information.

If you check SIDBPrune.log on the MediaAgent(s) associated to the Cloud Library, do you see any errors? Is S3 reporting a different amount of space consumed than Commvault is?

Optimize Storage Space Using Deduplication - https://documentation.commvault.com/2023e/expert/optimize_storage_space_using_deduplication.html

Thank you,

Collin