There are two kinds of Home Assistant users: those who make backups, and those who will eventually wish they had made backups.
Actually, there is a third category: people who have dozens of backups, proudly displayed in their Home Assistant dashboard, all stored on the same SSD that just decided to retire without notice.
Welcome to the wonderful world of disaster recovery.
Home Assistant has become the control centre for many homes. It manages lighting, heating, security sensors, energy monitoring, EV charging and sometimes even the coffee machine. After years of tweaking YAML, adding integrations and building automations, your installation represents a considerable amount of time and effort.
Losing that configuration can be painful.
Fortunately, Home Assistant has built-in backup functionality, automatic scheduling and support for multiple backup locations. But there is an important distinction between having a backup and being able to recover your smart home.
In this guide, we’ll build a sensible backup strategy, protect the encryption key, keep copies outside the main system and explore how to prepare for a real recovery.
Because the best time to discover that your backup doesn’t work is before you need it.
1. What Does a Home Assistant Backup Actually Contain?
A Home Assistant backup can include configuration files, installed apps, add-on data where applicable, and other selected parts of your installation.
A full backup can include the config, share, ssl and media directories, together with supported app data. You can also create partial backups containing only selected components.
The exact contents depend on your backup selection and installation.
That distinction matters. A backup of your configuration isn’t necessarily a complete copy of everything needed to rebuild your system.
Before relying on a backup, consider what your installation actually needs:
- Configuration: YAML files, dashboards, automations, scripts and integration configuration stored in your configuration directory.
- App data: Data belonging to the Home Assistant apps you choose to include.
- Certificates and shared files: Relevant files stored in the directories selected for backup.
- History and statistics: Database information, if included in your backup.
- External dependencies: Network shares, external services, credentials and hardware that may need separate attention.
A backup does not magically include every external system your smart home depends on. Your Wi-Fi configuration, router settings, separately managed services and physical hardware may require their own recovery plans.
For example, if your Home Assistant installation uses a Zigbee coordinator, restoring the configuration is only part of the job if the coordinator itself has failed.
Official documentation: Home Assistant backups.
2. Enable Automatic Backups
If you are still relying on remembering to create backups manually, let’s fix that first.
Open Settings → System → Backups and configure automatic backups.
Home Assistant supports scheduling backups and retaining a defined number of older copies. You can also configure multiple backup locations, depending on your installation and available integrations.
For most installations, daily backups are a sensible starting point.
Choose a schedule that suits your home. A backup during the night might be convenient, provided your network storage and other destinations are available at that time.
You should also review whether automatic backups are created before updates. A backup taken immediately before a significant update can be especially valuable if the update introduces an unexpected problem.
How many backups should you keep?
That depends on how frequently your configuration changes and how much storage you have available.
For example, keeping seven daily backups gives you a useful recent history. Keeping a few additional copies from before major configuration changes or upgrades can provide another recovery option.
However, retaining seven backups on one disk does not protect you against that disk failing.
Automatic retention helps manage storage. It is not a substitute for independent backup copies.
3. Follow the 3-2-1 Backup Principle
A useful starting point is the traditional 3-2-1 backup principle:
- Three copies of important data, including the original.
- Two different storage locations or media types.
- One copy stored off-site, away from the main installation.
You don’t need an enterprise storage system to apply this principle.
A practical Home Assistant arrangement might look like this:
| Copy | Location | Purpose |
|---|---|---|
| Original | Home Assistant system | Normal operation |
| Local backup | NAS or separate storage device | Recovery from system disk failure |
| Off-site backup | Secure cloud storage or another location | Protection against theft, fire or major hardware damage |
Home Assistant supports network storage and Home Assistant Cloud backup destinations. Other cloud storage options may be available through supported integrations.
A NAS in your home is a useful improvement over keeping every backup on the Home Assistant machine. But it won’t protect you from every disaster affecting the house.
Likewise, synchronising files to another device is not automatically the same as maintaining a proper backup history. If unwanted changes or deleted files are synchronised everywhere, you may lose your recovery options.
Choose a solution that provides suitable retention, access controls and, where possible, protection against accidental deletion or ransomware.
Official guide: Home Assistant backup storage and configuration.
4. Don’t Lose Your Backup Encryption Key
This is one of the most important details in the entire process.
Home Assistant backups are encrypted, and the backup emergency kit contains information needed to restore encrypted backups, including the relevant encryption key.
If you lose access to the key required for an encrypted backup, you may be unable to restore it.
During automatic backup setup, Home Assistant offers the option to download the emergency kit. You can also obtain the relevant information through the backup settings.
Store the emergency kit somewhere safe outside your Home Assistant installation.
A password manager with secure file storage, or another appropriately protected location, can be useful. Consider maintaining a separate protected copy so that losing your computer doesn’t also mean losing access to the key.
Remember that changing your encryption key affects future backups. Older backups may still require the previous key, so preserve the keys needed for the backups you intend to retain.
Home Assistant updated its backup encryption in 2026.4 with the SecureTar v3 format and stronger modern cryptographic defaults. Existing backups remain supported, but it’s worth keeping your installation up to date and following the official recommendations.
Never store your only copy of the emergency kit inside the same Home Assistant installation you’re trying to recover.
That would be a little like locking your spare house key inside the house and calling it a security strategy.
Official references:
5. Make Sure Your Backups Are Actually Accessible
A backup that exists but cannot be found when needed is not particularly helpful.
Open Settings → System → Backups and review the available backups and their locations.
Check the following:
- Does the latest backup exist?
- Is it stored in the locations you intended?
- Is the backup destination still accessible?
- Are old backups being retained as expected?
- Do you have the encryption key needed for restoration?
- Can you access the backup without relying on the Home Assistant machine?
If you use a NAS, verify that the network storage is reachable and that the relevant share has sufficient free space.
If you use cloud storage, check that the backup is visible in the expected location and that your account remains accessible.
For additional reassurance, download a backup to another computer and verify that the file can be accessed. This is a useful check, although it does not prove that the backup can be restored successfully.
A successful backup operation is a good sign. A tested recovery is stronger evidence.
6. Test Your Recovery Plan
This is the step that separates a backup strategy from a hopeful collection of files.
You do not need to deliberately break your main Home Assistant installation to test recovery.
Instead, consider testing with spare hardware, a suitable virtual machine or another isolated environment.
A practical test involves the following steps:
- Identify a recent backup and confirm that you have its required encryption key.
- Prepare a separate, compatible Home Assistant installation.
- Follow the official restore procedure and select the appropriate backup.
- Confirm that the configuration loads and that the expected apps and settings are present.
- Check dashboards, automations, scripts and important integrations.
- Document anything that requires manual intervention.
Be careful when restoring backups. A restore can overwrite the configuration and data of the target installation. Never use your production instance as a test environment unless you deliberately intend to replace its current state.
Some integrations may need additional attention after restoration. Devices may be temporarily unavailable, network storage may need to be reconnected, and external services may require authentication.
Radio hardware deserves special consideration. If you migrate to a different Zigbee coordinator or Z-Wave controller, the recovery procedure may involve additional steps beyond restoring Home Assistant’s files.
Your goal is not necessarily to prove that every device works instantly. It is to discover what recovery involves before an actual failure forces you to learn it under pressure.
Official guide: Restoring a Home Assistant backup.
7. What If Your Home Assistant Machine Dies?
Let’s imagine that your system disk fails completely.
Your Home Assistant installation is offline, and the machine cannot boot. What now?
With an external backup, the encryption key and a little preparation, the recovery process becomes much more manageable.
A typical recovery plan looks like this:
- Install a compatible Home Assistant system on replacement hardware.
- Access your backup from a separate storage location or computer.
- Restore the selected backup during onboarding, following the official instructions.
- Reconnect required network storage and external hardware.
- Check integrations, devices, automations and logs after restoration.
You don’t necessarily need identical replacement hardware, but you should verify storage requirements, supported installation methods and any hardware-specific considerations.
Home Assistant’s documentation explains how to restore a backup onto a new installation, including when migrating between different types of hardware.
The most important preparation is having everything required for that process available outside the failed machine.
A written recovery checklist can be surprisingly valuable. Include the location of backups, the location of your emergency kit, the hardware you need, and any important external dependencies.
Future you will appreciate it.
8. Build a Small Backup Maintenance Routine
You don’t need to spend every Sunday managing archives. A short, regular check is enough to catch many problems.
Once a month, review your backup history, storage capacity and retention settings. Confirm that the external destination is available and that your emergency kit remains accessible.
After major changes to your configuration, check that a recent backup exists before making additional changes.
Before a significant Home Assistant update, make sure you have a suitable recovery point. Home Assistant can create a backup before an update when configured to do so.
And periodically, test the recovery process in a separate environment.
These habits work particularly well alongside a Home Assistant Health Dashboard. The dashboard can highlight backup status and storage issues, while a recovery checklist ensures you can act on the information.
Final Thoughts
Backups are essential, but they are only one part of protecting your smart home.
A reliable strategy combines automatic backups, independent storage locations, secure encryption-key management and a recovery plan that you have actually tested.
Start with daily automatic backups, keep at least one copy outside the Home Assistant machine, protect your emergency kit and document how you would recover after a hardware failure.
You don’t need to implement every possible enterprise backup technique. You simply need to make sure that a failed disk, a broken update or an unfortunate hardware accident doesn’t force you to rebuild years of work from scratch.
Because your smart home should be smart enough to turn on the lights.
And your backup strategy should be smart enough to bring those lights back after a disaster.
Some of the links in this article are "affiliate links", a link with a special tracking code. This means if you click on an affiliate link and purchase the item, we will receive an affiliate commission. The price of the item is the same whether it is an affiliate link or not. Regardless, we only recommend products or services we believe will add value to our readers. By using the affiliate links, you are helping support our Website, and we genuinely appreciate your support.
