SQL Error when looking at Tapes

[aaron@ARB]

Veeam,

I have had 2 jobs logged now for an SQL error when looking at tapes (Jobs 01806664 and 01879550). The error is still present in 9.5. Should I log another job? Is it going to be fixed in a version coming up? Its just that its incredibly annoying!



Cheers,
Aaron

[Dima P.]

Hi Aaron,

Checking your cases. Stay tuned.

[aaron@ARB]

No worries thanks, happy to log a 3rd case but i thought i would just check first...

[Dima P.]

Aaron,

It's not required. I checked with DEVs and they are working on a fix. I was told that this could be fixed by updating the SQL database with this patch. If you are going to do it, do not forget to take a VBR’s configuration backup before installing the patch, just in case.

[aaron@ARB]

I am already running SP3 which given that the link doesn't include it, I assume means that it was already fixed by SP3?

Nonetheless, I am downloading the latest CU (6) (https://www.microsoft.com/en-us/downloa ... x?id=50733) and will see if that helps.

[Dima P.]

Aaron,

This CU should be installed on top of the SP3. Let us know how it goes, meanwhile I’ll push the team to include a fix from our side to the upcoming update.

[aaron@ARB]

Any news on when this will be fixed? I have just installed VBR 9.5 SP1 and the fault is still there even with the latest SQL updates etc. We have had a few VBR updates since I first reported the issue to support (and been told 'yeah a fix is coming'), can we have some traction on it please?

[veremin]

It turned our that the issues is hard to reproduce and requires a more complex fix that we've originally thought. So, according to the plan, it should be fixed in version 10, rather than in one of the upcoming updates. Thanks.

[aaron@ARB]

Happy for you to see it in my environment, i can reproduce it quite regularly.

[veremin]

I'm wondering what type of SQL server you're using. Built-in SQL Express or fully blown SQL server.

[aaron@ARB]

I'm wondering what type of SQL server you're using. Built-in SQL Express or fully blown SQL server.

Builtin

[veremin]

Don't you happen to have a full blown SQL server at hand? If so, it might stand to reason to switch workloads to it to avoid the said issues. Thanks.

[aaron@ARB]

I have moved this to our production SQL database, i will report back.

[veremin]

Having a product db running on full SQL server should fix the given problem, indeed. Kindly, let us know, if the issue persists.

[aaron@ARB]

The problem remains. It just happened twice now. I am going to re own the support case.

[aaron@ARB]

*reopen

[veremin]

We'd appreciate, if you provide us with a ticket number. Thanks.