What Is a NAS Drive and How Does It Work for Time Machine Backups? | SMB Setup

Guide

A NAS drive is a networked storage server that gives every Mac in the house one shared Time Machine destination over SMB.

Time Machine fails quietly. A Mac that can’t reach its backup disk keeps working as if nothing is wrong, and the first sign of trouble tends to be the afternoon you need to restore a file.

A NAS drive for Time Machine backups handles the logistics: one box on the router, every Mac backing up to it over Wi-Fi or Ethernet, no external drive to plug in. The other half is protocol, and Apple has tightened those rules.

The table below lines up the settings that decide whether a scheduled backup runs or stalls.

Does Time Machine Still Work With Third-Party NAS Drives?

Yes, provided the NAS speaks SMB. Apple’s requirements for third-party NAS backups say the drive must support Server Message Block (SMB), and that AFP-based NAS backup and data transfer are not supported in macOS 27 or later.

Apple’s Mac User Guide still lists both SMB and AFP (Apple Filing Protocol) destinations and recommends SMB when a disk offers both, so a new setup has no reason to keep AFP alive.

Two gates decide whether the option exists at all. QNAP’s workflow calls for a Mac on macOS 10.12 Sierra or later and a QNAP NAS on QTS 4.3.0 or later. Older firmware can hide the Time Machine service entirely, which is why updating the NAS software comes first.

Setup Element What To Set Why It Matters
Protocol SMB, with SMB 3 as the highest version on QNAP AFP is unsupported for NAS backup in macOS 27 or later
Backup account A dedicated NAS user with read/write on one folder Keeps a leaked password away from the rest of your data
Shared folder One Time Machine folder with a maximum capacity Stops a single Mac’s history from filling the volume
Time Machine service Enabled on the NAS so it advertises itself Lets the Mac find the disk without hunting for an IP
NAS software Current firmware, QTS 4.3.0 or later on QNAP Older builds can hide the Time Machine toggle
RAID Useful for uptime only Survives a dead disk, not deletion, ransomware, or theft
Network Ethernet from the NAS to the router A weak connection delays every scheduled backup

A NAS Drive For Time Machine Backups: The Step Order That Works

Build the NAS side first, then point the Mac at the share. Reversing that order is the usual reason Select Disk comes up empty.

  1. Connect the NAS to the router with Ethernet, install the drives, finish the vendor’s first-run setup, and update the NAS operating system.
  2. Create a dedicated user for backups plus one shared folder, and give that user read/write access to that folder only.
  3. Turn on SMB file sharing. On QNAP, set Highest SMB version to SMB 3.
  4. Enable the vendor’s Time Machine service. On QNAP it sits under HBS 3 > Services > Time Machine, where you can also cap the maximum capacity.
  5. On the Mac, open Finder > Go > Connect to Server, enter smb://NAS-name.local or the NAS IP address, sign in, and mount the backup folder. Apple notes the Mac must be connected to the SMB server during that setup.
  6. Open System Settings > General > Time Machine, choose Add Backup Disk, select the shared folder, choose Use Disk, and enter the backup account credentials.
  7. Switch on automatic backups and encryption if the NAS offers it.

Within a minute or two the destination appears in Time Machine’s disk list with an estimated size and a countdown to the first backup.

Picking the box is the easier half. Our roundup of NAS drives tested for Time Machine backups narrows the field to models that expose these settings without a fight.

Where NAS Backups Break, And What Fixes Them

Permissions and capacity cause most NAS backup failures, not the hardware. Each problem below has a setting behind it.

  • Too much access. Handing the backup account the whole NAS invites accidents. Scope it to the Time Machine folder.
  • No quota. One Mac’s version history can swallow a shared volume. Set a maximum capacity on the folder.
  • AFP leftovers. If a guide tells you to enable AFP, skip it — SMB is the supported route now.
  • NAS extras that interfere. An encrypted shared folder or the NAS recycle bin can disrupt Time Machine depending on the vendor, so run a test backup before you trust one.
  • RAID mistaken for a backup. RAID keeps the NAS running after a disk dies. It does not survive deletion, ransomware, theft, or a dead NAS, so keep a second copy offline or off-site.
  • A network the Mac can’t see. Sleep, VPNs, congested Wi-Fi, and NAS downtime all stall backups. macOS reconnects on its own after setup, but only when the destination is reachable.

Three settings carry more weight than any spec sheet: SMB on, a dedicated account limited to one folder, and a quota on that folder. Get those in place and Time Machine over a NAS stops being fussy.

Common Questions

Can Time Machine back up to a NAS over Wi-Fi?

Yes. Apple only requires that the Mac be connected to the SMB server while you set the destination up. After that, macOS can reconnect automatically and back up over Wi-Fi. Ethernet still makes sense for the first full backup, which is large, and for any Mac sitting in a spot with weak signal.

What happens when the NAS is offline at backup time?

The scheduled run is delayed or interrupted, then picks up once the Mac can reach the share again. Several missed windows in a row mean you have no recent backup, so check the Time Machine menu for the last completed date. If that date is days old, reconnect before assuming everything is fine.

Is a NAS enough on its own for Mac backups?

Not for files you would hate to lose twice. A NAS is a single device in a single building, and RAID inside it only guards against disk failure. Keep a second copy on an external drive stored elsewhere, or add a second destination in Time Machine, so a stolen or burned NAS doesn’t take every backup with it.

Sources