@olivierlambert Thanks that worked. Kind of obvious approach, still didn't try that

Hello, We tried the compression feature. You "can see" a benefit only if you have a shared storage. ( and again, the migration between 2 nodes is already very fast, we don't see major difference, but maybe a VM will a lot of ram ( >32GB ) can see a difference. If you don't have a shared storage ( like XOSTOR, NFS, ISCSI ), then you will not see any difference because there is a limitation of 30MB/s-40MB/s ( see here: https://xcp-ng.org/forum/topic/9389/backup-migration-performance ) Best regards,

@stephane-m-dev understood. My suggestion regarding the different behavior (does not work with disk share, does work with user share) on unraid would be to put this in a "tip" in the documentation section about setting up Remotes.

@djingo My syslog stopped working (I think after one o the updates) and this bug still exists. If you trying removing it form the Pool or individual hosts in the Pool via XO it will not let you have it as blank. If you ssh in and use xsconsole you can remove the syslog server and but it will not let you specify a port. But once it has been removed from xsconsole you can go back into XO and add in the syslogserver along with a non-default port such as 192.168.2.7:1521 and it will work.

@djingo Have you made any config changes to unraid? That will often make nfs go stale.

Then I don't see why it would be a XO problem FYI, we use JSON-RPC over websockets. Hopefully, someone at Teleport community would be able to pinpoint the problem

OK I got it. I didn't think that the host was using apparmor, but it actually does. So it must be started using --cap-add sys_admin --security-opt apparmor:unconfined Now it works.