XO High Availability

irtaza9

AFAIK, Xen Orchestra (XO) is stateless and relies on Redis for database operations. What happens if my XO instance goes down?

Will all users created in XO be removed?
Will it erase all ACLs assigned to each user?
Will it erase all self-service configurations?
If we restart XO and reconfigure the pools, will it change the UUIDs of pools, hosts, or servers?
Will existing VMs and their configurations remain intact, or will they need to be re-imported?
Will the connection to XCP-ng hosts be lost, requiring manual reconfiguration?
Does XO store any persistent data that needs to be backed up to prevent loss?
If XO is restored from a backup, will it automatically reconnect to the existing XCP-ng infrastructure?
How can we ensure high availability for XO to prevent disruptions?

DustinB

@irtaza9 said in XO High Availability:

AFAIK, Xen Orchestra (XO) is stateless and relies on Redis for database operations. What happens if my XO instance goes down?

Will all users created in XO be removed?

Will it erase all ACLs assigned to each user?

Will it erase all self-service configurations?

If we restart XO and reconfigure the pools, will it change the UUIDs of pools, hosts, or servers?

Will existing VMs and their configurations remain intact, or will they need to be re-imported?

Will the connection to XCP-ng hosts be lost, requiring manual reconfiguration?

Does XO store any persistent data that needs to be backed up to prevent loss?

If XO is restored from a backup, will it automatically reconnect to the existing XCP-ng infrastructure?

How can we ensure high availability for XO to prevent disruptions?

Create a backup of your configuration via the backup tab (or manually) and export it somewhere safe.

You can then import the configuration on a new system and be back in the same working order.

irtaza9

@DustinB We have a redis/valkey cluster deployed and I want to use this redis/valkey for my XO where do I have to configure the connectivity? I do not want put the load on the same VM where XO is deployed.

I want to have HA between my XO's like this (It's must irrespective of state and backups)

How the syncing will behave between n instances of XO's? assume one request is served by xo1 will this change be visible to xo2? vice versa.

irtaza9

@DustinB

I deleted all data from redis and now I am not able to access anything. Please tell me what is stored in redis? Also How can I import the config without having any access to my admin account?

olivierlambert

XO is almost stateless, but there's is like users and some permissions recorded in the config. As told, you can save your config 2 ways:

export the config manually somewhere
use XO backup metadata

With 2, you can even save it in the cloud to easily restore the config from your XOA account. In short, just redeploy an XOA, import the config and you are back on tracks

Danp

@irtaza9 You should be able to login with the default credentials after you restart the xo-server service with systemctl restart xo-server.service.