@acebmxer Good to know, that would change my feelings on that solution. We're a K12 school so money is not overly abundant.

This seems to be specific to XenServer guest agents?

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.

@hoerup Dang, how did I miss that. Thanks and my apologies! Graham

@gcpeters4 said: @john.c This is a good idea as well. If the previous suggestion of trying to do a DNS round robin approach doesn't work, this may be my best option. Thanks for taking the time to provide your suggestion! By the way my suggestion is recommended best practice from Microsoft for their Active Directory software and/or technology. My suggestion will be more likely to work if your DNS servers and requests have issues with Round Robin configuration. Plus with my solution you can easily add more servers as domain controllers to the cluster, as required and use replication to keep them consistent and up to date.

@florent OK cool, thank you for the info.

@tsukraw said: Hey guys, Looking for some help at understanding auto power on as the documentation possibly looks to need some refreshing. https://docs.xcp-ng.org/guides/autostart-vm/ From the Xen Orchestra, the guide does not mention the pool level it is only under the CLI that it mentions the pool level. Just looking for some clarification. In order for auto power on to function, we need to enable it on the pool level, and then per VM correct? If you have auto power on enabled at the VM level and the pool level disabled, the VM level is ignored, correct? What is actually triggering the power on? Is it XOA or the host itself? I am assuming the host itself, just looking for clarification if XOA VM was part of the systems that went offline, should we expect to see it auto power back on if it is set to auto power on. What determines the start order for auto power on when you have multiple VMs on a host? Thank you!! Yes, it needs to be enabled at pool level and at VM level. I tried once at only enabling at the VM level and it didn’t auto power on, as it wasn’t enabled at the pool level, it started auto powering on once it’s enabled at both levels. It’s configuring a XAPI value as this occurs at the Xen level (virtualisation server). Xen Orchestra is just making this value visible with a nice UI interface toggle.

@jvanabra "merge synchronously" option is there for log purpose. When you click on your backup job you can get all logs from this job here: [image: 1777971428328-78941893-5585-486a-b9bc-7d4c59873aa6-image.jpeg]

@bvivi57 said: getLicenses do you have xostor installed ?

@lknite Hello, sorry if replying in this old thread looks odd... but I wanted to share that we are starting to work on supporting Cluster API. We have an internal proof of concept: /home/nathanael/Images/Captures d’écran/Capture d’écran du 2026-05-05 17-12-22.png[image: 1777999357100-a9596fde-e251-4996-8fc9-3f8e208f9f01-image.jpeg]

I solved the problem by installing and setting up a new Ubuntu Server. I exported the XO configuration from the old server and imported it onto the new one. What can I say—the backup started working again right away.