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.
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?
@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
@irtaza9 it scans all the VDI's on the SR to see if something has changed, if there's a need for coalesce and so on.
I dont think it will be a big issue if you increase the auto-scan-interval value to lets say 5 minutes (300 seconds), but do remember, that everything regarding the VDI's on the SR will take up to 5 minutes to update, as well as triggering coalesce after removing snapshots.
