Test restore from Azure object storage

[mamosorre84]

Hi Fabian,

I understand the limitation for Azure Blob, and the unsupported option to give the ownership to the second VBR and then back to first VBR.

Is a config db restore a good/supported option ?

Which is the best option for a DR test and which for a real DR?

(Direct backup, Veeam 12.1)

Thanks

Marco S.

[Mildur]

Hi Marco

Configuration restore is a bad idea.
When the second backup server restores the configuration, it mistakenly considers itself as the primary backup server. It will initiate clean up sessions like background retention that will interfere with the objects in your Azure Blob container.

I would just use the unsupported workaround for now. It works, but it is unsupported because we haven't tested it against all scenarios it in our labs:
1) Make sure no job is running against this Azure Blob repository. Disable them to be sure.
2) connect your Azure blob to the second backup server
3) go back to the production backup server and click through the repository properties to get back ownership
4) Enable your backup jobs on the primary server
5) Start testing on the secondary backup server

Best,
Fabian

[mamosorre84]

Thank you Fabian, hadn't thought about that

[apolloxm]

Hello Fabian,

Did read-only work for Azure in the Veeam V12.2 or V12.3? Can you help to confirm this? or Do you have official document mention about how to do the disaster recovery from azure immutable blob storage. Thanks!

Hi Apollo

We will update the user guide with the limitation „read-only doesn‘t work for Azure“.
As discussed here and confirmed by our QA team, Azure cannot use read-only accounts. And connecting a repository from multiple backup server with write permission is not supported by us. We cannot document unsupported methods in our user guide.

Please use the unsupported steps Ivan posted earlier in this topic. It won‘t make it to the user guide, but it has proven itself workable for many customers.

[apolloxm]

Hello

Can someone help to confirm this?

[Mildur]

Hi Apollo

The limitation for Azure is still there: - General Considerations and Limitations

Consider the following:
This option is not supported for Microsoft Azure Storage and Veeam Data Cloud Vault.

But my answer for "Direct To Azure" repositories (while not officially supported) still works with v12.3: post518476.html#p518476
And for Azure in Capacity Tier, follow the approach with the maintenance mode.

Best,
Fabian

[gtelnet]

+1 for Veeam to make read-only keys work with Azure Blob and Veeam Data Vault. Thank you!