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

If your Home Assistant home matters to the rest of the household, the practical answer is simple: run automatic daily backups, keep at least one copy outside the Home Assistant machine, keep at least one copy off-site, save the backup emergency kit somewhere outside Home Assistant, and make a fresh manual full backup before risky changes.

That matches Home Assistant's own direction. The January 3, 2025 release overhauled backups around automation, encryption, retention, restore support, and 3-2-1 guidance. The current common-tasks documentation still recommends daily backups, recommends another system outside Home Assistant, and ideally another off-site copy as well.

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.

Why This Question Keeps Coming Up

The demand signal is current and obvious. A Reddit thread from early 2026 asked whether local-only backups on a single Home Assistant mini PC are enough in practice if the box dies. Another Reddit thread from 2025 described a failed restore after the owner realized their backups were encrypted and the key was nowhere to be found. On the Home Assistant Community forum, a January 7, 2025 community guide appeared specifically because many users were still asking how to handle manual backups, alternative storage targets, and container-specific edge cases after the 2025.1 backup overhaul.

Official product changes made the question more nuanced too. Home Assistant 2025.1 introduced automated backups, encrypted-by-default backups, restore support across installation methods, and retention. Home Assistant 2025.2 added Google Drive and Microsoft OneDrive locations, custom backup times, advanced schedules, and per-location encryption choices. Home Assistant 2025.5 added retention policies per location, which matters when your NAS can keep far more history than a cloud quota. And the April 1, 2026 release notes show the backup ecosystem expanding further with WebDAV, OneDrive for Business, and S3-compatible destinations such as AWS S3, iDrive e2, and Cloudflare R2.

The deeper reason people keep asking is simpler: a backup file does not equal recovery. GitHub issue reports opened on March 23, 2026 and June 11, 2026 show that restore paths can still hit edge cases. That does not mean Home Assistant backups are unreliable as a whole. It does mean that a backup you have never rehearsed is not the same thing as a house you can confidently recover.

Smart home kit components arranged so compute, radios, and backups can be recovered separately
A resilient Home Assistant setup treats the hub, radios, storage, and backup copies as recoverable parts instead of one fragile all-in-one box.

The Best Backup Setup for Most Homes

For a real home, the safest default is a 3-2-1-style backup posture: three copies, at least two locations, at least one off-site. Home Assistant itself explicitly points users to that model in the 2025.1 release.

In practice, most Tara-style installs end up with this shape:

  • 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 Nothing, if you forgot to save it

How to Configure It in Home Assistant Today

Home Assistant's common-tasks documentation is now good enough that the right setup is not exotic anymore. The important part is choosing the boring defaults on purpose.

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

The February 5, 2025 release added per-location encryption controls. That means you can keep off-site copies encrypted while optionally turning encryption off on a trusted local NAS if you specifically want easier manual file extraction. Home Assistant's default recommendation remains encryption, and downloaded backups from the Home Assistant UI are decrypted on the fly anyway, so most households can simply leave encryption enabled everywhere except maybe a tightly controlled local archive.

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.

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

Automatic daily backups are your floor, not your ceiling. Before a major update, hardware migration, Zigbee coordinator swap, database cleanup, or a big round of HACS and integration changes, create a fresh manual full backup with a name you will recognize later.

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.

Practice a Restore Before You Need One

This is the difference between a backup strategy and a hopeful pile of files. Home Assistant's current restore docs say onboarding restore works on a current system or on a new device, can migrate between device types, and may take roughly 45 minutes on a larger install. The docs also warn that the target needs enough storage, the old credentials still matter, and battery devices or radios may need attention after the move.

Those are exactly the reasons to do a rehearsal. The March 23, 2026 and June 11, 2026 GitHub issues are useful reminders that restore flows can still hit version or environment-specific edge cases. That interpretation is an inference from the issue tracker, not a Home Assistant guarantee of broad instability. The practical takeaway is straightforward: test while the house is calm.

  1. Spin up a spare HA OS VM or another temporary test target.
  2. Restore your latest backup during onboarding using the emergency-kit key.
  3. Confirm login, dashboards, automations, and critical integrations load correctly.
  4. Note anything external that the backup did not magically recreate, such as Docker sidecars, NAS mounts, or radio migrations.
  5. Delete the test system after you have proven the runbook works.

If you only do that once or twice a year, you are already ahead of most households. The goal is not enterprise disaster recovery theater. The goal is that a dead SSD or bad update does not turn into a lost weekend.

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?

Use full automated backups for routine recovery unless you have a very specific reason not to. Partial backups are fine for targeted manual work, but they are easier to misunderstand when you are stressed and trying to recover a whole home.

Can I restore Home Assistant to different hardware?

Usually yes. Home Assistant's restore docs say you can migrate from one device type to another during onboarding if the target has enough storage. Reattach your radios, keep the old login credentials, and expect some protocol-specific cleanup if the radio hardware changes.

What if I run Home Assistant Container?

Container users can still use Home Assistant backups, but the overall recovery story is more manual. The official install docs make clear that Container is an advanced install type with manual host responsibility, and community restore discussions still talk about manual restore steps for non-HAOS environments. If simple recovery matters more than Docker flexibility, HA OS is usually the calmer choice.