Invalid repositories appearing

[dasfliege]

I've received a fix from support which solved the problem for us. Version now is 8.1.1.2045

[andre.simard]

Same issue as start here also: Repository is invalid.: Exception of type 'System.Exception' was thrown"
Currently on version 8.1.1.159

i will open a case

Thank you

[dloseke]

I'm now having the same issue. All of my immutable Wasabi repos are showing invalid. I have two repo's that are no longer attached to a backup job, that are not immutable, that are still showing up fine. Opened Case 07709446

[dloseke]

After opening a Sev 1 case and getting a quick response with a link to Fix 960459, it looks like I'm good to go again on 8.1.1.2045. Bravo for the quick fix Veeam!

[dasfliege]

I received a fix for another problem we had and since i've installed it, i have 11 repos going invalid state again!
My version is 8.1.1.2052

[evgenich]

With installing version 8.1.1.2045 problem is resolved. Any news when stable official release will come?

[Polina]

It should be included into the next big patch, which I'm expecting in the next few weeks.

[tkutil]

We just started having issues with Backblaze repos for both VBR and V365. Fixed the VBR with new application keys from Backblaze but this trick did not work for V365. Now we cant even add a Backblaze repo in V365.
Running V365 8.1.1.159
Error: Access denied. Could not perform the operation because of missing permissions or wrong data center region.
Case #07715827

[tkutil]

Is there a KB for this fix 8.1.1.2045?
Where can I get it? I already have a case open Case #07715827
@Polina

[Polina]

@tkutil

There's no KB, you can only get a hotfix via support, and from your case details I see that you have already been provided with it

[pat_ren]

Just updating this as was my thread originally, since working with support and R&D team I have not had this issue for a couple of months now, I am running a lot of private fixes currently so can't remember which one fixed it, but we made a lot of tweaks and significant change was not to run repository maintenance daily on 800 repos, we changed it to once per month and i used a quick powershell loop to set it to a random date/time throughout the month and I believe this was a significant contributor. Worth revieiwng your maintenace schedule for anyone who is having this problem still.

Overall performance and stability is finally improving in v8 (in my experience after ~9 months) thanks to hard work from the Veeam team.

[dasfliege]

Have to post this here, hoping that i can prevent other from running into the same issue:
As written above, we have received a fix for another problem, which updated our installation to version .2052. By installation this fix, the fix for the invalid repo problem (.2045) has been overridden somehow and we now have plenty of repositories which are unavailable again. We basically can't perform backups for like 10 of our customers since one week! According to the support, it's not possible to uninstall a fix, so we have to wait until they have a combined fix ready. No ETA provided though!
This is absolutely inacceptable for a product intended for use by service providers. Don't know how i should explain to our customers, that we were unable to execute their backups for more then a week.