Tapejob error INSERT statement conflicted

[dlieshout@client.nl]

See Case # 00451296

Got now 2 customers with exactly the same error on there tape-jobs. Upgraded Veeam 6.5 to 7. Kept the local SQL Express 2005 database which has enough space left.
Tape jobs worked fine since Veeam 7. But after about 2 weeks it keeps getting the error:

Task F:\VeeamBU\BU-DomainServers\BU-DomainServers2013-09-30T180215.vbk failed: Microsoft SQL server hosting the configuration database is currently unavailable. Possible reasons are heavy load, networking issue, server reboot, or hot backup. Please wait, and try again later. Error information: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Tape.file_parts_file_versions". The conflict occurred in database "VeeamBackup", table "dbo.Tape.file_versions".

Tape job does dump all VBK-files in the path F:\VeeamBU. Together that is some TB's. This error shows up after a couple of hours dumping to tape.

Does anyone else have the same sort of error? Dump of database is now at Veeam Support.

[veremin]

From my perspective, it might be the case with overloaded SQL server. So, you might want either to update existing SQL server to, at least, 2008 Express or split your huge job into several small ones.

Also, do see any correlation between the side activities, such as tape change, and time you get the abovementioned error?

Anyway, thanks for providing the case ID – we will track the case and update the topic, once the root cause and/or resolution is found.

Thanks.

[dlieshout@client.nl]

Veeam did research on this case. Got this with 2 customers.
Got a special hot fix and is toetsing now.

[veremin]

For all new comers:

The private hotfix is currently being tested. So, if you’re experiencing similar problem, don’t hesitate to contact our support team and they will provide you with it. Assuming that the tests are successful, the fix will be included in the future patch.

Thanks.

[lordjeffers]

I'm getting this same error with a certain job. Using a new Veeam 7 installation (i.e. no upgrades)

I was getting this the other day so deleted the tape job and started again, which works. But I'm not really in a position to do that now.

I'll log a call in the morning...

[veremin]

Hi, David.

According to the plan, this issue should be fixed in the up-coming patch, assuming nothing unexpected shows up. For now you should, indeed, get in touch with support team in order to get the said fix.

Thanks.

[DJ82]

Hi,

Do you know, when the patch is comming?
We have exactly the same error.

Kind regards,
Daniel

[veremin]

Hi, Daniel, please take a look at the estimation provided by Anton Gostev. Thanks.

[DJ82]

Hi Vladimir

Thank you - But I don't need vSphere 5.5 Support, I only need the patch for the "tape error".

[veremin]

As far as I know, the said hot-fix should be included in the patch#2. This patch also adds support for new hypervisor platforms.

However, if you don’t want to wait for the patch release, you can open a ticket and obtain the hot-fix from the support team.

Thanks.

[connecT]

I installed the patch 3, but get the same error as described above.

Did it work with your tape-jobs after you installed the patch?

[Dima P.]

Hello,
I strongly encourage you to open the support case, as the hotfix for this issue was merged into product since patch 2 - so it is flagged as fixed. Please, update this thread with the case ID, so we could follow up. Thank you.