Short Answer: Automate Daily, Store One Copy Off the Box, and Keep the Key

Use Home Assistant's built-in backup settings for a daily schedule, separate storage, and a saved encryption key. Then check that a backup actually reached each destination. A scheduled job is not proof that a usable recovery copy exists.

Home Assistant OS and Home Assistant Container both support backup restoration. The Backup integration covers both; the difference is what else you must recover. Container does not rebuild your Linux host or separate MQTT broker, database, and radio-service containers. Do not follow an old Docker tutorial that says manual file extraction is the only restore method.

Research basis: Checked against Home Assistant documentation on September 15, 2026. The example and rehearsal below are planning procedures, not reported Tara hardware tests or recovery-time measurements. The cover is illustrative.

Tara's backup rule: keep one fast restore nearby, one easy copy off the box, one off-site copy, and one decryption key your future self can actually find.

The Best Backup Setup for Most Homes

The 3-2-1 rule means three copies, two different storage media, and one copy off-site. Two folders on the same drive do not protect against that drive failing. A NAS is a separate storage device on your home network; it still shares risks such as theft or fire with the home.

A practical household plan can use these layers:

  • Daily automatic full backup stored locally for fast rollback and easy short-term history.
  • The same automatic backup copied to a NAS, network share, or another always-on box so a dead SSD or mini PC is not the end of the story.
  • An encrypted off-site copy through Home Assistant Cloud or another supported remote provider so one building failure does not take out every copy.
Layer What it protects you from What it still misses
Local backup on the Home Assistant box Bad edits, bad updates, quick same-machine rollback Disk failure, theft, fire, or total machine loss
NAS or network-share copy Mini PC failure, dead SSD, faster access than off-site storage Whole-building loss, ransomware, or a dead NAS if that is your only other copy
Encrypted off-site copy Site-wide loss, dead NAS, disaster recovery Slower restore, storage quotas, and total failure if the key is lost
Backup emergency kit stored outside Home Assistant Restore of encrypted backups when the main box is gone The backup data itself; a key without the matching file is not a recovery copy

How to Configure It in Home Assistant Today

In Settings > System > Backups, choose Set up backups, or Configure automatic backups if already configured. Set the schedule, included data, locations, and retention. Save the emergency kit. The official walkthrough shows the current screens.

1. Turn on automatic daily backups

The official docs recommend a daily schedule. Pick a time when your backup locations are actually reachable. Home Assistant explicitly warns that if a target location is asleep or offline, that location's backup will fail. If you have a NAS that spins down overnight, use a custom time or an advanced backup automation instead of hoping the system-optimal window matches your storage behavior.

2. Add at least one backup location outside the Home Assistant box

The common-tasks page is unambiguous here: if you only store backups on the device itself, they are hard to access after a crash. The docs recommend another system outside Home Assistant and ideally one off-site. As of the April 1, 2026 release notes, supported remote backup paths now include Home Assistant Cloud, WebDAV, Google Drive, OneDrive, OneDrive for Business, and S3-compatible integrations.

If you already subscribe to Home Assistant Cloud, it is a good off-site safety net, but know its shape: the official docs say it stores one backup file, up to 5 GB, and it is always encrypted. That makes it a strong latest-copy option, not a deep archival history by itself.

3. Use retention on purpose, not by accident

Home Assistant 2025.5 added retention per location for a reason: different locations deserve different histories. A roomy NAS can keep weeks of daily backups while a cloud location might keep only the last few. Home Assistant's own release notes even use that exact pattern as the motivating example.

For many homes, keeping a deeper local or NAS history plus a smaller off-site history is the sensible compromise. The exact counts depend on your storage, but the strategy matters more than the number: shorter off-site history is still much better than no off-site history.

4. Keep encryption on anywhere the storage is not fully under your control

