Today was a demo of the upcoming veeam support for proxmox ve. Does anyone have new information on what can be done and if there are any limitations? I saw a video on linkedin and did a quick review of what I could see from that clip:
Also some links there are currently there for more information:
* Veeam Extends Data Freedom for Customers with Support for Proxmox VE [Link]
Lets wait for a demo with live restore without downtime and also file-level-recovery etc.
Edit: Update I got the recording now
Also some links there are currently there for more information:
* Veeam Extends Data Freedom for Customers with Support for Proxmox VE [Link]
Here you can see a recording of the Hashtag#Veeam support for Proxmox VE. An analysis:
* The demo does not show a live migration, but an offline migration
** In theory “this could also be live ... ?", however, this should work
* In the demo, the VM restarts within a minute
* this means: either the VM is very small and was transferred in time
** or it is similar to the Proxmox VE ESXi importer, starting the resources at Proxmox level including data streaming (which would not be so fine) (unless they protect it against potential data loss in the event of VM failure during recovery)
* In the Veeam log you can see “Type: Hot-Add” I'm not a Veeam pro now, I used to have a VMCE in version 7. Does anyone here have more info on what it does effectively?
* VMs can be converted to any format (qcow2 or raw) when selecting the target PVE host (or you can stick with the VMDK)
Unfortunately, there are no papers online that describe the exact feature scope. However, support is planned for the next Veeam GA version (Q3).
Lets wait for a demo with live restore without downtime and also file-level-recovery etc.
Edit: Update I got the recording now
- Migrate Proxmox from 5 other hypervisors to Proxmox VE with just a few clicks
- Hyper-V, Nutanix, VMware, Oracle Linux VM, Redhat
- VM has only 2.5 GB size (small Linux)
- VM is shut down before the backup
- The live demo switched to a video showing the process due to problems
- You can select the target storage (reads the storages from PVE)
- You can select the target format (qcow2, raw or vmdk)
- The network is matched, but you only see a matching to vmbr0 (no details)
- The VM is restored and then switched on and is accessible again (offline restore)
- Details of the restore:
- you can see in one frame that the VM has 512MB RAM, 1 core
- the VM has a legacy BIOS
- the LSI storage controller is used (no virtIO)
- the network uses a virtio driver (and works after the restore)
Last edited: