Skip to main content
  • EN

Support for Proxmox from Veeam has been one of the top requests in the last months. Therefore the announcement in May to extend the Hypervisor support to Proxmox Virtual Environment (VE) has been long awaited! This will be the 7th virtualization platform supported by Veeam, in addition to the 3 cloud hyperscalers and the Veeam agents.

The Proxmox integration is currently planned for Q3 of 2024 and v1 will already include some nice features/benefits:

  • flexible storage options
  • immutable backups
  • granular recovery
  • cross-platform recovery (for example Proxmox <> VMware)
  • Veeam ‘standard’ performance with CBT, hot add backup and Bitlooker

In part 1 of this blog series I want to give a quick overview of the architecture of Veeam Backup for Proxmox and it’s initial setup.

 

Disclaimer: All information and screenshots in this blog post are based on an early access release. Until the final release changes can and will occur!

 

Architecture

The Proxmox integration itself will be enabled with an additional plug-in, which is installed on the Veeam Backup Server.

Besides the Veeam Backup Server and at least a Backup Repository, Veeam Backup for Proxmox will utilize workers. The workers transfer the VM data from the Proxmox VE host to the backup repository; similar to the workers in AHV backup or the backup proxies for VMware. They are Linux based and can be deployed directly from the Veeam console. There should be at least one worker per host in order to utilize hot add transport mode.

Plug-in setup

Nothing special to write about the setup of the plug-in; next, next, finish.

 

Adding a Proxmox VE host

After installing the plug-in, Proxmox will be available as an additional server in the Virtual Infrastructure tab.

 

Directly after adding a new Proxmox host, you’ll get asked whether you want to deploy a worker.

 

Afterwards the Proxmox host including it’s VMs should be visible in the inventory.

 

Overall the setup and configuration of Veeam Backup for Proxmox isn’t complicated and is very straightforward. In the next blog post I will focus on backup & restore of Proxmox VMs, and also on the migration of workloads from VMware to Proxmox.

@ABA74 ​@Leela We have now published a possible workaround to backup VMs in stopped state:https://www.veeam.com/kb4715

Hi,We have changed the flag to "true" that is indicated in the line of the .json file and we have tested it and it works correctly!!!All the best. Thank you so much.

Great article

Thanks for your feedback and good to hear that it's working for you 😊

The logged error events are the only downside but probably there's not way to prevent or suppress those.

Hi Regnor,

after an quick test it seems to be working! It still produces many errors on the Prox cluster, but - working 😀. Thanks for following this issue.

Leela

@ABA74 ​@Leela We have now published a possible workaround to backup VMs in stopped state:https://www.veeam.com/kb4715

Thanks ​@Leela. I’ll let this check internally and will update you if I receive a solution.

​@regnor  Hi, here it is :

Case #07447368

Proxmox VM backup only possible on powered on machines

​@Leela Could you please share your case number with me?

​@regnor egnor Hi, I had a ticket opened already, but It was closed without investigation, which I can understand, as I am not an paying customer and the developers are probably busy...

​@ABA74 ​@Leela I don’t know any limitation regarding HA. So could you please open a support case to let our team check this? You can also send me the case number via personal message afterwards.

​@rupinkuruvilla Are you on the official Proxmox image? And if so, has this been host upgraded in the past from an older release?

For an overview you can just double-click on the running job from with the VBR console and select each virtual machine to gather the current status.

And a more detailed log is available on the VBR server under “C:\ProgramData\Veeam\Backup”. Each backup jobs has a corresponding subfolder with it’s name.

Hello
I have a cluster
How can I see detailed logs of work during backup Proxmox?
I didn't find them

Thanks for the answer!

