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.

Great article Max. Looking forward to testing this at some point.

FastSCP already works! Throwback!

Great article, thanks for sharing! @regnor 

Hi @Kremensky , the plug-in is currently in private beta, so it's not yet available in public. There's no information available so far about the community edition.

Nice initial setup post Max. Looking forward to other Parts!

Hello! 

Is it possible to download this plugin somewhere? Couldn't find it

And will there be access to it in the community edition?

More to this @Kremensky  → engage with your Veeam contact, such as an SE, as this is supported by the account team or whoever issues you the beta.

@weierstock Actually the DNS settings are in a different dialog; see my screenshot below. Maybe the documentation needs an update as it’s not so specific.

@augusto.lira The release was planned for Q3, so hopefully it won’t take that much time anymore :)

where to locate this plugin

@regnor 
According to the picture, there are only 6 virtualization platforms. Which is the other one?


“This will be the 7th virtualization platform supported by Veeam”

 

@YiDongVeeCN We count ‘Azure Stack HCI’ as a separate platform. It’s added via ‘Microsoft Hyper-V’ on the screenshot, so this point can be seen as 2 platforms.

Thanks for the answer

Great topic Max, congratulations! I’m anxious to try it!

Does anyone knows when it will be available for all?

Wow, looks already well ahead in the development. Looking forward for the availability to download and test it !!

Got the beta so will test it soon after work calms down.  Looking forward to this one. 😎

How can one person jioin the beta program?

Great article, Max.

I am anxious to try it myself. 😎

@YiDongVeeCN We count ‘Azure Stack HCI’ as a separate platform. It’s added via ‘Microsoft Hyper-V’ on the screenshot, so this point can be seen as 2 platforms.

Great, Anyone can set me to download the plug-in ?

I’d like to POC for my customer.

Great, Anyone can set me to download the plug-in ?

I’d like to POC for my customer.

Please keep in mind that the plug-in hasn’t been released so far. Therefore it should not be used in any productive environments or for customer POCs.

We host about 200 customers on Proxmox infrastructure and can’t wait to start testing this. Thank you for your innovation and great guides like this!

 

Hello,

I’m in the process of deploying the Veeam Worker on a Proxmox node, but it consistently fails with the same error. Have you encountered this error before, and do you have a solution?

 

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.

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

I can confirm the observation from ABA74...

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.

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

Comment


Terms & Conditions