@rtjdamen hey there, did you ever modify in the POOL advanced tab at the bottom the BACKUP network & MIGRATION network ? fiddle with these, note what they are actually set, and change them if possible between each change, check your SR stats @florent could explain better how SR stats use the backup network to get the RRDs... I guess you have stalled RRD tasks too ? in tasks list ?

@fcgo if the storage is shared : the export is done by one of the host of the pool If the storage is not the export is done by the host with the storage . Same for the host receiving the data The command channel, as you said, is always the master to the xoa (and eventually xo-proxy) So for a replication : [source SR] => source host =https export call=> xoa / xo-proxy =https import call=> target host => [target SR] if the xoa is running on the host doing an export, it does not use the physical network the network use between the host and SR is dependent on the storage used

It sounds like you tried to switch the pool master to a host at a lower xapi level. Had the host that you designated as the new pool master already been patched?

Exactly and that's what does the Rolling Pool Update feature

I also added windows build so that people can help with testing also on windows. It's a static build, no need for installer, just single zipped .exe file. No dependencies.