I will try this, but I am afraid, that this can not even be used as an workaround. HA is important :(

Best regards,

Leela

Hi,

I think that if the mv is powered off, I don't see that it is necessary, or that it matters much that it is in HA. It's off. The machine is not running.
But I understand your concern

Regards

I can confirm the observation from ABA74...

Thanks for the answer!

I will try this, but I am afraid, that this can not even be used as an workaround. HA is important :(

Best regards,

Leela

The VMs are running on Proxmox cluster. Some of the disks are on ZFS (and being replicated to other  cluster nodes), I think there it has to be RAW, some of them are on Ceph, I think they are QCOW2. The behaviour is the same for all of the VMs.

 

Nobody else having this problem ? I did find out, that when the VM is powered on, the backup starts and then I can shutdown the VM and all is still OK.

Could somebody please explain, what is in this case the NBD server ? The HV host is probably the Proxmox server, or?  “ Failed to connect the NBD server to the hypervisor host”

Hello,

We also had the error that Leela indicates when we had vms powered off in proxmox and we backed them up in Veeam: "11/28/2024 9:14:08 AM :: hostname-machine : Failed to perform backup: Failed to connect the NBD server to the hypervisor host."

In our case, what we did so that Veeam performed the backup without error, is to remove the vm from the proxmox HA, or set the vm in "ignored" mode in the "Request State" field.

All the best

Hey there,

 

currently getting the error “Failed to get HypervisorNetworko]. Method ‘GET /nodes/host/sdn/zones’ not implemented” when adding a Proxmox VE Worker. 

Any idea why this happens?

 

E: Running Proxmox 8.2.4

 

Has anyone fixed this issue?

I got Failed to refresh entities.

anyone does why ? I tried in two nodes proxmox 8.22 in one is fine and in one I got Failed to refresh entities. when add the proxmox server.

Help..

 

 

 

Nobody else having this problem ? I did find out, that when the VM is powered on, the backup starts and then I can shutdown the VM and all is still OK.

Could somebody please explain, what is in this case the NBD server ? The HV host is probably the Proxmox server, or?  “ Failed to connect the NBD server to the hypervisor host”

NBD is the “Network Block Device” mode used for the proxy backup to copy data on-the-fly between the pve node and the veeam server. 

 

The pve plugin for veeam still does not support DSA “Direct Storage Access” in order to backup data.

 

The VMs are running on Proxmox cluster. Some of the disks are on ZFS (and being replicated to other  cluster nodes), I think there it has to be RAW, some of them are on Ceph, I think they are QCOW2. The behaviour is the same for all of the VMs.

 

Nobody else having this problem ? I did find out, that when the VM is powered on, the backup starts and then I can shutdown the VM and all is still OK.

Could somebody please explain, what is in this case the NBD server ? The HV host is probably the Proxmox server, or?  “ Failed to connect the NBD server to the hypervisor host”

I’m curious as to how the pve backup works when the VMs are stored on LVM (block storage over FC).  in the Veeam doco it states

“Veeam Backup for Proxmox VE creates a Proxmox VE copy-on-write snapshot of each VM added to a backup job. The snapshot is further used to create a VM backup.”

I know on LVM you can’t create snapshots in proxmox, so how is Veeam getting the point in time for the backup?

 

When you deploy the worker vm, it ask you to specify a compatible snapshot storage for maintain the snapshots if the source vm is stored in a storage that does not support it. If you do not have any storage compatible to specify, it will not work.

I’m curious as to how the pve backup works when the VMs are stored on LVM (block storage over FC).  in the Veeam doco it states

“Veeam Backup for Proxmox VE creates a Proxmox VE copy-on-write snapshot of each VM added to a backup job. The snapshot is further used to create a VM backup.”

I know on LVM you can’t create snapshots in proxmox, so how is Veeam getting the point in time for the backup?

 

@DecioMontagna  - I was getting this socket error as well with the same RESTAPI paths… and while I thought DNS wasn’t my issue either, it definitely was.  Everything appeared resolvable between the PVE hosts and VBR, it was the worker that couldn’t talk to the hosts by NETBIOS name.  My hosts have valid DNS records on the server I specified in the worker config, and I had the PVE hosts added to VBR via the NETBIOS name and not the FQDN.  I removed the PVE hosts from VBR and readded them with the FQDN and redeployed the workers.  As soon as I did that, the worker test worked without issue.

Not sure if you might have the same issue but could be something worth looking at.

 

So, for me, like @Rick Vanover said….it’s always DNS 😆

What is the default username and password of the linux worker? t test de DNS resolution? 

@DecioMontagna  - I was getting this socket error as well with the same RESTAPI paths… and while I thought DNS wasn’t my issue either, it definitely was.  Everything appeared resolvable between the PVE hosts and VBR, it was the worker that couldn’t talk to the hosts by NETBIOS name.  My hosts have valid DNS records on the server I specified in the worker config, and I had the PVE hosts added to VBR via the NETBIOS name and not the FQDN.  I removed the PVE hosts from VBR and readded them with the FQDN and redeployed the workers.  As soon as I did that, the worker test worked without issue.

Not sure if you might have the same issue but could be something worth looking at.

 

So, for me, like @Rick Vanover said….it’s always DNS 😆

thanks..

Comment


Terms & Conditions