Losing a Home Assistant host is not just a storage problem. It can mean rebuilding automations, dashboards, integrations, and the quiet work that made the house feel finished.
A backup file alone is not the payoff. The payoff is a recovery plan: automatic backups, at least one copy away from the Home Assistant machine, a protected emergency kit, and a restore path you have already checked. If you are choosing or replacing hardware first, start with our Home Assistant Green vs Raspberry Pi vs mini PC comparison, then come back here before the next update.
The minimum safe Home Assistant backup setup
You do not need a NAS shopping list to get a useful baseline. Home Assistant’s common backup tasks already cover the practical path.
- Enable automatic backups from Settings → System → Backups.
- Use a daily schedule unless you have a clear reason to run less often.
- Send at least one copy outside the Home Assistant host, so a dead SD card, SSD, or appliance does not take the only archive with it.
- Download and protect the backup emergency kit, including the encryption key needed for encrypted restores.
- Test the restore path before a real emergency—at least confirm a recent backup exists off-host and that you can reach the kit and the official restore steps for your install type.
That five-step plan is enough for most beginners to finish today.
What a Home Assistant backup actually protects
Home Assistant stores backups as encrypted, compressed .tar archives. By default they live locally under /backup.
A full backup can include:
configshare- manually installed or created apps
sslmedia
A partial backup consists of selected default folders and installed apps. That is useful when you want a smaller archive—for example excluding large media—but it is not a complete substitute for a full recovery plan if those folders matter later. Not every installation has the same files, apps, or restore behavior, so treat the backup selection UI as the source of truth for what your archive will contain.
A backup protects Home Assistant’s own configuration and selected system content. It does not clone every device state, every wake-up condition, or every external network share as if nothing ever needs attention after restore.
The failures worth planning for
A useful backup plan covers five common failure modes: a bad update or configuration change; a failed SD card, SSD, or host; lost or corrupted configuration, including accidental deletion; planned hardware migration; and an unavailable backup location at schedule or restore time. Later sections cover off-host storage, the emergency kit, restore paths, migration checks, and location availability—this list is why the five-step baseline exists.
Why a backup on the same box is not enough
Two failure modes look similar and need different storage answers.
A bad update or configuration change often leaves the host reachable. A local backup can be enough to roll back selected content on the current system. Separately, a configuration file or stored configuration can be corrupted or accidentally deleted without an update being involved—local rollback still helps if the host is up and a recent backup exists.
Host, storage, or site failure is different. If the machine, SD card, eMMC, or SSD fails—or if the local network location that held your only copy is gone—a backup that lived only on that host may be unreachable when you need it most.
Home Assistant recommends keeping a copy on another system and, ideally, one off-site. Their 3…2…1… Backup framing is a useful resilience model once the automatic schedule is working: multiple copies, different media, and at least one copy that survives a local loss.
Local-only backups help with the first failure class. They are not enough for the second.
Set up automatic backups before the next update
Use the built-in UI path rather than inventing a custom automation on day one.
- Go to Settings → System → Backups.
- Under set up backups, start the automatic backup flow.
- Download the emergency kit when prompted and store it somewhere you can reach if Home Assistant is offline.
- Choose a daily schedule, or specific days if you must. Pick a time when every selected backup location is available; unavailable locations can fail that run.
- Decide whether backups should run automatically before updates. Large installs can take longer, so an update may start later than you expect.
- Set how many backups to keep. Older redundant backups can be purged according to those settings.
- Review what data is included. Official guidance often suggests excluding media and the shared folder when you want smaller, faster restores—adjust to what you actually need.
- Enable the backup locations you want to use.
After the first successful run, confirm the latest automatic backup completed. The Backup integration exposes last-successful and failed automatic-backup information, which is useful for a quick health check. Advanced users can notify themselves on failure; beginners do not need that automation to finish the baseline.
Keep the emergency kit separate from the backup
Encrypted backups are only useful if you can decrypt them.
The backup emergency kit holds the encryption key and related metadata. Home Assistant Cloud backups are always encrypted. Other locations can be encrypted by choice. Without the matching key, an encrypted backup cannot be restored.
Treat the kit as recovery credentials, not as a note inside the same device you are protecting:
- Download it during initial automatic-backup setup, or later from backup settings.
- Store it somewhere outside the Home Assistant host.
- If you change the encryption key later, keep the old kit for older backups. New keys do not unlock archives encrypted with the previous key.
If Home Assistant is still reachable and you have not rotated the key, you can usually re-download the current kit from Settings → System → Backups. If the host is gone and the kit is gone, the encrypted archive alone is not enough.
Make the kit findable before you need a restore.
Choose a backup location that survives the failure
Think in scenarios, not product brands.
Another device on the home network protects against Home Assistant host or storage failure. It may still fail in the same house fire, theft, or power event.
An off-site copy adds protection against broader local loss. How you get there depends on which backup locations your installation currently supports.
Home Assistant Cloud, if you already subscribe, can store a limited encrypted backup as documented by Home Assistant. You still need the emergency-kit key to restore it.
Network storage or other location integrations can work well when they are correctly set up as backup locations, online at schedule time, and reachable during recovery. Do not assume every NAS, cloud drive, or object store is available until you verify the current integration path and retention behavior for your install.
The rule for this guide is simple: get at least one copy off the Home Assistant host first. Expand to off-site when your risk tolerance says a same-site copy is not enough. Avoid treating an unconfigured destination as “done.”
How to restore Home Assistant after a failure
There are two common restore situations.
Restore the current system
Use this when the host still boots and you need to undo a bad update, broken configuration change, or similar recoverable mistake.
- Go to Settings → System → Backups.
- Select the backup you want.
- Choose what to restore. Selected current content will be overwritten.
- Start the restore and wait. Home Assistant restarts and the UI is temporarily unavailable.
- Sign in with the username and password that matched the system at backup time.
Restore during onboarding on new or reset hardware
On Home Assistant OS and Supervised-style installs, you can restore during onboarding when you replace hardware or factory-reset a device. That path assumes you have already installed Home Assistant on the target and are at the welcome screen.
You will need:
- the source system’s login credentials from the time of the backup;
- the emergency-kit encryption key for encrypted backups;
- more free storage on the target than the source system actually used—not merely more space than the backup file appears to occupy.
Upload the backup from the machine you are using for onboarding, or use a documented cloud-restore option if that is how your copy is stored. Select the parts to restore, enter the encryption key, and wait through the restart window without refreshing into a temporary “not found” state.
Container-style installs are different. The Backup integration can create and restore backups across installation types, but the onboarding migration flow above is an OS/Supervised recovery path. On Container-style setups, plan recovery around restoring into that install method rather than assuming the welcome-screen migration wizard applies unchanged.
What to check when you move to new hardware
Migration is where backup plans earn their keep—and where a few details get skipped.
- Keep login credentials and the emergency kit ready before you shut down the old host.
- Check Disk used on the source system (Settings → System → Repairs → system information under Home Assistant Supervisor) and make sure the replacement has more capacity than that real usage. The backup archive size is not a safe capacity estimate.
- Plug in USB radios or sticks on the new host before you expect those networks to return.
- Reconnect network storage after restore if it does not come back automatically.
- If the new hardware has a different built-in Zigbee radio than the old one, plan a Zigbee migration. Changing Z-Wave or other radios can need similar attention.
Hardware choice still matters for day-to-day ownership. For Green, Raspberry Pi, and mini PC tradeoffs, use the hardware comparison. The backup plan is what keeps that choice from becoming a full rebuild when storage fails.
A backup does not make every problem disappear
A successful restore returns Home Assistant configuration and selected content. It does not magically finish every household detail.
- Battery-powered devices may need to wake before they look healthy again.
- Connected network storage may need reconnection.
- A changed Zigbee, Z-Wave, or similar radio may require migration rather than a silent handoff.
- Recovery mode is a minimal safety net when normal startup fails. It loads a small set of system integrations so you can inspect logs, fix a configuration problem, or restore a backup. It is not a working smart home, and it is not a substitute for an off-host backup plan.
- A backup that has never been exercised is still an unverified recovery plan.
Recovery mode, a healthy running system, and a backup archive are three different things. Confusing them is how people discover gaps during the wrong week.
Confirm your recovery plan before you need it
You do not need to destroy a working installation to gain confidence. Before a major update or hardware change, walk this short check:
- Confirm the most recent automatic backup completed.
- Confirm a copy exists outside the Home Assistant host.
- Confirm you can open or locate the emergency kit and its encryption key.
- Read the official restore steps for your installation type—current-system restore versus onboarding migration on OS/Supervised, or the appropriate Container-style path.
- Decide what “test” means for your risk level: verifying off-host availability and credentials at minimum; a controlled restore only when you are ready for downtime and overwrite behavior.
Restore duration depends on installation size and content. Do not treat any single stopwatch figure as universal.
Home Assistant backup checklist
- Automatic backups enabled
- Daily schedule selected
- At least one backup copy stored outside Home Assistant
- Emergency kit downloaded and stored safely off-host
- Last successful automatic backup checked
- Restore path understood for this installation type
- Backup and kit reviewed before the next update or hardware change
Bottom line
A Home Assistant backup plan protects the time already invested in local control. Automatic backups keep the archive current. Off-host storage keeps it reachable after host or storage failure. The emergency kit keeps encrypted restores possible. A checked restore path turns those pieces into a plan instead of a hope.
Set the five-step baseline before the next update. When the foundation is protected, keep building toward devices and automations that stay useful without unnecessary subscriptions—our best smart home devices without monthly fees guide is a practical next step.