Restoring from Azure blob/storage container to Hyper V Host C: Drive.
Restoring from Azure blob/storage container to Hyper V Host - 8/2/2024 1:44:20 PM Error Restore job failed Error: Failed to create planned VM configuration (path: 'E:\VeeamRestored\Virtual Machines\9469f15z-4723-4eea-83a3-13f4816bc1d4.vmcx'). Job failed ('Failed to import a virtual machine. The Hyper-V Virtual Machine Management service encountered an unexpected error: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).'). Error code: '32768'.
Any insight would be appreciated.
Page 1 / 1
Seems like it is a permission related issue based on the message you posted. This may require a deeper look at the logs with support.
From the above, it looks like if you attempt to restore from Azure archive repositories (i.e. Blob), you can only restore back to Azure, not Hyper-V.
Hi @coolsport00 WOW is that for real, am i reading correctly?
This is my frist time doing a restore from Azure. But you are telling me that this is an actual limitation. Only Azure to Azure restoration is allowed/available.
It appears that way....from the archive Repos...yes. You could contact Support to verify.
Hi @coolsport00
Yes they just confirmed, very sad news. So basically only local to local repo restoration allowed and azure to azure repo restoration basically. I wonder if this is just an Azure limitation explicitly, I wonder if AWS and other cloud platforms allows restoration from restoration to back to hyper v. Some interesting stuff.
Hi SysEng
May I ask a question? Are you attempting to restore an Azure VM protected by Veeam Backup for Azure to a HyperV host?
Or have you created backups of HyperV VMs and uploaded them to Azure Blob directly or a SOBR Capacity/Archive Tier on Azure Blob?
Something tells me you have backups of HyperV VMs and now you want to restore them back to HyperV. Which is possible from the capacity or archive tier on Azure Blob.
