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.
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.
Statistics: Posted by donkeymagic — May 12, 2025 7:30 am
