@florent So the "Official tip (straight from the doc) is:
If you have full and incremental backups on a remote, you must configure 2 mirror backup jobs, one full and one incremental." from the docs is wrong....
If positive you should change that.

@florent Thank you!

So just to confirm if I understand it correctly I don't need the full (haven't been using it, only the incremental mirror and it seems to have worked).
And therefore I don't need the schedule also. Just an incremental mirror.

@TS79 This part of backups is bloody confusing!!!!!

@manilx
Did the following:

The schedule runs at 6. The 2 mirrors are disabled (if they were enabled the backup schedule would run or wouldn't it?).

This is really not clear at all in the docs.

@TS79 Thx! I had that but I must confess that it didn't seem logical to me....
So I do a sequence, full mirror and then incremental mirror.

What should I put in the backup retentions if I want to keep 3 months worth. And the original delta backup is daily.

84 full and 84 incremental?

My main backups are delta backups (with full backups after x backups) to one NAS and after that I'm doing a Mirror incremental backup to another NAS.
Do I also need to do a Mirror full backup (in addition)? Or does the Mirror incremental one have all backups of the original NAS (or even more depending on the backup retention defined?

@olivierlambert No more EPYC's here, that's for sure. In the future it'll be Intel again (even if they then belong to Broadcom and TMC :p)

@nicols We're on 2 HP's with AMD EPYC 7543P 32-Core and it is a pain.
Had to deploy Intel server just for running the backups, which improved a lot (but that's stupid with 2 beasts of hosts)

@olivierlambert Just to confirm that the error have stopped since I changed the backup plans.

The change being to have only one schedule per job and not using Replicate jobs.

@olivierlambert I can then restore the config and retest once it's identified/fixed.... But just now I need the backups working without issues

@olivierlambert Sure!

I had a main backup job running 2 schedules, on bihourly and one last one at the end of the day, the latter one with healthcheck.

Then I had 2 Mirror incremental ones running after that, one to a local NAS and one to a remote NAS @office.

I now have separate backups for the bihourly, end of day and the 2 mirror ones (now they are delta backups directly to the NAS'es).

I hope this explains it.

@olivierlambert I have changed my backup strategy because of that:

Before:

Now:

After this the problem did no longer occur.

@SudoOracle Thx for chiming in!

Glad to know I'm not alone.

@florent This make no sense. There has to be some leftover sometimes of a lock file.

@florent Only one single backup job every 2hrs (multiple VM's). Running fore more than 1year without issues (not counting the initianl cbt stuff).

@florent No other backup is running as I mentioned!

And "Merge backups synchronously" is on as mentioned.

This is not it.....

@olivierlambert @Business with XOA no. Only HomeLab with XO but it has been rockstable until this.

@olivierlambert That's the last update I did yesterday.....

Just updated now to latest: Xen Orchestra, commit ef636
Master, commit ef636

@olivierlambert XO Xen Orchestra, commit 987e9
Master, commit ef636

@manilx This has started 2 weeks go or so. But it's getting worse. I'm pretty sure it started with one of the XO updates..... As nothing else was changed.