Alternative title: “How I Wasted Five Hours of my Life Doing Something That Should Have Been Really Simple”.
A few months ago, my original Apple AirPort Time Capsule, purchased October 2009, finally bit the dust. The original 1TB hard disk drive built into the network router + wireless access point + file share server device succumbed to its age. 11 years in tech years is basically 111 years, after all.
As sad as it was to lose the oldest working piece of tech I owned (along with all my historical snapshots), I had been mentally prepared for the inevitability and what the next steps were.
Since macOS High Sierra, all Macs are capable of sharing any storage volume — internal or external — as a Time Machine backup disk over the local network. Previously that feature had been reserved for the now-defunct macOS Server suite. That feature relocated into the File Sharing pane of System Preferences, allowing anyone to setup their own Time Machine destination.
So now all I had to do was purchase a large solid state drive, plug it into the family Mac mini, and BOOM! Time Machine lives again on the network. Easy.
It wasn’t.— Narrator
If you want to jump right to the solution and skip my rambling and public troubleshooting, just go to the bottom.
A Quick Word on File Systems
I’m not going to break down all the differences between HFS+ and APFS. It’s entirely irrelevant to this discussion and quite honestly is way beyond my understanding. Just know this:
For about fifteen years, HFS+, labeled “Mac OS X Extended (Journaled)”, was the default file system on Macs since MacOS 8.1. It was neat and did a lot of things. Apple introduced APFS as the default file system with macOS High Sierra in 2013, along with the adjacent iOS releases. APFS was neater and did even more things.
From then on, all new Macs shipped with macOS High Sierra and above were formatted as APFS. Anytime you format a new storage device, it defaults to APFS. When I received my new SSD that was destined to be the Time Machine volume, naturally I plugged it in and formatted it as APFS.
And here’s where the trouble begins…
Time Machine, a key feature of macOS since Mac OS X 10.5 Leopard, does not support APFS. Well, currently it does’t. Apparently Time Machine on macOS Big Sur will support APFS. I’m running the macOS Big Sur Beta on my personal MacBook Pro. The Mac mini acts as a media server as well as a VM host for many network resources, including a web server for this website. Therefore, it’s still on the last stable build of macOS, 10.15 Catalina.
The differences of APFS support became really problematic in troubleshooting the ultimate cause of the upcoming fiasco.
You cannot have your cake and eat it, too. Unless you have two cakes.
The first thing I did was plug the empty SSD into the Mac mini via the USB 3 port. Once I got the Mac mini backed up, I would share the drive over SMB. I turned on Time Machine, selected the SSD, enabled encrypted backups, and started the backup.
However, right before the backup initialized, Time Machine informed me that the drive would have to be “erased” because the drive was not compatible. In Apple speak, that means it has to be reformatted. It was here that I realized APFS was a no-go. It reformatted the SSD as HFS+ Encrypted, since I had selected encrypted backups; this, later, proved to be an issue.
Since the Mac mini is basically a glorified internal server, there was not much to backup when excluding the /System and /Applications directories, so the initial backup went really quick.
(Aside: My old Time Capsule had a 5400rpm hard disk drive and a 100Mbps network card. A 10Gb initial backup would have taken an hour. This Samsung EVO SSD over a 5Gbps USB 3 bus took about 30 seconds with the symlink overhead. Pure ecstasy.)
With the Mac mini backup completed, I went into System Preferences > File Sharing, selected the drive, and enabled it for use with Time Machine. What this does is broadcast the drive’s availability and feature set over Bonjour. If your network is set to block multicast packets, Bonjour, and thusly Time Machine over the network, will not work. You won’t even see the drive as an option on networked Macs.
On my MacBook Pro, I enabled Time Machine, selected the networked drive (yay, that part worked), logged in with my Mac mini credentials, and started it up.
Except, there was an error: “You do not have the necessary read, write and append privileges on the selected network backup disk.”
… okay. That doesn’t make sense. So just to be sure, I added my local account to the file sharing pane for the shared Time Machine drive, and I added my account to the drive’s permission set (CMD+I).
Still, same error.
To be safe and because I’m relatively insane, I repeated the process to no avail.
Solution: A Pair of Volumes
To summarize the previous discoveries:
- To use a volume as a local Time Machine, it can and should be formatted as APFS
- To use a volume as a networked Time Machine, it can only be formatted as HFS+.
- A networked volume cannot be used by the host/local machine.
So what do you do if you only have one external drive (or only one free USB port) and you want to have a networked Time Machine drive and backup the host machine? The “duh” solution I came up with after hours of pulling my hair was to partition the drive. One partition was ten percent of the drive, formatted APFS for host backups, and the remainder was an HFS+ partition for networked backups. Time Machine does not know the difference between two partitions/volumes and two separate external storage devices.
Of course this is not the most efficient use of space because these partitions are not flexible per the needs of the backup. You’ll have to figure out how much your host machine needs. (Pro tip: backup volumes should be 5x-10x the size of the data being backed up. If your estimated initial backup size is 200GB, you’ll need 2TB.)
Finally. Both the host Mac and networked Macs were able to backup to the external SSD.
Is this annoying? Yes. Should Apple fix it? Yes. Will they? Hell no.
6 thoughts on “Setting Up a Networked Time Machine Server in 2020”
Tim, I have no hair to pull out. Was racking brain all morning why this no longer worked and keep forgetting how APFS has horked things up. I have a 8TB drive connected to a Mac mini, partitioned to 5 APFS/ 3 HFS+ and now is working like a charm. Many many thanks.
You’re welcome, Allen. Apple’s documentation is really lacking on this. Even with Big Sur, it’s still not working without jumping through hoops.
It’s worth noting, if like me you are running Catalina, that the HFS+ restriction applies to the local/host machine with this too. In my case it is in an APFS container, but I suspect that’s a level of complication (or just trying to get things to work), that is not strictly necessary.
Thank you very much!
This solved my dilemma on Big Sur 11.6 with a 6TB external on a MacPro.
I can now backup local (the Pro) and networked laptops.
Just as a comment to all who struggle with implementing Time Machine Backups through the local Network.
Some key information you should consider:
1.) MacOs Big Sur DOES in fact support APFS formatted drives, HOWEVER – as I discovered – you must use *APFS CASE SENSITIVE*, plain APFS Format does not work with Time Machine. Unfortunately Apple is NOT so kind as to mention that, instead they just claim it “works with APFS”.
2.) Mac OS Journaled Format does also work with Time Machine
3.) Local Hard Drives that are being selected as local Time Machine Backup Drives are being marked as such by the operating system. You can share them through file sharing just as any other drive, local computer can access the drive as well, but they will be unable to write to it. Thus, Time Machine through the network will not work.
I had a perfectly working local+network Time Machine backup set-up going. I originally set it up a couple of macOS versions ago, presumably before Time Machine insisted on APFS for local backups; so the drive was a single HFS+ partition and it worked.
Something happened to the drive, so I reformatted it, again as HFS+. When I went to use the drive for local backups (now using Monterey), it “prepared” the drive — which means it retroactively reformatted it as APFS — which means it wouldn’t work for networked backups. But if I reformatted it again as HFS+ then if I used the disk for network backups *before* using it for local backups, then it worked for both. But when I tried to add a second networked machine, however, it again generated the permissions error — this despite the fact that the first networked machine was working fine.
So I ended up using your solution of partitioning the drive into an APFS partition for local backups and and HFS+ partition for networked backups. Thanks!
FYI: when partitioning, it asked me whether I wanted to create a true partition or merely another volume inside the APFS container — the advantage of the latter is that they can share free space unlike true paritions. Since I was fed up dealing with this problem, I didn’t try that to see if that would work (assuming the added volume could be HFS+ inside an APFS container).