Leave encryption enabled unless you have a deliberate, protected local-file workflow. Home Assistant offers per-location encryption controls, but Home Assistant Cloud storage is always encrypted. Encryption makes a stolen backup unreadable without its key.

A browser download can be different from the stored file. Downloading through Home Assistant normally decrypts the archive as it downloads, when the matching key is available. Treat that download as sensitive, unencrypted household data: do not email it, attach it to a public issue, or upload it to a public repository. Successfully opening that download does not prove you can decrypt an encrypted copy recovered later from remote storage.

Do not treat this as a cosmetic setting. Backups can contain device credentials, household history, cloud tokens, and other sensitive data. If the copy leaves your house or lives on third-party storage, encryption should stay on.

5. Save the emergency kit somewhere outside Home Assistant

This is the step people keep skipping until it hurts. Home Assistant's docs tell you to download the emergency kit and keep it safe because you need it to restore encrypted backups. The Reddit thread about lost backup keys is the real-world version of that warning: the owner had years of backups and still ended up rebuilding from scratch.

A password manager, secure household vault, or another external system is fine. Just do not store the only copy of the key inside the Home Assistant box you are trying to recover.

Keep old keys with their backup dates. Changing the key affects future backups, not old files. If the original system still works, check its backup settings for the current kit. If the required older key is gone, generating another will not recover it. Nabu Casa cannot supply a missing encryption key.

6. Check the result, not just the schedule

After a run, inspect the backup's locations and confirm the off-device upload finished. The Backup integration's status sensors separate the next scheduled run, last attempted run, and last successful run. An attempted timestamp is not a success; a success timestamp is not a restore test.

For failure alerts, use the integration's documented automatic-backup event and its event_type attribute, not the event entity's timestamp as though it were a success flag. Add a separate daily check for an overdue successful backup: a task that never starts may not produce a failure event. Test the notification itself using a harmless message, not by breaking storage or deleting a backup. See the notification-delivery checklist if the message does not arrive.

Worked Example: Can Someone Recover the House Without the Hub?

Consider an illustrative home with a 1.2 GB daily backup, a NAS, and Home Assistant Cloud. Seven such files need about 8.4 GB before allowing for growth and storage overhead. The Cloud location keeps only the latest copy, so it does not replace a longer local history. This is a planning example, not a measured Tara installation or a prediction of restore time.

Walk through this checklist with the Home Assistant computer unavailable. Do not shut it down merely to inspect files and account access.

  • File: Can you locate the chosen backup on the NAS or remote account from another computer? Record its date and included data.
  • Key: Can you find the emergency kit that matches that date, independently of the failed computer?
  • Access: Can an authorized household member unlock the password manager and complete any account two-factor check?
  • Target: Do you know which spare machine, installation type, radios, and external services the recovery needs?
  • Evidence: Record the last successful upload and last actual restore separately. Finding a file passes the access check, not the restore check.

What to Back Up, and What to Leave Out

The Home Assistant docs specifically recommend disabling media and the shared folder if you want smaller, faster backups. That is usually the right move for homeowners who care more about getting automations, dashboards, integrations, and credentials back quickly than about preserving every old camera clip.

A good rule is this:

  • Include by default: core config, automations, dashboards, entities, secrets, apps/add-ons, and the parts of history you actually rely on.
  • Exclude if separately protected: camera media, bulky exports, and any large share-folder files that already live on a NAS or another retention system.

If you run extra services around Home Assistant, treat them as a second backup problem. That matters especially for Home Assistant Container, because the official installation docs say Container users bring their own Linux and manual update flow, do not get apps, and do not have out-of-the-box support for some Thread or Z-Wave pieces that HA OS handles more conveniently. Practically, that means your Docker compose files, MQTT broker, databases, radio mappings, and companion containers still need host-level backup coverage.

Do not let camera retention bloat your recovery path. Restoring the automations and device state of your house is usually more urgent than restoring months of clips that already belong in a separate video-retention workflow.

Before Risky Changes, Make a Fresh Manual Backup

