@florent can you confirm for the replication job ? Thank you

@wilsonqanda HAHA. problem resolved instantly for me on last SR I had the troubles [image: 1767986291861-6593f43e-d85b-4865-8797-e9f949e07b88-b255d2fd-7e51-4e65-b85f-05a24582bbf0.png] playing with the "rescan all ISO SRs" made the guest tools iso reappear AND ALL MY OTHER VDIs ON THIS SR/HOST that were invisible donnnnn't ask me HOW... [image: 1767986447067-01c9cf72-44fb-4e96-abd5-c39290d20784-535a410a-4f18-4281-a1d9-23113829e6c4.png] but this trick didn't work on other local RAID5 SR that have the problem

It isn't clear why you are trying to change the master at this time. Can you explain? What is the status of the two hosts that have been patched and rebooted?

@Bastien-Nollet I used vhd-cli info without the --chain option and it worked correctly. Thank you. But vhd-cli info isn't the solution for me. From what I've researched so far, it seems that to have cross-control of the backups, I'll have to use xo-fuse-vhd to mount the backup aliase.vhd and then run dd if=/mnt/vhd0 of=/dev/null bs=4M status=progress to verify the consistency of all the blocks in the backup. The problem with this mechanism is that each time the verification is run, it checks the entire VDI and not just the incremental blocks of the aliase.vhd file, making it very resource-intensive for daily use. Any suggestions would be welcome.

If I remember some previous discussions, EVE-ng uses some features that doesn't work in nested mode with Xen.

@majorp93 I've updated and added a node.js-installation to the role. Targeting the LTS-24 version. I hope you find it to your liking.