@olivierlambert I have seen that part of the documentation and it did not contain a solution for me. I also talked to the community on the Teleport Slack and some staff member tried to solve it, but was unable to. So I hope the Teleport discussion forum on github will lead to some solution, so for not.
So lets please keep this post open as someone here who is using Teleport might see it and answer, while that person may or may not follow the Teleport discussion on github.
@olivierlambert like what ballpark? I used it on 1Gbps.
@olivierlambert said in Migration compression is not available on this pool:
So just to recap, setting it via xe works out of the box right?
Correct.
And now it works again (the toggle in XO) but doesn't change the config when checking via xe ?
No. Toggeling on the UI is also reflected correctly by checking via xe.
After some testing however, no performance difference could be measured between Migration Compression being enabled or disabled.
@olivierlambert there was nothing in the log. I tried setting it per the xe command and using xe I could see that it is on or off, but XO did not show these changes on the UI.
what helped was restarting XO. since then I can toggle it and xe shows the same status.
I cannot enable the Migration Compression on my pool of two 8.3 XCP-ng hosts. The X_O UI says "Migration compression is not available on this pool". Any ideas what could be the reason and how to make it work?
@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.
@stephane-m-dev well, have you tried this on an unraid server with a disk share? if not, you are still missing my point.
the disk share (there the error occurs):
"/mnt/disk3" -fsid=87,async,no_subtree_check 192.168.100.0/24(sec=sys,rw,no_root_squash,insecure) *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash)
the user share (here it works):
"/mnt/user/backup" -fsid=91,async,no_subtree_check 192.168.100.0/24(sec=sys,rw,no_root_squash,insecure) *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash)
please also do not overlook the other problem with the full backup mode when encryption is used: "Trying to add data in unsupported state" (see above)
@stephane-m-dev the folder was positively empty, I explicitly removed all files before adding it as remote. Have you read what I wrote about different share types in unRAID?