You have to name them differently. And you need to move your Zigbee devices out of HA. I run my Zigbee2MQTT and Mosquitto outside of HA, using an Ethernet based coordinator.
What you’re looking for @MikeTMechanic is called a ‘high availability’ clustered application. It’s not easy to do this with HA as it would need to be designed from the ground-up to support it. The principal would be that all attached devices would communicate back to a single instance of HA (the shared cluster IP) and then a service in HA would write changes to all instances of HA to ensure consistency. Additionally you would need either a cluster-aware database or some way to syncronise the databases, and then you’d need independent storage systems as well as hosts.
Somebody did do this in the past using Docker and GFS, but it’s not an active project.
In order for High Availability to work you need to research you devices and make sure that they can be handles by multiple hosts at the same time.
Zigbee have already been mentioned, but Z-wave is having the same issue.
Some WiFi devices are also limited on the number of control connection they can have.
The oft chosen solution is to make them to MQTT, which will make MQTT the single point of failure, but it is a simplier service and one which is pretty mature, so bugs are not that common.
MQTT allow for multiple HA servers to connect, thereby making it possible to run two HA instances and keeping them updated.