Skip to main content
Question

support of Proxmox Ve 9.0.18

  • November 20, 2025
  • 6 comments
  • 28 views

atinivelli
Forum|alt.badge.img+3

Good day, I have a PVE 9.0.18 in my NUC, using local storage only. Yesterday I updated the VBR and Plugin to the very lastest versions. But..

Well, the Proxmox plugin still isn’t working for me… it’s really strange: I configured and tested the worker successfully;

I added a Windows VM (same subnet as the VBR, no firewall) to a job

If I run the credentials test, it fails because the VM is powered off (??)

The backup, even crash-consistent, also fails

For the credential test, I guess the error in the log is: 

“”aiting for file C:\ProgramData\Veeam\Backup\Plugins\PVE\Backup\PVE-Win_c1c3bce9-32d8-419d-b31a-6a63f6c6d2de\8fa94a5b-e558-4d50-bb67-241ff316ecab\PVE-Win.log to be unlocked”

for failed backup (hot add mode)

Failed to await the Backup task 444dd208-68ee-498c-aa5a-8282d85b2369: Veeam.Communication.TypeProvider.Invoke.RpcCallException: Failed to perform backup: Failed to prepare disks for backup”

 

what am I doing wrong?

6 comments

coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • November 20, 2025

Hi Alessandro -

Markus posted a couple links on this in our V100 group:

https://www.veeam.com/kb4687

and

https://forums.veeam.com/kvm-rhv-olvm-pve-schc-f62/no-pve-hypervisor-workloads-after-inplace-upgrade-t101073.html

The forums post suggested an invalid certificate which may need changed.


atinivelli
Forum|alt.badge.img+3
  • Author
  • Veeam Legend
  • November 20, 2025

it appears to be a different issue…
i think I’ll have to try opening a support case as it was a production environment.


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • November 20, 2025

Ah, ok. Interested to hear the resolution when you get one.

Thanks.


atinivelli
Forum|alt.badge.img+3
  • Author
  • Veeam Legend
  • November 20, 2025

opened Case #07894154 🙋🏻


  • New Here
  • November 24, 2025

Hi

I opened last week a Case for same error : 07895480 

With Veeam 12 and the latest Proxmox plugin, everything worked on my two servers sharing eight VMs (I ran a backup just before installing Veeam 13 on another VM).

Before migrating to Veeam 13 on November 19th, backups of Windows, Debian, and FreeBSD VMs worked perfectly.

I installed Veeam 13, and with the same configuration, Windows VM backups work, but BSD (pfsense) and Linux Debian backups do not.

I'm getting the same message: "Failed to perform backup: Failed to prepare disks for backup."

I then installed Proxmox version 9.1 on Wednesday, and the backup still works perfectly on the Windows VMs but fails on the BSD and Debian VMs.

The workers on both servers start correctly, and the worker test is OK.

I disabled application-aware and guest file system indexing for the failing VMs, but that didn't change anything.


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • November 24, 2025

Curious what you all get as the resolution...🤔