Hi all,
I'm not looking for technical support at this point, I just want to know if this is possible/supported.
Our existing production system is on prem vsphere 8, backing up via Veeam v13 Windows, using a scale out repository. This uses Wasabi as the capacity tier.
As part of our DR plan, we use a Veeam 13 Windows VM running in Azure to import backups from Wasabi, then restore VM's to Azure.
We're looking at Proxmox due to the large license cost increase with vmware/broadcom.
My question is, should the same process still work, replacing vmware with proxmox?
So backup a Windows VM running on proxmox using veeam, restore to Azure?
Any limitations like VM's can't be UEFI, have a TPM disk, or similar?
Thanks in advance.
-
GreenEnvy
- Enthusiast
- Posts: 29
- Liked: 6 times
- Joined: Jul 31, 2012 3:45 am
- Full Name: Lee
- Contact:
-
HannesK
- Product Manager
- Posts: 15973
- Liked: 3597 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Does v13 support restoring machines from Proxmox to Azure?
Hello,
restore from Proxmox to Azure / AWS / Google is supported in general, yes. TPM & UEFI restore won't work.
The limitations on Azure side apply to all backups and I suggest testing the restores. Windows & Linux behave a bit different depending on the disk setup.
Best regards
Hannes
restore from Proxmox to Azure / AWS / Google is supported in general, yes. TPM & UEFI restore won't work.
The limitations on Azure side apply to all backups and I suggest testing the restores. Windows & Linux behave a bit different depending on the disk setup.
Best regards
Hannes
-
GreenEnvy
- Enthusiast
- Posts: 29
- Liked: 6 times
- Joined: Jul 31, 2012 3:45 am
- Full Name: Lee
- Contact:
Re: Does v13 support restoring machines from Proxmox to Azure?
Thanks Hannes.
I did test this yesterday.
At first I was getting errors restoring to Azure. I'd see a warning in the restore logs that conversion failed, but the job still completed.
The error in the logs was related to 'vdmount::CVhdMounter' with error # 1392.
The VM was visible in Azure but would fail to boot.
I found in the release notes for 13.0.1.2067 that this was a known issue that was resolved issue in that build, so I updated our Veeam servers from 13.0.1.1071, and the problem went away.
These machines do have a tpm drive in Proxmox and are Uefi. It looks like Veeam converts them to BIOS during the restore.
So the answer is yes this works, as long as you're on the newest build.
I did test this yesterday.
At first I was getting errors restoring to Azure. I'd see a warning in the restore logs that conversion failed, but the job still completed.
The error in the logs was related to 'vdmount::CVhdMounter' with error # 1392.
The VM was visible in Azure but would fail to boot.
I found in the release notes for 13.0.1.2067 that this was a known issue that was resolved issue in that build, so I updated our Veeam servers from 13.0.1.1071, and the problem went away.
These machines do have a tpm drive in Proxmox and are Uefi. It looks like Veeam converts them to BIOS during the restore.
So the answer is yes this works, as long as you're on the newest build.
Who is online
Users browsing this forum: No registered users and 1 guest