Maintain control of your Microsoft 365 data
Post Reply
t7MevELx0
Service Provider
Posts: 61
Liked: 9 times
Joined: Feb 06, 2024 6:55 pm
Contact:

Cleared NATS Cache, Restarted Services – VBO Still Not Processing Jobs; 8.1 and then upgraded to 8.1.1; no change.

Post by t7MevELx0 »

We were notified that jobs were “stuck” on one of our Microsoft 365 environments, so we proceeded with the upgrade to version 8.1.1. However, after the upgrade, the jobs remained stuck.

I cleared the NATS directory and restarted all services. This resolved the usual symptoms we see when the NATS cache is the issue—there are no running jobs now—but starting any job results in it getting stuck at the "Detecting" stage. No data is processed.

At this point, we have another large Veeam Backup for Microsoft 365 environment that has stopped working unexpectedly. The 8.1.1 update did not resolve the issue.

Support Case #07670283 – Severity 1.
t7MevELx0
Service Provider
Posts: 61
Liked: 9 times
Joined: Feb 06, 2024 6:55 pm
Contact:

Re: Cleared NATS Cache, Restarted Services – VBO Still Not Processing Jobs; 8.1 and then upgraded to 8.1.1; no change.

Post by t7MevELx0 »

Well, we have an update on this one. We used PowerShell to start one of the jobs as -runasync, and for some odd reason, now all of the jobs are working. Even though we only ran that command against a single job / org... It somehow knocked something loose for everything.

I'll be watching it, but so far at least it's working again.
t7MevELx0
Service Provider
Posts: 61
Liked: 9 times
Joined: Feb 06, 2024 6:55 pm
Contact:

Re: Cleared NATS Cache, Restarted Services – VBO Still Not Processing Jobs; 8.1 and then upgraded to 8.1.1; no change.

Post by t7MevELx0 » 1 person likes this post

Just wanted to share how we got the jobs moving again in case it helps someone else later. It's a bit odd—we only ran this against one organization's job out of hundreds, but after that, the other jobs started responding too, without needing to run it for each one. No idea why that worked, but I’m glad it did.

$job = Get-VBOJob -Name "Job Name"
Start-VBOJob -Job $job -Full -Runasync

I also want to thank Veeam for obviously hiring more people/help for the O365 software. I opened that severity one case and I actually had someone on the phone in under an hour per the SLA. So thank you!
Post Reply

Who is online

Users browsing this forum: jeffrey.saavedra and 92 guests