I have a customer running 11.40 and Commvault now has the combo tiers for cloud storage configured by default. My question resides in which tier the bucket should be created. The customer had previously created a bucket in AWS (this may come into play later) that was used to create a Cloud Library in Commvault using the AWS Glacier Deep Archive tier. When examining the data in the bucket, we can see the CHUNK data is written to Glacier Deep Archive however, the index metadata is showing under Glacier Instant Retrieval. This seems wrong to me.
I have read that Commvault will apply an Amazon storage class header to every upload API call and then writes the data to the bucket, which is part of what is allowing the CHUNK data to be written to one tier with the index metadata to another tier. I’m starting to believe that the storage class header only is being applied to the CHUNK data and the metadata is using whichever storage tier the AWS S3 bucket was created with. Documentation doesn’t make it clear (or I’m misunderstanding it) when the bucket should be created, nor which tier should be selected when talking about combo-tiers.
- Is Glacier Instant Retrieval an expected tier when using the combined storage tier? (My assumption is no)
- Does the AWS S3 bucket need to be created with the tier set to where the index metadata should be written to? (ie S3 Standard-IA)
- Is the behavior discussed above due to the bucket being created within AWS targeting Glacier Instant Retrieval and then using Commvault to create the Cloud Library pointing to Glacier Deep Archive? (this is my assumption)
Thank you in advance.
