Im pretty sure your issue is the hostname that is not resolvable outside of proxmox. pve01.domain.local is probably a default hostname and you cant ping pve01.domain.local from Veeam Server and Worker. If the Proxmox is inside a Nat Network and you have a local dns server, add a entry for it. If its a public reachable proxmox server you can add a a-record to any existing domain like proxmox.domain.xyz and set the hostname accordingly

Are your workers “hard firewalled” from the VBR server? This would explain the issue, and I can get the documentation updated to reflect these requirements. Thanks @DecioMontagna 

No, this host is not a nested vm. I think this is because there is no token ID configured for API access, but the veeam documentation does not describe this as a requirement for the worker

@DecioMontagna  → I had some worker tests fail when I didn’t have enough CPU, but that doesn’t seem like this type of error. Is your host nested on another hypervisor?

My worker is not passing test connection to pve node (cluster node)

 ERROR | ProxmoxRemoteAgent]]ProxmoxRestClient]:  <== Request "Get" "https://pve01.domain.local:8006/api2/json/nodes", body: "{}"

ERROR | |ProxmoxRemoteAgent]tProxmoxRestClient]:  ==> Response "Get" "https://pve01.domain.local:8006/api2/json/nodes", "status: Error", duration: "2 min 10 sec 210 msec", body: """"

ERROR | ProxmoxRemoteAgent]: Failed to test cluster connection: System.Net.Sockets.SocketException (110): Connection timed out

If I try to access a brownser with https://pve01.domain.local:8006/api2/json/nodes I got a 401 error.

“replicating to a completely other hypervisor platform is the dumbest thing I have seen in a while..”

2 thoughts: 

1. That’s harsh. We try to play nice here on the community
2. Migration use case, sure. “Regular DR” - I agree it is not practical - exception maybe some want to plan on cloud target as DR (which is a different platform).

I do see a market for an in-operating system type of sync, which can get into new problems of drivers and such. But above all, I think high speed recovery with Veeam goes a long way. There are tricks with what we already have. Agents maybe still, Instant Recovery to Hyper-V Role on Veeam B&R server, etc.

@Bitcircuit I believe there’s been a misunderstanding. My inquiry was specifically about global replication with Veeam, including scenarios involving Proxmox. The mention of replicating from Proxmox to VMware was not suggesting it as a direct feature but rather exploring potential workarounds or alternative solutions that Veeam might offer. If you’re focusing on Proxmox to VMware, that’s a different issue and not the core of my question. Let’s clarify: I’m interested in how Veeam can facilitate replication across different environments, not just between two specific systems. Your comment seems to miss this context entirely.

There are still options to replicate to another cluster depending on the current Cluster Setup but you stated to replicate from Proxmox to vmWare what makes absolutly no sense

@Bitcircuit The native replication in Proxmox does not support the direct replication of virtual machines (VMs) between two different Proxmox clusters. Replication is designed to work only within the same Proxmox cluster, where nodes share a common configuration and centralized management. The most frustrating and ignorant thing is when someone talks without understanding the situation.

Replicating to a completly other Hypervisor Platform is the dumbest thing i have seen in a while. Why would anyone do that instead of running 2 independent proxmox clusters and replicate them? 

Issues with Bootloader and missing drivers may be expected if not any other problems. You would have to convert the drive to vmdk and probably fix Bootloader when switching from Proxmox to ESXi

@marouen labidi → We have not announce any replication type of capability for Proxmox VE but this and many things have been requested. Nothing to share at this time other than the interest in Proxmox is very strong, which prioritizes new capability priorities.

@Bitcircuit we need replication from cluster PROXMOX to another cluster vmware, PROXMOX do only replication in self cluster and need ZFS or Ceph storage and we don’t have thoose requirement!! thats why we need it from Veeam, i’m only asking about this feature in veeam when its available, thans.

Proxmox has pretty good HA and Replication capabilities by itself. Why do you need that feature in Veeam?

@regnorThanks for the answer, but when will this feature be available?

@marouen labidi Sorry for answering in english, but for now replication isn’t available for Proxmox VE.

@Freddy86 If the preparation time for the worker takes too long, you could post your feedback in the R&D Forums. This way it might get changed in the next release: https://forums.veeam.com/kvm-rhv-olvm-proxmox-f62/

Est t-il possible de lancer des tâches de réplication Veeam des machine virtuelles sous PROXMOX-VE ??

You have to disable the preallocation for the proxmox storage or make it us default

I have the same problem. Are there people who claim that it is language related?

@regnor I just tested it. When starting a Backup and Veeam Console getting the worker ready until it says the worker was prepared successfully it took 6 minutes and 30 seconds. I our environment it takes between 11 and 13 minutes after starting a job until the first bytes are beeing transfered. 

@Bitcircuit Thank you very much for your feedback. Only Proxmox VE hosts installed via the image from Proxmox are supported. The helpcenter article regarding the System Requirements got updated: https://helpcenter.veeam.com/docs/vbproxmoxve/userguide/system_requirements.html?ver=1

@Freddy86 As you say it’s about saving resources, as the workers are only needed during the backup. How much time does it take for the worker to get active?

Nice one Max, thanks for sharing!

Is there a special reason why the workers getting shutdown after every job or just saving resources on the cluster? Is there a option to let them turned on? Starting the workers and waiting for them to contact the backup server is taking quite long. Taking backups of serveral hundred vms and terra bytes, every second counts in the night :-D  Besiedes that you guys did a greate job with the proxmox implementation. We waited for this!

There seems to be a difference in using Proxmox from the PVE Installer and using Proxmox as Debian 12 Installation via https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm

Using the PVE Iso, i had no issue deploying Veeam and the according worker for it.

Not a problem.  Let us know how you make out and what ends up fixing this for you.

thanks Chris, 

I'm currently working in a lab environment, so I can't open a support case right now. However, I plan to do the same for the customer later, and it should work for now.