Deadlocks in Backup Copy Jobs -> Copies Corrupted #01752760

[mkretzer]

Hello,

we are quite worried... We have set up several backup copy jobs to a off-site SO repo with single VM backup chains. Every now and then we get database deadlocks in the Veeam database while merging the backup - but only on these jobs which use the new repo.

The thing is that after the deadlock it is not possible to just restart the job/merge because metadata seems to get corrupted and Veeam just does not find the files in the remote backup repo anymore because they were successfully merged but it is not in the db.

Removing backups from DB, rescanning, mapping did not help.

Only deleting and doing active full - loosing the backups.

Has anyone experienced something similar?

Case 01752760

Markus

[mkretzer]

We will change everything back to non-single VM files as recommended by Veeam on the phone because it is less likely to happen then. Lets hope this is true...

BTW the backups could be "fixed" by editing the database.