Veeam Backup for Microsoft 365 • Re: Invalid repositories appearing

To update this case again, I have looked at my jobs today and there's approx 60-80 jobs which all failed with the following error:
6/10/2024 4:13:16 PM :: Nothing to process
6/10/2024 4:13:16 PM :: Repository is in an invalid state. The local cache and object storage are not synchronized.

Veeam, we really need a fix for these constant issues, every day since upgrading to version 8 there has been problems, if I could go back to version 7 I would do it right now.
This update just doesn't seem like it's production ready.

edit: the number of failing jobs with the same error keeps increasing, it's now over 100. I suspect almost all jobs are now experiencing this issue.
I'm not doing the same fix as last time which was move job to temp repo, delete old repo, stop all services, delete lock file from object storage, start services, re-add repo to console, re-add job to repo and let job do a full backup. there's a couple of jobs that haven't even finished a full since the last time this happened. we need a better solution.

My support case has been updated with the new instance of this same issue.

Statistics: Posted by pr_osit — Oct 06, 2024 8:20 am

---