Well.. proxmox suggests you should install 'workers (== proxies)' on your pve hosts when you add them through the wizzard (it's a checkbox). Then, when it's installed it will test them and starts them. I see all that in the proxmox events. The deploy/test window in veeam reports the error after a while. I'll assume that it is not a big thing in a test environment with two hosts and 6 VMs, but as the option is offered, I'd like to try.
Also you can deploy the workers in the backup proxies after the fact under backup infrastructure, if you have pve hosts added.
Fwiw. I've been reinstalling veeam on windows 2022 since noon, because veeam might have missed 2012r2 (my POC server version) testing for proxmox support, even though it the documentation suggests that 2012r2 is supported for v12. There might be some windows old-school ssl cert used, but I didn't figure out yet if this is the case or on which service. Almost there. We shall soon know.
Also you can deploy the workers in the backup proxies after the fact under backup infrastructure, if you have pve hosts added.
Fwiw. I've been reinstalling veeam on windows 2022 since noon, because veeam might have missed 2012r2 (my POC server version) testing for proxmox support, even though it the documentation suggests that 2012r2 is supported for v12. There might be some windows old-school ssl cert used, but I didn't figure out yet if this is the case or on which service. Almost there. We shall soon know.
Statistics: Posted by gdvm — Aug 30, 2024 1:14 pm
