Skip to main content
Question

azure blob lifecycle management for Commvault backup

  • March 25, 2025
  • 1 reply
  • 18 views

Forum|alt.badge.img

Hello everyone,

In our backup environment, we have a CommServe and a Media Agent. We are currently using two policies:

  • Policy A: Basic retention of 35 days.
  • Policy B: Basic retention of 35 days, with extended retention: Monthly for 365 days and Yearly for 15 months.

Backup Targets:

  • Primary: Data Domain
  • Secondary: Auxiliary copy to Azure Blob (combined storage tier Cool /Archive ).

Since our data is on the Archive tier, restores are taking hours to rehydrate and restore. Therefore, we have decided to disable the combined storage tier and use container default (Cool).

We plan to change the storage class to Cool and retain only basic retention backups in the Cool tier. We want to move any extended retention data to the Archive tier. Is this possible using Azure Blob Storage lifecycle management? Additionally, once the data is moved to the Archive tier based on the lifecycle policy, will it impact the auxiliary copy? We use Deduplication with DASH enabled.

Thank you for your insights!

1 reply

Forum|alt.badge.img+3
  • Vaulter
  • 19 replies
  • April 2, 2025

Hi ​@syedameerdxc 

 

Moving data to the Archive tier based on a lifecycle policy can impact auxiliary copies when using Deduplication with DASH enabled. Lifecycle policies are not recommended for deduplicated data because they can archive all data, including jobs still within the retention period, which may interfere with auxiliary copy operations. It is advisable to create a separate auxiliary copy for data intended for the Archive tier to avoid potential issues.

Please let me know incase of any queries.

 

Regards,

Karthik


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings