Thanks, that helps. Some VMs fail to the Synology but pass to S3, and some the other way round. So I think the backups on Ark are probably fine (they pass health checks, as you said at the start) and it has more to do with what each target already holds, but I could be wrong. I'd also flag the several delta jobs with different retentions all feeding Ark, I just don't know the mirror code well enough to say whether that matters. @Team-XO-Backend, posts 6 and 10 have the log and the pattern if someone gets to this one.

Maybe, the view from hypervisor level would be interesting, too: # xenstore-ls -f | grep -i driver Will list the drivers for each domain. # list_domains Gives the VM UUID for each domain id.

@blueh2o said in Health check scripts. Where is the example?: xen-orchestra/backups/docs/healthcheck example/wait30seconds.sh that would be here https://github.com/vatesfr/xen-orchestra/tree/master/%40xen-orchestra/backups/docs

Ping @thomas-dkmt for better doc clarity about it.

@florent increasing the timeout value was the solution. Thank you.

Additional info: uuid ( RO) : 127a8a7b-e277-27dc-802f-7f779676e18e name-label ( RO): Async.VBD.eject name-description ( RO): subtask_of ( RO): <not in database> subtasks ( RO): resident-on ( RO): 74e89397-c334-43f5-8322-5331c31ae368 status ( RO): pending progress ( RO): 0.000 type ( RO): <none/> result ( RO): created ( RO): 20251106T19:44:14Z finished ( RO): 19700101T00:00:00Z error_info ( RO): allowed_operations ( RO): current_operations ( RO): other-config (MRW): debug_info:cancel_points_seen: 1

@DustinB with Easyvirt integrated in the stack