Jobs stalling with VBM365 Failed Nothing to Process - Build 8.1.1.159

[claudiohipolito]

We have backup jobs on the VBM server showing a nothing to process error. The job gets stuck in detecting mode and then fails immediately.

I believe the error is due to connectivity with the NATS Server. This has happened before and we resolved it by updating the version, but we are now on the latest release 8.1.1.159, replacing 8.1.0.3503, which caused the same error.

We have backup jobs on the VBM server showing a nothing to process error. The job gets stuck in detecting mode and then fails immediately.

I believe the problem is due to connectivity with the NATS Server. This has happened before and we resolved it by updating the version, but we are now on the latest release 8.1.1.159, replacing 8.1.0.3503, which caused the same error.

In our environment, the NATs Server was previously installed on port 4225, since port 4222 was already in use by a vulnerability management solution.

An old workaround was to delete the cache from the nats-server stream folder available in the C:\ProgramData\Veeam\Backup365\nats\jetstream\$G\streams directory, but this folder only exists when NATS-Server is installed directly through the VBM setup.

Registered case 07694872 in support but no workaround recommendations for now.

Thanks.

Cláudio Hipólito

[t7MevELx0]

I've been deleting the NATS streaming directory and restarting services for weeks now. They need to pull this version/build, as it is clearly defective.

Case #07674412 — Issue "Case #07670283"

The last "fully" working version was 8.05.

[raftbone]

I'm having the same issue. Some jobs seem to be stuck, but when I check the logs on the proxy, they seem to be still running.
As soon as I restart the main Veeam M365 server, the job status is updated on the console. Seems to be a communication issue between the proxies and the main server.

However, some other jobs (especially copy job) are completely stuck even after rebooting the main server. Those issues really needs to be addressed. Having tons of issues since upgrading to version 8.

[jokester6633]

Good luck. Tech support has not moved much on my case that has been open since beginning of February.

[donkeymagic]

We had a similar issue recently which was caused by installing a recent .net framework updated but not an optional rollup update for Windows. We had very similar issues in that backups would start and just do nothing (only affecting a single organisation) with the others running ok. Veeam support went round and round in circles and couldn't diagnose the issue (firewall, ports, permissions etc) but I ended up installing the optional windows update and it resolved the issue.

The .net update was KB5057056 with the windows rollup being KB5055612. The solution has been perfect since but it gave very similar results before hand in that the NATS server wasn't responding and/or passing on the information to the proxy server and we had to delete the cache to keep some stability in the solution.