Home Assistant Backup Download

The Backup integration allow you to create and download backups for your Home Assistant Core and Home Assistant Container installations. This backup file can be used if you migrate to Home Assistant Operating System.

Backup of your Home Assistant and add-on data and configuration. They are stored in a compressed archive file (.tar). Backups are made from the backups panel under Settings > System > Backups. There is also a service available that allows you to trigger the creation of a backup from an automation. By default, backups are stored locally in the /backup directory.

Download File 🔥 https://fancli.com/2y2DfG 🔥

Migration: This procedure also works if you want to migrate from one device to another. In that case, use the backup of the old device on the new device. The target device can be a different device type. For example, you can migrate from a Raspberry Pi to another device.

This will become a target. You can use it in service calls or when manually creating a backup. The first storage you add of this type becomes your new default target. If you want to change the default target, check out the documentation below.

Snapshots. Create a snapshot in the hass.io control panel and download it from Samba in the backup share folder. This way if something does go bad, you can just reinstall hass.io fresh and upload/restore your snapshot to be back up and running.

Careful with snapshot, they do not back up everything. I recently had to re-install hassio, I thought it would be piece of cake as I had plenty of backups, but when I wanted to restore I found that pieces are missing. I ended up re-imlementing the whole thing, took me a week. My python scrips were gone, the www directory, packages and few other files. Or is it just me?

Since then, I do backup, but I also copy the files via robocopy to my cloud account.

To manually create a backup, navigate to Settings > System > Backups and click + Create Backup:

If you choose to create a Full Backup, give it a name and an optional password protection. If you leave it empty, Home Assistant will automatically assign a timestamp as a name to your backup.

If you choose to create a Partial Backup, select any addons, integrations and folders that you want to keep, give it a name and a optional password.

The Add-on will automatically start to Sync any existing backups you might already have in Home Assistant. On the left side of the screen, you can overview how many backups you have in Home Assistant and how many you have uploaded to Google Drive.

The Home Assistant Google Drive Backup Add-On has a bunch of built in settings we can tweak. Naturally, you do not want to keep the all the backups the Integration creates neither in your Home Assistant Instance or your Google Drive account.

By default, the add-on is set to keep 4 backups in Home Assistant and Google Drive. I personally like to keep only 1 on my Home Assistant server and 4 in Google Drive. I feel like there is no need for more, but you can adjust this to suit your needs.

First, create the backup like you normally would or click the Actions menu in the corner and select + Create backup. Than, click the backup in the UI and click Never Delete in the popup:

If you click Show unused optional configuration options, the add-on will add two new settings in the menu. One of which is the Allowed hours when the backup should be performed (e.g. 3AM) and the other is a Backup Instance Name, used to distinguish between two different Home Assistant installations backing up to the same account.

Click Save and you are done!

If you would rather save your backups locally and not depend on the cloud, you can setup the Samba Backup Add-on by thomasmauerer. This method is completely local, does not depend on an internet connection, but requires a Samba Share server deployed on your local network.

This add-on includes a sensor for Home Assistant which reflects the current status and additionally has some useful statistics within its attributes. No configuration is necessary in order to use the sensor. The name of the sensor is sensor.samba_backup.

Wherever you look, the 3-2-1 rule is mentioned as essential practice for treating your backups. This rule says to keep 3 copies of your data on 2 different devices/mediums with 1 off-site storage solution.

But I have on issue: i use a zwave hat for my raspberry which needs a config change in /boot/config.txt which is not covered in the backup.

Any chance to backup also this?

Now i have to do the changes in the file before doing a restore.

100% guess:

You had SSL configured before (which is included in your backup)

The webpage you are using to restore is HTTP (non-SSL), so when it completes, that webpage refuse to answer to non-SSL request as the restored config are using SSL.

One the most important aspects of maintaining Home Assistant is regular backups. Implementing the 3-2-1 backup rule with Home Assistant is now easier than ever, with the 2023.6 release. The 3-2-1 rule states you should have (at least) 3 copies of your data (production + 2 backups), on two different media types, and a copy off-site. This post will walk you through how to just this with Home Assistant OS (HAOS), using your local NAS and a Google Drive account.

6. On the Confirm Settings page click Next.

7. On the Configure user permissions page, give your new Home Assistant backup account read/write access. Click Apply.

5. Go to Settings -> Backups. In the upper right hand corner click on the three dots. Select Change default backup location.

6. Pick your NAS share from the list and click Save.

The Home Assistant Google Drive Backup add-on is one of the best, if not THE best, HA backup add-on you can use. It is highly configurable, is regularly updated, and seems pretty bullet proof. So we will using this add-on to do our cloud replicate (the off-site backup). It can also help maintain the number of backups stored on your NAS.

Now that HA has NAS backups, and the Google Drive Backup add-on can help manage those backups, we need to quickly discuss a backup strategy. Prior to NAS backups, I significantly limited the number of local backups (inside HAOS) and relied on the cloud for longer term backups.

I will only use backups stored in Google Drive as a last resort backup in case my HAOS server and NAS suffer a catastrophic failure (fire, flood, earthquake, etc.). Basic Google Drive accounts are limited to 15GB of storage. And you might already be using some of that storage space for other content, leaving less than 15GB for HA backups. If your main Gmail account is really short on storage, you might want to consider a fresh Gmail account that is dedicated to HA backups.

12. If everything looks successful, click the blue Plus in the lower right corner. Enter a backup name and click CREATE BACKUP.

13. After the backup is done, in the upper right corner click on Actions, then Open Drive Backups. Review your Google drive to ensure the backup appears.

14. On your NAS navigate to your HA backup share and ensure a new tar backup was created.

15. After your first scheduled backup is supposed to run, review the contents of both your NAS and Google drive to ensure the backups are where you expect them to be.

With this entity you can setup an automation that alerts you to any backup failures. Just create a new automation, use the Backups Stale entity, and use Problem state. You can then define any action that you want, such as sending an email, a text message, or any other notification method you have defined in Home Assistant.

I strongly urge you to do periodic test restores of your HA backups. To do this, I would setup a fresh non-production instance of HAOS. You could use Proxmox, an old PC, or a desktop virtualization solution like Parallels, Fusion, or VMware Workstation. Install the latest HAOS, then perform a restore using your latest backup. Ensure that it it works as expected.

Yesterday, the card on my Raspberry Pi 3B plus started to fail. I imaged a new Home Assistant OS onto a card, popped it into the Pi, and as soon as it was ready, I restored from my latest backup. It was painless!

Data loss is inevitable, and may occur due to hardware and software failures. However, with regular backups, you can restore the data and critical applications, such as Home Assistant, back to their original or last working state. Here we'll explain a few different methods to create full and partial backups of your Home Assistant server on a local drive and cloud storage. You will also learn how to schedule automatic backups and use these backups to restore your Home Assistant server after a failure.

Alternatively, you can click on the three dots at the top in the automation window, choose Edit in YAML, paste the following code to create an automation for backup, and click Save.

If something goes wrong with your Home Assistant Server, such as damage to your Configuration.yaml file or if the servers start acting up, you can install the Home Assistant Server on a Raspberry Pi or Docker and then upload the last backup to restore the Home Assistant to its normal working state.

Ravi is an expert tech explainer, an IoT enthusiast, and a Linux lover with a background in big data and app development. He's a tech geek with over 7 years of experience in creating DIY tech and how-to guides on data recovery, file repair, Exchange Server, Outlook, Microsoft 365, Windows, Mac, Linux, iOS, and smart home. ff782bc1db