@olivierlambert Correct. Running commit 4944ea902ff19f172b1b86ec96ad989e322bec2c works.
Top contributor
Posts
-
RE: Continuous Replication jobs creates full backups every time since 2025-09-06 (xo from source)
-
RE: What Are You All Doing for Disaster Recovery of XOA Itself?
@DustinB Yeah I thought about doing something like this, but then we are getting into overkill costs lol.
My main point behind this post was to get info on what other people are doing, I presumed most are just relying on config backups and will restore it at the other site if needed, which is fine.
I was just also debating about whether or not I wanted the subnets to match between these 2 sites, since that can create some routing headaches, but should still be doable and would make recovery even faster.
@olivierlambert yeah I do use that feature, so that's very helpful! Should make this all doable.
-
RE: What Are You All Doing for Disaster Recovery of XOA Itself?
@Andrew Yeah so I hear you on this, and it all makes sense, I've recovered XO plenty of times in my lab.
But, it still feels more complicated than it needs to be and I feel like there has to be a better solution in place. The idea with disaster recovery sites is relatively quick failover (even if manual). Having to restore XO, then reconnect it to all the servers, reconfigure it's IP addresses, etc... feels like it's more work than it should be to do a restore. Not to mention accessing the other cluster assuming something like complete natural disaster destruction at the primary site.
As for backups, yes, I manage a lot of infrastructure like this, not a noob by any means I promise lol, I'm just trying to improve the way I am going to do this in the future, if possible.
Restoring XOA at another site and then reconfiguring it entirely seems like a lot of work.
-
RE: What Are You All Doing for Disaster Recovery of XOA Itself?
@planedrop I don't think there is a true active/standby XO setup. You can always replicate to a different pool and start/recover it there if you have a failure. You can also just have XO run on a different pool and not have it do anything (ie. backups) but still be able to access pools and restore backups.
As a last ditch total disaster recovery option, I have XO running on a laptop (Windows/VirtualBox/Linux). It is not a true duplicate/backup but does have connectivity (from the office or a VPN) to the needed hosts so I can fix/rebuild/restore. I can start over with new location, new hardware, and recover from off-site backups.
You can always deploy new XCP and new XO in minutes then restore your config... You have backups, right?