Skip to main content
  • EN

Hello,

I have a question regarding how Veeam uploads backup files to Azure Blob Storage, and I’m a bit confused by the behavior. I believe the documentation might not be fully accurate or clear on this point.

Here’s the scenario:

  1. I created an Azure Storage Account and set the default access tier to Hot.

  2. I also created a container inside that storage account.

  3. On the Veeam side, I configured an Azure object storage repository, and I left the "Use cool blob storage tier (may result in higher cost)" checkbox unchecked.

    Use cool blob storage tier

     

My First question is: In this case, what access tier does Veeam use when uploading backup files to the container? Will the backups be uploaded with the Hot tier (as per the storage account default), or does Veeam explicitly set a tier regardless of the default?
My Second question is: same scenario but with default access tier (Azure Side) set to Cool.
My Third question is: same scenario but with default access tier (Azure Side) set to Cold.

You’re right, the documentation doesn’t seems to say which will take precedence in such a scenario. However, I would assume that whatever is specified in the Veeam console will override the default access tier configured on the container. I believe Veeam writes each blob and sets the tier on that blob at the same time.

Regarding the cold access tier, this would only be possible for repositories you added as an Archive Tier in a Scale-Out Backup Repository.

 

Hi,

 

These scenarios are actually within the documentation:

https://helpcenter.veeam.com/docs/backup/vsphere/azure_storage_details.html?ver=120
 

If you plan to access your backup data infrequently, select the Use cool blob storage tier (may result in higher cost) check box. Veeam Backup & Replicationwill keep blobs in the cool access tier.

IMPORTANT

Consider the following:

  • If you do not enable the cool access tier option, Veeam Backup & Replication will use the hot access tier.
  • If you specify the cold tier in the Azure storage account settings, Veeam Backup & Replication will ignore this setting and will use the hot access tier.

Hi,

 

These scenarios are actually within the documentation:

https://helpcenter.veeam.com/docs/backup/vsphere/azure_storage_details.html?ver=120
 

If you plan to access your backup data infrequently, select the Use cool blob storage tier (may result in higher cost) check box. Veeam Backup & Replicationwill keep blobs in the cool access tier.

IMPORTANT

Consider the following:

  • If you do not enable the cool access tier option, Veeam Backup & Replication will use the hot access tier.
  • If you specify the cold tier in the Azure storage account settings, Veeam Backup & Replication will ignore this setting and will use the hot access tier.

 Ahh, I wasn’t able to find it in the documentation (I wasn’t looking within the configuration instructions, just the backup infrastructure components.), but my assumption appears to have been correct that the Veeam setting takes precedence.

 Regarding the cold access tier, this would only be possible for repositories you added as an Archive Tier in a Scale-Out Backup Repository.

 

Yes on the veeam side but think also in the azure side what if I set the default access tier to Cold 

 Regarding the cold access tier, this would only be possible for repositories you added as an Archive Tier in a Scale-Out Backup Repository.

 

Yes on the veeam side but think also in the azure side what if I set the default access tier to Cold 

Veeam would ignore whatever default you set on the azure side, and use whatever setting is configured in Veeam. 

Hi,

 

These scenarios are actually within the documentation:

https://helpcenter.veeam.com/docs/backup/vsphere/azure_storage_details.html?ver=120
 

If you plan to access your backup data infrequently, select the Use cool blob storage tier (may result in higher cost) check box. Veeam Backup & Replicationwill keep blobs in the cool access tier.

IMPORTANT

Consider the following:

  • If you do not enable the cool access tier option, Veeam Backup & Replication will use the hot access tier.
  • If you specify the cold tier in the Azure storage account settings, Veeam Backup & Replication will ignore this setting and will use the hot access tier.

I am aware of that in the documentation, I am asking if someone had the Chance to test those scenarios, we need to think of 2 separate things here: what is the default access tier on azure side and what is the available option on Veeam object storage repository 

According to that Reddit discussion the behavior mentioned in the documentation is not correct: https://www.reddit.com/r/Veeam/s/STj7yIVUg2

 Regarding the cold access tier, this would only be possible for repositories you added as an Archive Tier in a Scale-Out Backup Repository.

 

Yes on the veeam side but think also in the azure side what if I set the default access tier to Cold 

Veeam would ignore whatever default you set on the azure side, and use whatever setting is configured in Veeam. 

According to the documentation yes, but it that really what happens? 

Refere to that Reddit post: https://www.reddit.com/r/Veeam/s/STj7yIVUg2

Hi,

 

These scenarios are actually within the documentation:

https://helpcenter.veeam.com/docs/backup/vsphere/azure_storage_details.html?ver=120
 

If you plan to access your backup data infrequently, select the Use cool blob storage tier (may result in higher cost) check box. Veeam Backup & Replicationwill keep blobs in the cool access tier.

IMPORTANT

Consider the following:

  • If you do not enable the cool access tier option, Veeam Backup & Replication will use the hot access tier.
  • If you specify the cold tier in the Azure storage account settings, Veeam Backup & Replication will ignore this setting and will use the hot access tier.

I am aware of that in the documentation, I am asking if someone had the Chance to test those scenarios, we need to think of 2 separate things here: what is the default access tier on azure side and what is the available option on Veeam object storage repository 

According to that Reddit discussion the behavior mentioned in the documentation is not correct: https://www.reddit.com/r/Veeam/s/STj7yIVUg2

Hi this was referring to an older version of the documentation and you can see the final comments are saying the same thing I’ve said as the documentation has been updated.

Comment


Terms & Conditions