Best Practices XO Location
-
Should XO be installed inside of a pool or on a separate host?
Currently, we have three servers in an HA pool with shared storage. We will continue to expand this beyond one pool, but would it be better to install XO on its own host or inside the pool?
-
Hi,
There's no golden standard. But you can backup XO config with XO (or even XOA entirely). It's not hard to restore a fresh XOA and even if you lost the config, you'll be able to find back all your previous backups without any issues. So as you can consider XOA as disposable, it's up to you to decide what's best for your environment in terms of simplicity, risks and how-to get back on your feet.
In my own production at Vates, our XOA is sitting on top of the production pool for simplicity reasons. If you want to host it elsewhere, it will work perfectly fine too.
-
gofm I run XO on the pool and it's good.... but I have a few backup options:
- Run a second VM XO on the same pool
- Know how to force a manual start of XO on the pool in case of trouble
- Run XO as a VM on another host/pool (or a small Linux PC or VirtualBox)
- Run XO as a VM on windows (VirtualBox)
- Quickly manually deploy a new XOA on a pool (without needing any config).
- Use XO-Lite (soon). Available because the XCP host has booted.
I use one main XO on the pool that does all the backups and normal operations. The backup XO VMs just sit and do nothing until I need to use XO outside of the pool (or I screwed up the main XO install).
-
Thank you for the feedback. That is very helpful!
-
I do run XOA on its own dedicated host/dedicated pool, so the xcp-ng cpu scheduler does not cause issues with other busy production VM's while backup tasks are happening. this also allows XOA to use 100% of cpu cores making backups (especially with compression on) faster.
xoa does DR back up to the primary pool in case something happens to the host its running on.
