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.

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

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

@julienXOvates Got it. I didn't get a chance to work on this over the weekend, so sometime this week, I'll just bounce the host and see if it comes back. Right now, while I can SSH into it, the admin console appears to be frozen and unresponsive (over iLO).

@dkg Please also note that you should not use @jul1an ISO installer on production environment. Only on test env where you can afford to break things and lose data.

@stormi That is quite possible. I'll open a ticket for further investigation.

Hello @codemercenary In theory Xen is NUMA aware (See https://wiki.xenproject.org/wiki/Xen_on_NUMA_Machines) so you would leave memory interleaving option of the BIOS off so that Xen does what it thinks is necessary. But these kinds of settings are very very workload sensitive and in fact it's usually a good idea to just test what works best for you. Regards, Yann