Restore from Azure Blob Storage to Azure VM

Morning 🙂

Absolutely, check this out: https://helpcenter.veeam.com/docs/backup/vsphere/restore_capacity_tier.html?ver=110

It calls out specifically you can restore from Capacity tier to Azure and has a wealth of links in there to talk you through steps and what to know!

thanks, I got here and stuck :( https://helpcenter.veeam.com/docs/vbazure/guide/vm_restore_wizard.html?ver=40

there are no VMs in protected data. How to import it from azure blob storage?

Hi, have you got Veeam Backup for Microsoft Azure deployed? As that’s the product you’ve just sent the step for. Just making sure we’re aligned here!

Yes I have and from there I’m trying to find a way to import backup from azure blob storage and restore vm 

Hi,

That wouldn’t be wise as you shouldn’t share blob storage between different products. You should deploy an Azure Proxy (https://helpcenter.veeam.com/docs/backup/vsphere/restore_azure_proxy_config.html?ver=110), and then attempt your backup restore via VBR using the restore to Azure option 🙂

I’m super confused right now :D

Maybe I will start from beginning.

on-premise : VBR with enterprise license, connected to hyper-v

cloud: azure

vm: windows 10

What I need is to send backups to azure and quickly restore them as azure vm in case of on-premise failure. Your last comment was helpful. Drove me to use Home→ Backups→ Object Store → restore to microsoft azure but I saw that “conversion” of VM causing download huge amount of data that usually, so I suppose that conversion is made on my PC. Why is that? Do I have to install VBR from marketplace in azure to perform all of the operation in cloud?

Hi,

Im guessing you either don’t have an Azure proxy configured within VBR or the permissions of your storage account the capacity tier is using prevent the Azure proxy from communicating with the storage account.

If you use an Azure proxy for the restore to azure feature, with azure blob storage as your source, whilst the orchestration will be conducted via VBR, your data will remain within Azure, with the Azure proxy creating the restored VM directly from the capacity tier storage account as the source 🙂

I just have configured azure proxy once more and even pointed the same storage account (with the LRS replication) where backup from VBR stays.

From the Log:

Restoring .vhdx (9GB): 1.1 GB restored  at 118MB/s - takes only 17 seconds (which I guess means there is read permission to my storage account).

but then “Performing conversion” takes almost 9 minutes and my WiFi monitoring tells me that something comes in and goes out :)

Thanks for the update.

The proxy should be doing the conversion in this case, as per: https://helpcenter.veeam.com/docs/backup/vsphere/restore_azure_hiw.html?ver=110

How much network traffic are you seeing? Unless you’ve got a 1Gbps connection then 118MBps makes sense as traffic flowing within Azure.

I’d expect to see some traffic, as I say, VBR is orchestrating the task, but the Azure Proxy should be doing the work.

At this point I would check your logs to see if there’s any references to failing over from the proxy due to XYZ missing permissions as an example.

Once I know how much traffic we’re roughly seeing (aka does it look like VBR is dealing with 1GB+ worth of traffic), and if the logs don’t indicate any type of failure of using the proxy, then I’d suggest a support case.

But feedback on the above please and we’ll go from there 🙂

I have noticed second point from the list

2.Veeam Backup & Replication converts disks of a backed-up workload to the VHD format and uploads converted disks to Blob storage in Microsoft Azure.

and have found log from this process and got proof that vhd file is mounted to C:\WINDOWS\TEMP\xxxxxx.vhd where all magic happens :)

It’s a bit ambiguous as the diagram shows the repository flowing data to the proxy, not to the VBR. But if you’re seeing the logs showing the VBR doing the conversion then it’s definitely taking place there I’d assume.

I’d raise a case with Veeam as there’s a discrepancy between the diagram and what you’re seeing, could be worth an investigation.