Your backup is a stream, doing backupressure (or not). As explained in the linked topic, it depends on dozens of different parameters.

You might try to use NBD with 4 concurrent download, that might be better though, because I'm betting your bottleneck is likely XAPI export speed.

Hi @Houbsi, good question. This is how it works:

any XO instance that is connected to a pool will add some information about itself to the pool's metadata XO Lite reads that information to know the URL of XO's UI

In xo-server's config, you can force XO to report a custom URL instead of raw network information:

[http] publicUrl = 'http://example.com'

However, at the moment, XO Lite doesn't support it, but it's coming soon: https://github.com/vatesfr/xen-orchestra/pull/7849 🙂

And @olivierlambert, yes, for now, any XO instance, whether it's an XOA or not, reports itself on the pool and we simply pick the latest one. But we can definitely implement something smarter in the future if necessary.

pdonias opened this pull request in vatesfr/xen-orchestra closed feat(lite/XoaButton): support `xo-server`'s setting `http.publicUrl` #7849