@frb94 Just leaving it on 24/7 winter is here now or so we thought (its 75f outside today) . If there is any update on this i would try again. but as it seems you are having the same issue i did then, it does not appear to be fixed.

@Octopuss Follow this post - https://xcp-ng.org/forum/topic/9964/xcp-ng-8-3-updates-announcements-and-testing for host updates. This where where the rolling pool update would come into play when using more then one host. also look here - https://xcp-ng.org/blog/

@poddingue said: While you experiment, do the failing VMs have something in common? The same source SR, for example, or a mirror target keeping a different retention than the source. There are two backup jobs that are failing. One from Ark (local) to Synology, and one from Ark to S3. It seems to be the same VMs failing each night, but interestingly, there are some that fail to Synology but succeed to S3 and vice-versa. There are 9 VMs that fail for both. They do not all share the same SR. The backups on Ark are coming from several delta jobs that run daily, weekly, and monthly. Retention are different for all those.

Thanks for the information, @ph7 . That's a typo, for sure.

@nick.lloyd that's something out of this plugin, that's ceph native. most clusters should run on msgr2 native. which ceph versions are you running?

Just as an update on this. Did get the migrations working. Still haven't gotten the backups working. Pool is still stable otherwise. Have managed to get backups by using Veeam so it's not to much of a problem.

@ludalm13 the PCI-DSS Requirement 10 part helps your case, I think, because it turns this from a nice-to-have into something an auditor will ask for. You're not the only one asking, either. The Feeder request @dknight-bg linked is at four votes now. I'll also point the XO backend folks at the PR directly, a tag in a forum thread is easy to miss in a busy week.