Ok I think I have resolved the issue. It appears that if you do not activate either a paid license or the trial, it fails with the import because many of the features are not active until you enable the license and then update the XOA appliance.

Once I activated the trial and then updated the appliance again, I was able to successfully import the backup.

My hesitation with activating the license before importing the config as the licenses are bound and I didn't want to have to redo the setup if the config did not import.

Again, it looks like I need to activate the license first and then I can import the config.

Ok I think I have resolved the issue. It appears that if you do not activate either a paid license or the trial, it fails with the import because many of the features are not active until you enable the license and then update the XOA appliance.

Once I activated the trial and then updated the appliance again, I was able to successfully import the backup.

My hesitation with activating the license before importing the config as the licenses are bound and I didn't want to have to redo the setup if the config did not import.

Again, it looks like I need to activate the license first and then I can import the config.

@acebmxer I already did this several times. I have a running job that takes a backup of the config every night and have the last 7 configs kept. I also did a manual config backup and tried that import as well. Both come up with the same error message on the XOA appliance. Error while importing config.

I have both versions of the backup config files. The manual backup which is just one file and the automated config backup which is two files. Any of the files that I try give the same error message that there is an error while importing the config. I also don't see any information in the logs.

I have also tried 3 separate times and imported the XOA appliance to start fresh.

Hello,

I migrated our smaller DMZ VM cluster from VMware to XCP-NG and XOA a few months and have been using the community edition of XOA. Everything has been going great with no complaints.

Recently I got approval to get a paid service subscription to Xen Orchestra. I have the licenses and imported the new OVA using the XOA deploy site. It successfully imports the VM and I can log in and connect my Vates account. My issue comes from importing the backup config that I have from my community edition to the new XOA.

Everytime I try to import it, it says there was an error message importing. It seems to connect to one of the pools but none of the other information comes over. Missing backup jobs I created, missing remotes for backup jobs, plug in configurations.

At first I thought it was because it was on a different version of XOA. I noticed that it uses the stable channel by default and it showed XOA being 6.2 I think. The community edition XOA we are running is running the latest 6.4. I did change it to use the latest channel and it did upgrade to 6.4 but it still said there was an error importing the config file.

Is it possible to import our config from our community edition into the XOA appliance? Apologies as this is my first time actually using this edition of the XOA server.

@tsukraw No worries! Just glad that we can all help each other out!

@florent Hello,

So I am not sure what changed but it looks like the continuous replication should be working as intending now. I did reconfigure the schedule a last time before I posted last and let it run. I can see where it was still doing the full backups and where I stopped it by restarting the XOA. It seems then after the reboot and saving the schedule again it appears to working.

It is now showing delta backups and the transfers are much smaller.

I wish I had a better idea what would have caused it to work but I will continue to monitor it. I would say for now my issue is resolved.

@florent Hello!

The VMs are replicating within the same pool. The pool only has 2 hosts and all is taking place within the same pool.

All the VMs currently live on host 1 with the local storage. The VMs are set to replicate to the local storage on host 2.

I am currently working on trying to setup continuous replication from one host to another. I have the process setup and it does replicate the VMs from the local storage of server 1 to local storage of server 2 but every time the job runs, it runs a full back up. It was my understanding that it runs a full backup the first time and then does a delta every time after based on the schedule.

I am currently on this version of the XOA vm.

I have done the following to try and troubleshoot it.

• Set the replication retention to both 1 or more.
• Verified that Force Full Backup option is NOT checked on the schedule.
• Verified that the Purge snapshot data when using CBT. is NOT checked. I don't currently use CBT as well but made sure it was unchecked as well.
• Full backup interval is not set.

I could also be mistaken on how this process should be run. Any help would be appreciated.

@xisco thanks for the advice. I did try attaching the disk to an existing VM I had running but it still boots to the same screen.

I was able to resolve the issue. It was a permissions issue on the NFS server. It was running on an Ubuntu 18.04 server and running the command chown -R nobody:nogroup.

I am currently running a fresh Xen orchestra install and created an Ubuntu 18.04 NFS server. I can mount the share on the XOA vm via the command line and make files and folders but when I attempt to connect via the web console, I am told that I do not have access. In the /run/xo-server/mounts folder, I can see each of the 3 attempts I made via the web console. It creates the folder with my username but root permissions is the one that was mounted via the command line with SUDO. Now I can browse each of those folders and see the test folder I created but if I attempt to make a file or folder without root permissions, it fails.

Does anyone know what the correct permissions the /run/xo-server/mounts folders need to have?