Veeam Issues After Backup Server Migration

[nbaptista]

Hello,

We had a Veeam software solution installed in a VM running Windows Server 2022, which so far it has worked great for several months, recently we have decided to buy a new dedicated server to have the Veeam software solution installed.
So I've proceeded with a basic installation of Windows Server 2025 OS and Veeam software, and did the configuration export from the "old" server and imported the configuration in the new server using the "migration" option, so far, everything went fine. Btw, the Veeam software version used was exact the same between the old an new server, Build: 12.3.2.3617.
But as soon the new server started to run the usual backup job cycles, I started to see weird errors in the backup jobs, which I can't find a pattern of these errors because everyday it may hit in a different job, or even if it hits in the same job the error hits in a different VM, so the behavior is very random.

The errors that I'm having are these ones:

- A very persistent error
Task failed. Error: Access is denied. RPC function call failed. Function name: [GetSvcVersion]. Target machine: [xxx.xxx.xxx.xxx:6160].

- Errors that appear from time to time
Error: Failed to call RPC function 'DDBoostFcIsExist': Access is denied. RPC function call failed. Function name: [DoRpcWithBinary]. Target machine: [xxx.xxx.xxx.xxx:6160].
Error: Failed to call RPC function 'DDBoostFcIsExist': Access is denied. RPC function call failed. Function name: [DoRpc]. Target machine: [xxx.xxx.xxx.xxx:6160].
Error: Failed to call RPC function 'DDBoostGetUnitInfo': Access is denied. RPC function call failed. Function name: [DoRpcWithBinary]. Target machine: [xxx.xxx.xxx.xxx:6160].

The target machine IP also tends to be random, meaning, we have setup 4 VM backup proxies, the same ones that were being used with the older backup server without any problems, and with the new backup server, the errors above appear hitting one them in a random way.

Even though I've these errors, Veeam does the auto retry and the job finishes at the second time successfully.
Now the issue is, what is causing these random errors, I've already open a support case on this issue but so far no solution on sight.

Anyone experienced something like this? Am I missing something in the backup server migration?

Thanks,
Nelson

Veeam Support Case ID: 07756357

[david.domask]

Hi Nelson,

Thanks for the details and sorry to hear about the challenges.

That it's intermittent makes me think either periodic network issues or something with one of the Guest Interaction Proxies, but regrettably from just the above it won't be possible to divine much more.

I'd review the User Guide page for Guest Interaction Proxies and ensure the requirements are met and that the account used for Guest Processing meets the required permissions. I would manually check each one even if the account should have permissions, as it's possible maybe something was changed inadvertently.

If that doesn't help, please continue with Veeam Support, as likely a review of the logs will be required to better understand the intermittent nature of the issue.

[nbaptista]

Hi David,

I've checked the network connectivity from the new backup server and I don't see any errors at the network port switch, also I did some pings while monitoring the backup jobs were running and didn't caught any timeouts against the backup proxies.

As for service account that I'm using to connect the backup server to the backup proxies, I've changed/renewed the account password but the behavior continues to be the same...

This might sound weird but is there anything related to the fact of the newer backup server having installed as OS the Windows Server 2025 which could contribute to these issues? the older VM backup server had installed a Windows Server 2022 and hadn't any issues like this.

Thanks,
Nelson

[david.domask]

Hi Nelson,

Thanks for checking those details. Please be sure you note the testing you did in your Support case.

As for your question, off the top of my head I cannot think of anything related to Win2025 as the VBR server (and presumably Guest Interaction Proxy), but it would be good question to ask Veeam Support in your case.