Veeam How To Add Azure Capacity and Archive Tier Object Storage

Veeam How To Add Azure Capacity and Archive Tier Object Storage

Adding Capacity and Archive Tier Azure storage to Veeam via Object Storage Repositories has a few extra steps, then some of the competitors.

I’ll be adding Veeam KB’s and try to update this if and when permissions change on Azure side. Or if pre-requisites change.

Adding Microsoft Azure Blob Storage, Microsoft Azure Archive Storage

Considerations and Limitations

Microsoft Azure Storage Accounts

Go Into Azure, and create a new storage account. Or use an existing one.

Most of the default options are fine.

Disable All soft Delete Options

The reason we want to disable soft delete, and not have versioning enabled / object lock enabled.

Next lets touch on permissions

Azure Object Storage Permissions

Creating Custom Role for Azure Account

Create a Custom role, for Storage account if It does not have the required permissions. Or If you want to give an existing user access. Also if you want to add Azure Archive Tier in the future.

Add by JSON file. Be sure to edit Role Name, Description, and Subscription information before uploading.

Assign the new role to User/Users

Create a Container for Capacity Tier Storage.

Create Container for Archive Tier

In Veeam add your Azure Storage Account

Storage Keys can be found here

The service account, should only require Contributor role. But to be on the safe side, I would create custom roles for each of the KB’s and assign to required users. A Compute account will be required to spin up a proxy appliance if using Archive Tier.

Azure Service Account Permissions

Azure Repository Account Permissions

Go ahead and create your Object Storage Repositories for Capacity Tier, and Archive Tier.

Once those are created, create your Scale-Out Backup Repository.

I’ll come back and clean this up.

Comments are closed.