What happens to your smart home when the SD card dies, the SSD fills up, or a bad update bricks the whole system? For most people, the answer is a weekend of rebuilding automations from scratch. That is exactly why moving your Home Assistant backups to a network drive matters. It is the difference between a ten-minute restore and a total rebuild.
This guide walks through how Home Assistant handles backups today, where a network drive fits in, and the practical traps that catch people out. No fluff, no hand-waving. Just what actually works.
Why a Local-Only Backup Is a Backup Half-Done
Home Assistant‘s built-in backup system, rebuilt in the 2025.1 release in January 2025, stores backups on the Home Assistant host’s local storage by default. That is a big improvement over the old snapshot system, but it carries one obvious weakness: if the storage device fails, the backups fail with it.
Think about the failure modes:
- The microSD card in a Raspberry Pi wears out and dies. Backups on that card die too.
- A power surge kills the SSD. Same story.
- Ransomware or accidental deletion wipes the drive. The backups go with it.
A network drive (usually a NAS or a shared folder on another computer) solves the “same disk” problem. The backup lives on separate hardware, so a single failure no longer takes out both the system and its safety net. This is the core logic behind the widely recommended 3-2-1 rule: three copies of data, on two different media, with one copy off-site. The 3-2-1 backup strategy is standard practice across IT for good reason.
Does Home Assistant Back Up Directly to a Network Drive?
This is where expectations and reality often part ways, so it is worth being precise.
The native backup feature does not, in its original design, offer a simple “pick a network folder” destination in the interface. Backups land on local storage. To get them onto a network drive, you have a few documented paths, and each has trade-offs.
| Method | How it works | Best for | Main catch |
|---|---|---|---|
| Cloud backup integrations | Official Google Drive and OneDrive agents upload backups off-device | Hands-off cloud copies | Depends on internet; storage quotas apply |
| Samba Backup add-on | Writes backups to an SMB share on your NAS | NAS owners who want local network copies | Add-on maintenance; SMB setup required |
| Network storage mount | Mounts an SMB/NFS share at the OS level via Settings, then targets it | Users on recent versions with NAS hardware | Support depends on version; not always a backup target |
| Manual copy | Download the backup and move it yourself | Occasional, low-stakes setups | Easy to forget; not automated |
The honest summary: Home Assistant supports network storage mounts at the operating-system level, and it offers official cloud backup integrations, but whether the backup engine can write straight to a mounted network share depends on your version. Later 2025 and 2026 releases have steadily expanded storage options, so check the current release notes before assuming a feature exists or does not.
If you are also hardening the rest of your setup, the same discipline that protects your network applies to your backups. A guide on how to secure your home wi-fi network pairs well with locking down a NAS that holds your smart home data.
The Encryption Trap Nobody Warns You About
Here is the mistake that catches more people than any other. Since the 2025.1 backup redesign, backups are encrypted by default, and the encryption key is stored locally on the Home Assistant device.
That is great for privacy. It is terrible if you lose the key.
Picture the scene: your Home Assistant box dies. You grab the backup file from your NAS, feeling smug because you set up a network drive. You try to restore. It asks for an encryption key you never wrote down, and the key lived on the dead device. The backup is now a very secure brick.
The fix is simple but easy to skip: export and store your encryption key somewhere separate from the backup itself. A password manager is ideal. A printed copy in a drawer works too. Just do not leave it only on the machine you are trying to protect.
Practical rule of thumb: if your backup and its key live in the same place, you do not have a backup. You have a single point of failure wearing a disguise.
Setting Up a Network Backup: A Practical Walkthrough
The exact menu names shift between versions, but the workflow is consistent. Here is the sequence that works for most people running Home Assistant OS or Supervised installs.
- Prepare the network share first. On your NAS, create a dedicated folder for Home Assistant backups and a user account with read/write access to only that folder. Least privilege matters here.
- Mount the share on Home Assistant. Go to Settings, then System, then Storage, and add a network storage mount using SMB or NFS. Enter the server address, share name, username, and password.
- Install a backup path that can reach it. Either add the Samba Backup add-on (which writes to SMB shares directly), or configure an official cloud integration if you prefer off-site copies.
- Schedule automatic backups. Set a cadence you will actually keep, such as nightly or weekly, and configure retention so old copies rotate out. Unbounded backups will fill any drive eventually.
- Export the encryption key and store it away from the backup location.
- Test a restore. This is the step almost everyone skips. Do it anyway.
That last point deserves emphasis. A backup you have never restored is a hypothesis, not a safety net. Spin up a test instance, restore the backup, and confirm your automations, dashboards, and integrations come back. It takes an evening and saves a panic later.
Common Mistakes to Avoid
- Skipping the restore test. The most common and most painful error.
- Forgetting the encryption key. Covered above, but it bears repeating.
- Pointing backups at the same failing disk. If your NAS shares a power supply or network switch with the Home Assistant box, a single outage can still take out both.
- Ignoring retention settings. Backups grow; without rotation, the drive fills and new backups silently fail.
- Assuming a Container install behaves like Supervised. Home Assistant Container (Docker) users do not get the Supervisor backup feature and must back up volumes manually. This has been true throughout the Supervisor era.
Cloud Integrations vs. Network Drive: Which Should You Choose?
Neither option is strictly better. They solve different problems, and many people sensibly use both.
A network drive gives you fast local restores, no subscription cost, and full control over your data. It is ideal for the “my SSD died and I need to be back online tonight” scenario. The downside is that a fire, flood, or theft can take out the NAS and the Home Assistant box together.
Cloud integrations (the official Google Drive and OneDrive agents, which have existed for several years) give you an off-site copy that survives local disasters. The downsides are dependence on your internet connection, storage quotas, and the fact that a large backup can take a while to upload.
The balanced approach is to write backups to the NAS for speed and convenience, then let a cloud integration handle the off-site copy. That satisfies the 3-2-1 rule without much extra effort. If you are already thinking about resilience in other parts of your home tech, the same “separate the failure domains” logic shows up in guides like best external hard drives for backup, where redundancy beats raw capacity every time.
Version and Install Caveats Worth Knowing
A few technical realities trip people up, and they are worth stating plainly.
Restores generally require a matching or newer Home Assistant version. Restoring an old backup onto an older core version is typically unsupported. If you are rolling back, check compatibility first.
Supervisor-based installs and Container installs are not the same. The backup and restore feature is a Supervisor capability. If you run Home Assistant in Docker without the Supervisor, you are responsible for backing up your configuration and data volumes yourself, usually with a script or a container-aware backup tool.
Network storage mounting arrived at the OS level around 2024, separate from the backup redesign in early 2025. The two features evolved on different tracks, which is why documentation sometimes describes one without the other.
Encryption behavior can vary by version. Whether you can disable encryption per backup has changed across releases. Verify against the current documentation rather than assuming.
For anyone maintaining a broader home lab, treating the Home Assistant box like any other server pays off. The same habits that keep a PC healthy, such as disciplined storage management, apply here. If you are upgrading hardware at the same time, a walkthrough on how to clone hard drive to ssd 2026 covers the migration side of things.
Does the Hardware Matter?
It matters more than most guides admit. The storage medium under Home Assistant determines how often you will need those backups in the first place.
| Storage type | Reliability | Backup urgency |
|---|---|---|
| microSD card | Low; wears out under constant writes | High |
| USB SSD | Moderate to good | Medium |
| Internal SSD (mini PC, NUC) | Good | Medium |
| NAS-hosted VM | Good, with snapshot support | Lower |
A Raspberry Pi running on a microSD card is the classic failure case. Constant database writes wear the card, and failures are common enough that the community treats them as a matter of when, not if. Moving to an SSD, or running Home Assistant as a VM on a NAS that already does snapshots, dramatically reduces how often you need to lean on backups.
This connects back to the network drive question: if your Home Assistant already lives on the NAS, a backup to a share on that same NAS is a weaker safety net than it looks. In that case, the off-site cloud copy becomes the important one.
A Sensible Backup Setup in Plain Terms
Strip away the technical detail and a good setup looks like this:
- Local automatic backups to a network drive, scheduled and rotated, so recent restore points always exist.
- One off-site copy, either through a cloud integration or a periodic manual export to a drive you keep elsewhere.
- The encryption key stored separately, in a password manager or on paper.
- A restore test done at least once, ideally after any major version upgrade.
- Retention configured so the drive never silently fills.
That is it. No exotic tooling required. The people who lose their smart home setups are almost never the ones who skipped a clever trick; they are the ones who never tested a restore or never stored the key.
Conclusion
Backing up Home Assistant to a network drive is one of the highest-value habits in home automation, but it is not a single toggle. The native backup system stores copies locally by default, cloud integrations handle off-site copies, and network storage mounts let you target a NAS at the OS level. The exact combination that works for you depends on your version and hardware.
What matters most is not which method you choose. It is whether you have tested it. A scheduled backup to a NAS, an off-site copy, a safely stored encryption key, and one successful restore test put you ahead of most smart home owners. Do those four things and a dead drive becomes an inconvenience instead of a catastrophe.
Frequently Asked Questions
Can Home Assistant back up directly to a network drive?
It depends on your version. Home Assistant supports network storage mounts at the operating-system level through Settings, System, and Storage, and the Samba Backup add-on can write backups to SMB shares. Whether the native backup engine can target a mounted share directly has changed across releases, so check current documentation for your version.
Where does Home Assistant store backups by default?
By default, backups are stored on the Home Assistant host’s local storage. That means they live on the same device the system runs on, which is why a separate network or cloud copy is strongly recommended.
What happens if I lose my backup encryption key?
The backup becomes unrecoverable. Since the 2025.1 backup redesign, backups are encrypted by default and the key is stored locally on the device. If the device dies and you never exported the key, you cannot restore the backup. Always store the key separately in a password manager or on paper. (Backup)
Do I need a NAS to back up Home Assistant?
No. A NAS is convenient, but official cloud integrations for Google Drive and OneDrive let you store backups off-device without any local hardware. You can also periodically download backups and copy them to an external drive kept somewhere else.
Why did my automatic backups stop working?
The most common cause is a full destination drive. Backups grow over time, and without retention settings to rotate old copies, the storage fills up and new backups fail silently. Check available space and configure a retention count.
Can I restore a backup on an older version of Home Assistant?
Generally no. Restoring a backup typically requires a matching or newer Home Assistant version. If you need to roll back, verify version compatibility before attempting the restore, or you may end up with a system that will not boot properly.
