Best Backup NAS Build 2026: A Dedicated Second NAS for the 3-2-1 Rule

If you already own a primary NAS, the single most impactful upgrade you can make for data safety is adding a dedicated backup NAS. This isn’t a second server for daily file access or media streaming; it’s a purpose-built target for your backups, designed to enforce the 3-2-1 rule (three copies of your data, on two different media, with one copy off-site). This guide walks you through building a cost-effective backup NAS that prioritizes capacity and reliability over raw performance.

Why a Backup NAS Has Different Hardware Requirements Than a Primary NAS

A primary NAS handles multiple concurrent workloads: file sharing, media serving, Docker containers, and possibly virtualization. This demands a capable CPU, ample RAM, and fast storage. A backup NAS, by contrast, has a single, predictable workload: receiving writes from your primary NAS once or twice a day. It doesn’t need to transcode video, run a database, or serve files to multiple users simultaneously.

This means you can use older, power-efficient hardware. A used business-class mini PC or a low-power motherboard with an Intel Celeron or a low-end Core i3 is more than sufficient. The CPU is rarely the bottleneck during backup transfers; the network link (1 GbE or 2.5 GbE) is. You also don’t need ECC RAM for a backup target, unless you are using ZFS and want to be extra cautious about data corruption during the backup window.

HBA Card Use for Maximizing Drive Bays Cheaply on Older Hardware

Many used motherboards or mini PCs come with only 2-4 SATA ports. To attach 4-8 hard drives for a backup NAS, you need an HBA (Host Bus Adapter) card. An HBA in IT mode (or “passthrough” mode) presents each drive directly to the operating system, bypassing any RAID controller logic. This is ideal for software RAID solutions like ZFS, Unraid, or mdadm.

An HBA card typically plugs into a PCIe x8 slot. If your motherboard only has x16 slots, the card will still work (it just won’t use the full bandwidth, which is fine for spinning disks). For a backup NAS, a single HBA can handle 8 drives easily, giving you a 6-drive RAIDZ2 or an 8-drive RAID 6 array.

Case and Bay-Count Planning for a Backup Target

For a backup NAS, you are optimizing for storage density and low noise, not hot-swap convenience or high airflow for constant reads. A simple 4-bay or 6-bay tower case is often the best choice. Avoid expensive rack-mount chassis with backplanes unless you already have a rack and need the form factor.

Don’t over-provision bays. A 4-bay backup NAS with 12 TB drives gives you 36 TB usable in RAID 5, which is enough for most homelabs backing up 10-20 TB of critical data. If you need more later, you can replace drives one at a time (if your RAID supports online expansion) or build a second backup NAS.

Software Options for a Dedicated Backup NAS

The software on your backup NAS should be stable, minimal, and focused on receiving backups. You don’t need a full desktop environment or a media server stack. Here are the most practical options, ranked by suitability.

Proxmox Backup Server (PBS)

If you run Proxmox VE on your primary server, PBS is the obvious choice. It is purpose-built for backup, supports incremental backups, deduplication, and encryption. It runs on Debian and is free and open-source. PBS uses ZFS for its storage backend, which gives you data integrity checks and snapshots. It can also back up non-Proxmox systems via the proxmox-backup-client.

Unraid

Unraid is a popular choice for a backup NAS because it allows mixing different drive sizes and uses parity instead of striping. This means you can add drives over time without rebuilding an entire array. Unraid also supports Docker, so you can run backup apps like Duplicati or rsync right on the server. The downside is the $59+ license fee, but for a backup-only box, the basic plan is sufficient.

For a deeper comparison of TrueNAS vs Unraid for your primary NAS, see our TrueNAS vs Unraid guide. For a backup target, Unraid’s flexibility with drive sizes is a strong advantage.

rsync and Restic on a Minimal Linux Install

For the most control and lowest overhead, install a minimal Debian or Ubuntu Server and use rsync (for file-level syncs) or Restic (for encrypted, incremental snapshots). This approach uses almost no RAM (512 MB is enough) and gives you full control over backup schedules via cron. You can even set up an SSH server with key-based authentication for push-style backups from your primary NAS.

• Install Debian server (no GUI) — uses ~200 MB RAM idle.
• Configure SSH with public key authentication (disable password login).
• Set up a ZFS pool or ext4 + LVM for the storage volume.
• Write a simple rsync script or use Restic for snapshots.
• Schedule with cron (e.g., daily at 2 AM).

Vendor Backup Apps

If your primary NAS runs TrueNAS, you can use its built-in replication feature to push ZFS snapshots to a second TrueNAS system. Similarly, Synology and QNAP have their own backup suites (Hyper Backup, Hybrid Backup Sync). These are easy to set up but lock you into the same ecosystem. Using an open standard like rsync or Restic gives you more flexibility to switch primary NAS platforms later.

Where to Physically Place Your Backup NAS

The 3-2-1 rule requires one copy off-site. For a homelab, “off-site” can mean a friend’s house, a family member’s basement, or a small colocation cage. If that’s not feasible, at minimum place the backup NAS in a different room from the primary, ideally on a different floor or in a fire-resistant area.

For most homelabs, a realistic first step is to put the backup NAS in the garage, a basement, or a utility closet. This gives physical separation from the primary NAS (which might be in your home office or living room) without needing a second internet connection. If you have symmetric gigabit fiber, you can even place the backup NAS at a friend’s house across town and back up over WireGuard.

Sample Build: Budget Backup NAS (4-Bay)

This build targets the sweet spot for most homelabs: 4 bays, low power, and under $300 (without drives). It uses a used Dell OptiPlex Micro or similar mini PC with an added external drive enclosure, or a custom build with a cheap motherboard and an HBA.

With 4 x 12 TB drives (around $120 each), the total build cost is roughly $750-$820. This gives you 36 TB usable in RAID 5, enough to back up 10-20 TB of primary data with versioning. Idle power draw is around 15-20W, costing about $1.50-$2.00 per month at $0.12/kWh. See our guide on reducing NAS power consumption for more tips on optimizing this build.

Bottom Line: Which Backup NAS Build Should You Choose?

For 90% of homelab owners reading this, the answer is a 4-bay or 6-bay tower with a used HBA, a low-power CPU (Intel 8th gen or newer), and a minimal Linux install running rsync or Restic. This gives you the lowest cost per terabyte, the most flexibility in software, and the physical separation required by the 3-2-1 rule. If you already run Proxmox, use Proxmox Backup Server for seamless integration. If you need to mix drive sizes, Unraid is worth the license fee. The most important step is to start — a backup NAS with 4 TB of storage is infinitely better than no backup NAS at all.