Error "Transaction was deadlocked..." - should I worry?

[TommyB]

Hi,

every now and then I get the following error message for one or more of the VMs:

"Transaction (Process ID 77) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction."

Simply re-running the tape backup job picks up the missed backups ans pushes them to tape.

According to my web search, this has something to do with SQL server.

I think this started with V8, can't remember this to be happening with V7

The question is - should I worry about this and contact Veeam support?

[veremin]

The question is - should I worry about this and contact Veeam support?

Even though the issue seems to go away, whenever you retry a job, I'd recommend to contact support team and find out the root cause of this behaviour. Thanks.

[cffit]

I'm having this issue as well. Did you come up with any resolution?

[veremin]

The OP has never updated the topic with found resolution, neither has he provided a support ticket number. So, it might be worth reaching support team. Thanks.

[alanbolte]

Make sure you're on Update 3 first, several bugs that could cause these errors were fixed in Update 3. A few hotfixes are available for Update 3, but I have seen some deadlock fixes implemented for v9 that have not been backported to v8.