@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?

So I remade the VM twice. Once with 18.04 template which I have used before and another with the Windows 2016 template. Neither of them work as well. Still boots up to the same screen that is shown in the first post.

@xisco Thanks! I did use the CentOS 8 template when creating the VM. I'll try one of the templates you suggested when I get home tonight.

I also have the same issue. VGA was enabled by default but I did try disabling it. I also did try switching from BIOS to UEFI but doesn't boot at all.

If I do the shutdown command it still gracefully shutsdown the VM so it seems like it is still running but the GUI doesn't respond in CentOS 8.