How to Back Up Your NAS: The 3-2-1 Rule in Practice
10 min read
1,975 words
If your NAS is protected by RAID or ZFS, you have redundancy — but you do not have a backup. RAID protects against a single drive failure. It does nothing against accidental file deletion, ransomware encryption, a power surge that fries the motherboard, a house fire, or theft. A proper NAS backup strategy is what saves your data when redundancy fails. This guide walks you through the 3-2-1 backup rule applied to a real home NAS setup, covering local copies, off-site options, automation, and — most importantly — how to test that your backups actually work.
Why RAID Is Not a Backup: The Core Distinction
This is the single most important concept in NAS ownership. RAID (whether RAID 1, RAID 5, RAIDZ1, or RAIDZ2) provides availability — it keeps your NAS running after a drive dies. A backup provides recoverability — it lets you get your data back after something catastrophic happens to the NAS itself.
What RAID Protects Against
- Single (or dual, with RAID 6/RAIDZ2) drive failure
- Corrupted sectors that the RAID controller can rebuild from parity
What RAID Does NOT Protect Against
- Accidental file deletion or overwrite
- Ransomware encryption (it encrypts the live array)
- Power supply failure that destroys all drives
- Theft of the entire NAS
- Fire, flood, or physical destruction
If you delete a file on a RAID array, it is gone from every drive simultaneously. RAID mirrors or stripes the data — there is no “second copy” to revert to. A backup is the only way to recover.
The 3-2-1 Backup Rule: NAS-Specific Breakdown
The 3-2-1 backup rule is the industry standard for data protection. Applied to a NAS, it means:
- 3 total copies of your data (1 primary + 2 backups)
- 2 different media types (e.g., internal drives + external USB drive)
- 1 copy stored off-site (geographically separate from the NAS)
For most homelab users, a practical 3-2-1 setup looks like:
- Copy 1: Your live NAS with RAID/ZFS redundancy (the primary)
- Copy 2: A second local device — either a second NAS or a rotating set of external drives
- Copy 3: An off-site destination — a friend’s NAS, a cloud provider, or a safety deposit box drive rotation
Step 1: Create a Local Second Copy
Your first backup destination should be local — fast, under your control, and accessible for quick restores. Two common approaches work well for a NAS backup strategy.
Option A: A Second NAS for Local Backup
A dedicated backup NAS is the most robust local option. It can be a smaller, lower-power unit — think a 2-bay device with two large drives in RAID 1. Configure it to receive nightly rsync or ZFS send/receive snapshots from your primary NAS. This keeps the backup physically separate but still on your LAN, so restores are fast.
Option B: Rotating External USB Drives
If a second NAS is outside your budget, rotating external drives are a cost-effective alternative. Buy two external drives (same capacity as your critical data set). Keep one connected to the NAS for a weekly backup, then swap it with the other drive stored in a different room or a fireproof safe. This protects against both drive failure and local disasters like a fire that takes out the whole rack.
Label each drive with the backup date and rotate weekly. Use a USB 3.0 or USB-C connection — a full backup of 4TB over USB 3.0 takes roughly 3-5 hours.
Step 2: Set Up an Off-Site NAS Backup
The “1” in 3-2-1 is the hardest part for many homelab users. An off-site NAS backup ensures your data survives a total site disaster. You have two main paths.
Cloud Backup: Backblaze B2 and Similar Services
Backblaze B2 is the most popular cloud destination for NAS backups. It charges per GB stored and per GB downloaded. For a 4TB backup, expect to pay roughly $20-$25 per month for storage, plus a one-time upload cost. Tools like Duplicacy, Restic, and the built-in cloud sync in TrueNAS or Unraid all support B2.
| Cloud Service | Storage Cost (per TB/month) | Download Cost | NAS Software Support |
|---|---|---|---|
| Backblaze B2 | $5-$6 | $10/TB | TrueNAS, Unraid, Duplicacy, Rclone |
| Wasabi | $6.99 (no egress fees) | $0 | Duplicacy, Rclone |
| Google Cloud Nearline | $10 | $12/TB | Rclone, Duplicacy |
Cloud backup is ideal for irreplaceable data — family photos, documents, personal projects. For easily replaceable media (Linux ISOs, downloaded movies), consider whether the monthly cost justifies the protection.
Off-Site to a Friend’s NAS
If you have a friend or family member with a NAS, you can set up a mutual backup arrangement. Use Tailscale or WireGuard to create a secure VPN tunnel between the two devices, then run rsync or Syncthing for encrypted data transfer. This is essentially free beyond the electricity cost at the remote site.
Always encrypt the backup data before it leaves your network. Tools like Duplicacy and Restic encrypt by default. If you use rsync, pipe it through an encrypted tunnel (SSH or WireGuard) — never send unencrypted data over the internet.
Step 3: Automate Your NAS Backup
Manual backups fail. The only reliable how to backup NAS answer is automation. Every major NAS operating system has built-in tools for this.
Identify which shares are critical. Family photos, documents, and configuration files are non-negotiable. Media libraries may not need backup if you can re-rip or re-download them.
TrueNAS uses ZFS snapshots + replication or rsync tasks. Unraid has a built-in backup plugin (CA Backup/Restore). Synology DSM includes Hyper Backup. For any OS, Duplicacy or Restic work well.
Run local backups daily (incremental) and off-site backups weekly. Cloud backups should use incremental uploads to minimize bandwidth and cost. Schedule during off-peak hours — 2 AM is a common choice.
Keep daily snapshots for 7 days, weekly for 4 weeks, monthly for 6-12 months. This protects against ransomware that may go undetected for weeks — you can roll back to a clean snapshot.
TrueNAS ZFS replication is one of the most efficient backup methods available. It sends only the changed blocks (not entire files) and verifies data integrity on both ends. Combined with snapshots, you can restore to any point in time within your retention window. This is far more efficient than file-level rsync for large datasets.
Step 4: Test Your Restores — Not Just Your Backups
A backup you have never tested is a backup you do not have. Testing restores is the only way to confirm your NAS backup strategy actually works. A corrupted backup file, a misconfigured tool, or a failed drive in the backup destination can all silently break your safety net.
- Quarterly: Restore a single critical file from each backup destination (local NAS, external drive, cloud). Verify the file opens correctly.
- Annually: Perform a full disaster recovery drill. Simulate a complete NAS failure — wipe a test share, then restore it from backup. Time the process.
- After any major change: Re-test backups after a NAS OS upgrade, a drive replacement, or a network reconfiguration.
Cloud backups can fail silently if your internet connection drops mid-upload or if the backup software encounters an error it doesn’t report. Always check backup logs weekly. Many NAS operating systems can email you a success/failure report — enable this.
NAS Backup vs RAID: When Each Matters
Understanding the NAS backup vs RAID distinction helps you allocate your budget correctly. They solve different problems and both are essential.
| Scenario | RAID Handles It? | Backup Handles It? |
|---|---|---|
| Single drive fails | Yes — rebuild from parity or mirror | Yes — but restore takes longer |
| Accidental file deletion | No — file is gone from all drives | Yes — restore from backup |
| Ransomware encrypts files | No — encrypts the live array | Yes — restore from clean backup |
| NAS is stolen or destroyed | No — whole device is gone | Yes — if backup is off-site |
| Power surge fries all drives | No — all drives affected | Yes — if backup was disconnected |
Your RAID configuration protects your uptime. Your backup protects your data. They are complementary, not interchangeable.
Which Should You Choose: A Complete NAS Backup Strategy
Here is the bottom-line recommendation for a practical, cost-effective how to backup NAS plan for a typical homelab.
For most users (under 10TB of critical data): Use a single external USB drive for local backups (rotate two drives if budget allows) plus Backblaze B2 for off-site. Automate with Duplicacy or the built-in tool in your NAS OS. Test a file restore quarterly. Total cost: roughly $30-$50 one-time for drives plus $20-$30/month for cloud storage.
For power users (10TB+ or multiple NAS units): Add a second low-power NAS for local backups and use a friend’s off-site NAS or a higher-tier cloud plan. Use ZFS send/receive for efficient replication. Test a full disaster recovery annually. Total cost: $200-$500 for the backup NAS plus $50-$100/month for cloud at higher capacities.
If you are building a new NAS, consider a CPU that supports efficient encryption for off-site backups. The Best CPU for TrueNAS in 2026 guide covers processors with AES-NI support, which significantly speeds up encrypted transfers.
Remember: RAID gives you uptime. Backup gives you recovery. You need both. Start with a simple automated backup to an external drive this week, then add off-site protection next month. Your future self will thank you when a drive fails — or worse.
Frequently Asked Questions
Does RAID count as a backup?
No. RAID protects against drive failure by providing redundancy (mirroring or parity), but it does not protect against accidental deletion, ransomware, file corruption, or physical destruction of the NAS. If you delete a file from a RAID array, it is gone from all drives simultaneously. A backup is a separate copy of your data stored on different media, often in a different location. RAID and backup serve different purposes and both are necessary for complete data protection.
What is the 3-2-1 backup rule?
The 3-2-1 backup rule is a data protection strategy that recommends keeping three total copies of your data (one primary and two backups), stored on two different media types (such as internal hard drives and external USB drives), with one copy stored off-site (geographically separate from the primary location). For a NAS, this typically means your live RAID array as the primary copy, a second local device like an external drive or second NAS as the second copy, and a cloud service or friend’s remote NAS as the third copy. This protects against drive failure, local disasters, and ransomware.
What’s the cheapest way to do off-site NAS backup?
The cheapest off-site NAS backup method is a mutual arrangement with a friend or family member who also has a NAS. Using a secure VPN tunnel (Tailscale or WireGuard) and rsync or Syncthing, you can back up to each other’s devices at no cost beyond electricity. If you prefer a cloud provider, Backblaze B2 is the most affordable option at roughly $5-$6 per terabyte per month, with no minimum storage period. For small datasets under 1TB, some cloud providers offer free tiers (like Google Drive or OneDrive) if you encrypt your data before uploading.
How often should I test restoring from backup?
You should test restoring a single critical file from each backup destination (local and off-site) at least once per quarter. Perform a full disaster recovery drill — where you simulate a complete NAS failure and restore an entire share from scratch — once per year. Additionally, test your backups after any major system change, such as a NAS OS upgrade, a drive replacement, a network reconfiguration, or a change in backup software. Automated backup logs should be checked weekly for errors, but a successful log entry does not guarantee the backup is restorable — only a test restore confirms that.
Last verified: July 09, 2026. Specifications cross-checked against manufacturer documentation where available.
🛡 Shop Recommended Hardware
Prices and stock verified regularly by our affiliate partners. As an affiliate, HomeLabCost may earn a commission on qualifying purchases at no extra cost to you.
Browse Hardware Picks →
homelabcost
HomeLabCost editor covering NAS builds, hardware selection, and homelab server setup guides.