Skip to main content

I'm running Server 2022 Definitely in 64 bit (Do they make 32 bit even????) and whenever I try to create a VMWare proxy or any other proxy I get the error "VMware backup proxy requires 64-bit operating system"

 

I have no idea why, and I haven't found anywhere leading me to anyone else having this exact issue either. Any idea what might cause it?

Windows server has been 64-bit only since 2008 r2, can you grab the logs for this to determine what it sees?


Windows server has been 64-bit only since 2008 r2, can you grab the logs for this to determine what it sees?

Yeah I can. Any idea where I would start to look to see what it’s seeing?


Hi @cylemmulo ...the logs for VBR are located in:

%ProgramData%\Veeam\Backup , as noted from the Helpcenter here. Proxies deal with the Transport service, so I’d look at the Svc.VeeamTransport.log to start, then go from there. Maybe the Svc.Installer.log after.


Hi @cylemmulo ...the logs for VBR are located in:

%ProgramData%\Veeam\Backup , as noted from the Helpcenter here. Proxies deal with the Transport service, so I’d look at the Svc.VeeamTransport.log to start, then go from there. Maybe the Svc.Installer.log after.

Thanks! Yeah in everything it detects it correctly

“.2023 03:25:28.099] <  9076>          |   Module version: 12.0.0.1420
.29.04.2023 03:25:28.099] <  9076>          |   Build edition: standard
t29.04.2023 03:25:28.099] <  9076>          |   OS version: Microsoft Windows Server 2022 (21H2, 64-bit) (10.0.20348)
29.04.2023 03:25:28.099] <  9076>          |   Process Id: 5248”

 

Weird enough, this time it allowed me to create the proxy, but when i attempt to use it I get the error that “All backup proxies are offline or outdated” So it refuses to use them.

 

It’s allowing me to use a remote proxy, just to be clear this is with using the current server as the proxy.


That is weird. I’d go ahead and open a support case bud. At this point, your best bet.


Strange….please report back what you find out.  I’m really curious about this one.


Hi @cylemmulo ...did you ever get Support assistance with this? If so, curious what the resolution was as there seems to be another poster with a similar issue, albeit running on Win10 22H2.

Thanks.


Comment