V12: Retention job fails backup, backup also blocks retention job

[mkretzer]

Hello,

at the same time the new V12 retention job can be blocked by backup:
26.08.2023 12:28:02 xxxx Unable to delete backup file xxxx - xxxx because it is locked, waiting for it to be unlocked...
AND can lead backup to fail:
12:23:10 Task failed. Error: Item [xxxx- xxxx] is locked by running session Retention job [Retention job]

Is that normal? Why should a backup fail because of an retention job and at the same time block the retention job?

For us thats a huge issue as there are days where backups run nearly 24 hours a day...

Markus

[mkretzer]

To my surprise Veeam immediately delivered a hotfix via Case 06264521...

[S0ufiane]

Hello,
We have the same problem, can you share with us the hotfix the support provided?
This is an urgent matter and we don't have time to open a support ticket.
Regards.

[Mildur]

Hello Soufiane

Private Hotfixes are not shared publicly. Before a private hotfix is provided, we need to be sure that it solves the exact issue you are facing. Therefore a most recent log package must be investigated by our support team.

Please open the support case and provide me with the case number. If it's "urgent", open the case with severity 1.

Best,
Fabian

[mkretzer]

And tell them our case number...

[tyler.jurgens]

A sev 1 ticket opened with Veeam will definitely get you better results than posting on a forum and hoping the OP sees and shares the hotfix with you.

Out of all the vendors we work with, I rarely get frustrated opening a Veeam ticket. If only other vendors had the same quality support Veeam does.

[mkretzer]

Yes, and simply sharing private fixes is not ok (in the end its my fault your backup system fails). But normally Veeam helps quite fast!

[Mildur]

Thanks guys.
Private hotfixes should never be shared via a forum post between users. A hotfix may interfere with other hotfixes installed on the backup server. Or it may come with known limitations.

So it‘s a must to wait for the investigation and recommendation of our support team.

Best,
Fabian