Before an update or migration, choose Backup now > Manual backup, name the milestone, select the required data and destinations, and wait for completion. Preserve a known-good older copy too: the newest backup may already contain the fault you want to undo.

Home Assistant 2025.2 and 2025.5 both improved the backup-before-upgrade workflow, including default preferences and OS-upgrade backup toggles. That is useful. Still, if you are about to make a change you would hate to unwind by memory, a clearly named manual milestone backup is the better habit.

Restore Without Starting a Second Controller for Your Home

A restored copy is not automatically a harmless sandbox. Home Assistant normally restores automation on/off states at startup, and backups contain connection settings and credentials. Our safety recommendation follows from that: assume a restored copy could contact devices, send notifications, or run routines as soon as it starts.

Choose the test boundary first. An isolated rehearsal needs enforced separation from household devices, network brokers, radios, shared storage, and cloud-control accounts. A different IP address is not isolation. Simply blocking the internet is also insufficient for local devices, and may prevent software needed for the restore from downloading. Have an experienced administrator arrange that environment; otherwise use planned downtime with only one controller active.

The recovery sequence

  1. Prepare: Keep the source machine and backup intact. For a real cutover, plan manual controls for heating, locks, water, and other essential equipment; review startup routines and shut down the old controller before the restored one can reach the home.
  2. Select: On a fresh installation's welcome screen, upload the backup. On an existing installation, select it under Backups and choose Restore. Restoration overwrites the selected data.
  3. Recover: Supply the matching key if encrypted. Wait without refreshing; then use the login from the backup. Allow sufficient target storage based on the original installation's used space, not its compressed archive size.
  4. Inspect before control: Check dashboards, configuration, and the recovery notes. On an isolated copy, unavailable integrations are expected; this does not validate radios, physical device control, or cloud services.
  5. Verify deliberately: During the planned single-controller cutover, reconnect the required services and existing radios, then test one noncritical lamp. Use the dedicated hardware migration guide for radio changes. Do not test by unlocking doors, operating valves, or disabling alarms.
  6. Finish: Record what worked and what remains untested. For a rehearsal, stop the restored copy before restarting the original. Do not leave a duplicate controller or its cloud connection running in the background.

Follow the official restore procedure for your installation. Restoring Home Assistant data is not the same as restoring every external service. Keep your only good backup until the intended recovery has been verified.

Tara's Take

A local smart home should not depend on heroics when something breaks. The whole point of running Home Assistant locally is control, privacy, and predictability. A backup plan that lives only on the same box, or only in one person's memory, breaks that promise.

The Tara version is deliberately boring: stable hardware, clean power, radios that are easy to reattach, a documented off-box backup path, and a handoff that another person in the house could follow without reverse-engineering your hobby.

If your backup question is really an update, hardware, or migration question underneath, these guides help with the next decision.

FAQ

Are Home Assistant automatic backups enough if I only keep them on the same machine?

No. They help with bad updates and bad edits, but not much with dead storage or a dead host. Home Assistant's own docs recommend another system outside Home Assistant and ideally another off-site copy.

Do I really need the backup emergency kit?

Yes. Encrypted backups require the key from the emergency kit. Without that key, the backup file may exist but still be useless for restore.

Should I use full backups or partial backups?

Include all the configuration and app data needed for recovery. Exclude large media only if separately protected or intentionally disposable. A partial restore replaces selected components; it is not a merge of an old configuration into the current one.

Can I restore Home Assistant to different hardware?

Yes, supported migration paths can use different hardware. Check storage requirements and external services first, keep the old login and matching key, and plan radios separately. Do not let both controllers operate the same home during the move.

What if I run Home Assistant Container?

Built-in backup restoration supports Home Assistant Container; it has since Home Assistant 2025.1. You still maintain Linux, Docker configuration, and companion services separately. An OS backup's apps do not become separate Docker services automatically when you move to Container.