How to move backup image from hot tier to archive tier?

Hello @xiwen 

Thanks for the great question.

In short yes it is 100% supported but not recommended as per the following:

https://documentation.commvault.com/2023e/essential/9236_supported_cloud_storage_products.html

The way it will work is that CV will write the data as a specific storage class that is configured on the library and then Azure will go ahead and assign the life cycle and change that storage class if the data has not been accessed in X days.

If CV attempts to read that data it will try and find the class has changed and move the data back to the original storage class to enable it for reading.

When running dedup this can result in some surprise charges as you will have schedule validations and such that read a lot of the data resulting in movement of data you do not expect.

Due to this it is not recommended to use a Life Cycle Policy as it can cost a lot when mixed with deduplication as per the following:

https://documentation.commvault.com/2023e/essential/99623_supported_cloud_storage_features.html​​​​​

Instead the recommendation is to use the "Combined Storage Tier". The following goes into it in depth:

https://documentation.commvault.com/2023e/essential/139246_combined_storage_tier.html

Commvault's combined storage tier stores a small portion of the frequently accessed indexing and metadata in the warm tiers, while storing a major portion of the actual data in the cold tiers, to provide a simplified, cheaper, and quicker data recalls when needed. By placing frequently accessed indexing and metadata in warm tiers, a recall is as simple as a Browse and Restore operation.

Please advise if this answers all of your questions and helps.

Kind regards

Albert Williams