# Copy/paste the lines between the '-' and save with Ctrl+X # Also copy the 'shebang' starting with #! # - #!/bin/bash readonly SOURCE_DIR = '/opt/homeassistant/config' readonly BACKUP_DIR = '/mnt/backup/homeassistant' readonly BACKUP_PATH = ' $ ' docker start homeassistant You may need to install it on your system first. We use rsync to copy the data, as it has some nice features which are ideal for doing periodic automated backups. We can achieve this using a small script, which we could even run periodically. So a backup of this folder, would keep our HA data safe.īecause a running Home Assistant could cause inconsistencies in the backed up data, it’s a good idea to temporarily stop the HA Container while copying the data. This folder is exposed to our Docker volume at /opt/homeassistant/config. The most important data within Home Assistant is stored within the /config folder inside the container. Creating a Home Assistant Backup Backing up Docker volumes ¶ In case an upgrade fails, we can restore Home Assistant using the backup file to rollback the changes.

Once the backup is created, download it to your local system by clicking the ⬇ button to the right of the created backup.

Click the + Create Backup button on the bottom-right and Create in the pop-up window.

In Home Assistant, go to Settings > System > Backups.

With this integration enabled, taking a backup is a simple 3-step process: If you did remove this line, you can selectively enable the backup integration by adding backup: to the HA configuration.

Unless you removed the default_config: entry from your configuration.yaml, the backup integration is enabled by default. Home Assistant Backup Integration ¶Ī first, and obvious, choice is using the built-in backup integration.

Let’s check out a few options for backing up Home Assistant Container. The September 2022 update for Home Assistant just dropped, so it’s time to upgrade.īefore jumping to upgrading, however, it’s always a good idea to pause and create a backup first.

Fbackup 7