Invalid repositories appearing

[pr_osit]

Hey all,

Another issue has appeared in version 8 for us the last few days, was working well for almost 5 days on v8.0.2.501 without any major issues then this new problem started out of nowhere. First a few jobs failed with invalid repository, then a few more and now I have 20 invalid repositories. A few more seem to become invalid each day.

The issue is 'Repository is in an invalid state. The local cache and object storage are not synchronized.'

I knew how to fix this in v7 but no idea in v8 since the local cache has moved. This is causing the 20 jobs which use those repos to fail constantly now. The sync repo button is greyed out in v8 and there's no local cache folder on the proxy to clear anymore.

A case has been logged with support Case #07440695 and trying to provide them the info they need to help troubleshoot.

Any extra eyes I can get on this issue would be appreciated, thank you.

Kind regards,
Pat

[Polina]

Hi Pat,

In v8, repository caches still exist and synchronization is still required; but instead of a separate database per repository, caches are now stored in a centralized database.

Thank you for the heads up; I'll bring your case to the attention of our RnD team to fix it faster. Please keep working with our support engineers.

Thanks!

[aeph]

"to fix it faster" - what does this mean? We constantly report issues around repo sync stuck and invalid state since two weeks and the message is still the same "RnD is working on it". So it should not be a recent discovery.
We backup a lot users - we urgently need a solution.

Thanks!

[pr_osit]

I received a fix from support, basically had to delete and re-add all of the invalid repos. This is fairly time consuming but has fixed my immediate issue. I do still have some concerns about what would cause 20 repos to become invalid within about a 24 hour period, I'll be looking further into root cause analysis try and identify the issue as so far there's no clear cause of the problem identified.

[aeph]

With fix you mean a private fix with a specific build version number? May i ask which build number this is?
We also got a hotfix but it was not solving the issue.

[pr_osit]

Hi aeph, I didn't get any specific private fix for this issue, the fix was just removing and re-adding all of the affected repos, but I've received fixes for other issues, currently on 8.0.2.501 for about the last 2 weeks, and still having new issues popping up almost daily.

[aeph]

Same for us. But we have 8.0.2.311.

We added the repos again several times, but that didn't solve the problem either. We still have repos that we can't add - for more than two weeks.

[edh]

@aeph 8.0.2.311 is a private fix/version?

[Mildur]

It‘s shared as a private fix. Public releases are listed here:
https://www.veeam.com/kb4106

We plan to release a public cumulative patch soon with all the fixes.

Best,
Fabian