Azure storage configuration for Commvault cloud library

  • 13 June 2022
  • 1 reply

Badge +8

We plan to enable WORM on current cloud library with below link, found we didn’t enable “version-level immutability support” when we created storage account


Q1, Microsoft confirmed they couldn’t enable “version-level immutability support” on exist storage account. I will create new one, Shall we enable other option under “Data Protection” when create storage account? 

For example: Enable software delete for blob, container, file, etc.

Or please guide me what is the best practice to create Azure storage account for Commvault cloud library.


Q2,  “Verify that the Storage Blob Data Contributor role is assigned in Azure.” 

How to understand the request? media server should has Contributor role for Azure storage account?


Q3, We enabled DDB on currently tape library, how to migrate backup image to new cloud library?


Q4, currently we configured one cloud library, one mount path for one container. What is best practice? shall we create more container or more storage account? 



Best answer by Collin Harper 13 June 2022, 16:52

View original

1 reply

Userlevel 5
Badge +14


  1. From my understanding we currently only support Bucket level immutability but we do have plans for object level immutability. For proper permissions you will need to have your Cloud Management Team verify the service account\role is configured correctly -
  2. Verifying Storage Blob Data Contributor role is something your Cloud Management Team would need to verify is configured for the service account\role.
  3. I responded to this on your other thread, but simply you can create an aux copy with the tape copy set as the source copy -
  4. I also responded to this on your other thread, but this is something we do not have recommendations or best practices on. This is based solely on your company’s design plans\requirements.