High Availability in Home Assistant

Installation
11

Hey @ryan-ronnander, thanks for posting the blog, I have already tried a test setup and it works as you described, except from the part of migrating from a Virtual Machine (VM) using the official KVM (qcow2) disk image provided by the Home Assistant Team.

When the docker is installed I do not see at the first screen the “Restore from backup” option for some reason. I also tried to scp everything from the config directory of the source server to the /mnt/home-assistant of the primary new server from your example, but there were issues (I guess sql was not happy with such approach).

  1. Any clues on how to migrate to the high available docker setup?
  2. Any ideas on how to use DRBD to use the non-docker setup that I currently have and just add another VM?

Thank you in advance!
Dominicus

20240531 2148 EDIT:

After some further research::

  • There is no Web GUI method implemented to restore from a backup for home assistant docker version.
  • The scp seemed to have worked well (*except that I had to add a new user via CLI hass command)
  • The docker version of home assistant is not supporting add-ons; one way of using ex. Zigbee2MQTT add-on is to make another docker. (ex. Living without add-ons on Home Assistant Container )

Would extending the following code from your blog Home Assistant High Availability and instead of x1 High Available docker having x3 would make any sense? How common is to use multiple dockers in such High Availability configurations?

# Home Assistant resource
primitive p_docker_home-assistant ocf:heartbeat:docker \
    params image="ghcr.io/home-assistant/home-assistant:stable" \
        allow_pull=true \
        name=homeassistant \
        run_opts="--privileged -e TZ=America/Los_Angeles \
        -v /mnt/home-assistant:/config \
        -v /run/dbus:/run/dbus:ro --network=host" \
    op start interval="0s" timeout="120s" \
    op stop interval="0s" timeout="120s" \
    op monitor interval="20s" timeout="100s"

# MQTT resource
primitive p_docker_mqtt ocf:heartbeat:docker \
    params image="eclipse-mosquitto:2.0" \
        allow_pull=true \
        name=mqtt \
        run_opts="-v /mnt/mosquitto-data:/mosquitto \
        -p 1883:1883 -p 9001:9001 \
        --network=host \
        mosquitto -c /mosquitto-no-auth.conf" \
    op start interval="0s" timeout="120s" \
    op stop interval="0s" timeout="120s" \
    op monitor interval="20s" timeout="100s"

# Zigbee2MQTT resource with serial over network
primitive p_docker_zigbee2mqtt ocf:heartbeat:docker \
    params image="koenkk/zigbee2mqtt" \
        allow_pull=true \
        name=zigbee2mqtt \
        run_opts="-e TZ=Europe/Berlin \
        -v /mnt/zigbee2mqtt-data:/app/data \
        -v /run/udev:/run/udev:ro \
        -p 8080:8080 --network=host" \
    environment="ZIGBEE2MQTT__SERIAL__PORT=tcp://192.168.1.12:6638" \
    op start interval="0s" timeout="120s" \
    op stop interval="0s" timeout="120s" \
    op monitor interval="20s" timeout="100s"