HeartbeatHocusFocusFilesMacHyperTile
Guide

Time Machine, the backup system where the app is not the machine

The backup system measured on macOS 27: a 336 KB app whose whole menu is four commands, a 6 MB engine awake 30 days waiting for a disk, and a 28 verb command line older than your Mac.

By Chethan Kumar S N · Updated

You know the name. You may even know the starfield, the animation where your desktop floats backwards through its own history until you find the file you deleted on Tuesday. What almost nobody can answer is the simpler question underneath: what is the thing? Is it the app in the Applications folder? The preference pane in System Settings? The process called backupd that sits in Activity Monitor using almost nothing, forever?

This page answers it the way this series answers everything: by reading the system itself. The Mac used here runs macOS 27.0.1, has been up for 30 days, and has no backup disk attached. That last fact turns out to be a feature for once, because it shows the machinery in its resting state, which is the state most Macs are in.

The app is a doorbell

Start with the app, because it is the smallest surprise on the page.

Path       /System/Applications/Time Machine.app
Size       336 KB
Identifier com.apple.backup.launcher
Version    1.3 (build 102.0.3, source 102000003000000)
Project    Docklets

Read the identifier again. Not com.apple.TimeMachine. The app’s own name for itself is a launcher, and the version plist’s internal project name, Docklets, tells you where it came from: it grew up as a Dock companion, not as a working app. Version 1.3 is not a typo either. The engine beside it ships as build 102.0.3, and the app holding the icon has barely moved its version number in years, the same trick the Activity Monitor page caught in reverse, where the app read 10.14 on a Mac running 27.

If you want the entire feature list of the app in one place, it fits in one file, Menu.plist, four commands:

command 1   Open Time Machine Settings...
command 2   Back Up Now
command 3   Stop Backing Up
command 4   Browse Other Time Machine Disks...

That is the whole app. Open settings, back up now, stop backing up, browse other disks. There is no window of its own to speak of, no preferences of its own, nothing to configure. The binary inside is so thin that its strings are worth reading precisely because there are so few of them, and the two that matter are:

com.apple.peabody.backupnow
x-apple.systempreferences:com.apple.Time-Machine-Settings.extension

The second string is a doorway into System Settings. The first is the bell itself: a Mach service name ending in backupnow, which is the whole message. When you click Back Up Now, the app does not run the backup, it rings that bell, and the process that answers it is somewhere else entirely.

The engine lives in CoreServices

Somewhere else is here:

/System/Library/CoreServices/TimeMachine/
  backupd          6,265,152 bytes   the engine
  backupd-helper     526,960 bytes   its assistant
  brtool             627,216 bytes   a boot restore tool
  TMHelperAgent.app                  menu bar helper, still carries a .nib

The engine, backupd, is eighteen times the size of the app that carries its name. Measured live, on a Mac where it has nothing to do:

PID        574
User       root
Elapsed    30-00:15:57      (whole session, never exited)
Runs       1                (launchd count: started once)
CPU total  5:26.86          (about eleven seconds a day)
Memory     3.5 MB
State      tmutil status:  Running = 0,  Percent = -1

Two numbers in that block do all the explaining. Never exited in thirty days, and Running = 0. backupd is awake the entire life of the machine, the way a night watchman is awake, and with about as much to do until you give it a disk. Its assistant, backupd-helper, was up four days on a quarter of the memory. Neither is a problem, and neither can be usefully quit: they belong to launchd, which would simply start them again.

The third file is the strange one. brtool, sitting in the Time Machine folder, has nothing to do with hourly backups. Run it with no arguments and it introduces itself:

Usage: brtool update <vol> -f
       brtool listboots <vol>
       brtool erasefiles <srcVol> <bootDev>
       brtool copyfiles <src> <bootDev>[/<dir>] [<BlessStyle>]

Boots, not backups. brtool is boot restore machinery, the code that puts files onto a startup disk in the right blessed order, which is installer and recovery territory. It lives in the TimeMachine folder because the engine’s file copying code and the installer’s file copying code grew up sharing a toolbox, and the folder kept both. The name decodes the same way the whole series decodes: not from marketing, from the strings.

The dictionary is a manual page

There is a user guide hiding in the last place most people look, a manual page, and it is the closest thing Time Machine has to a written constitution. It ships on your Mac right now:

man tmutil
TMUTIL(8)   System Manager's Manual
Mac OS X    10 June 2015

The date line still says Mac OS X. The page defines a nine term vocabulary for describing backups, realms it calls them, and the definitions come with worked examples that Apple has never updated, which is exactly why they are worth reading. A machine directory example:

/Volumes/Chronoton/Backups.backupdb/thermopylae

Chronoton was somebody’s backup disk. thermopylae was somebody’s Mac. The backup examples all carry 2011 dates, which means the manual’s examples are older than several Macs reading this page, and the paths they describe, Backups.backupdb on HFS+ disks, are still what an HFS+ destination looks like today, because the format has to stay readable for disks created fifteen years ago. Backward compatibility, in one folder name, forever.

The manual also inventories its own tool, 28 verbs, and the list is a better feature tour than any settings screen:

destinationinfo    listbackups         latestbackup     restore
setdestination     removedestination   setquota         machinedirectory
startbackup        stopbackup          calculatedrift   compare
enable             disable             inheritbackup    associatedisk
addexclusion       removeexclusion     isexcluded       uniquesize
listlocalsnapshots deletelocalsnapshots thinlocalsnapshots
listlocalsnapshotdates  localsnapshot  verifychecksums
delete             deleteinprogress

Some of these are small stories in one word. calculatedrift measures how much the time on your Mac drifts against the backup disk’s clock, because a backup history is useless if the timestamps lie. inheritbackup is what lets a new Mac adopt an old Mac’s backup history instead of starting over. verifychecksums walks a backup and checks every file against its stored checksums. uniquesize answers the question that has annoyed everyone who ever owned two Macs: how much of this backup is actually unique, and how much is the same data counted twice.

One warning in the manual deserves quoting whole, because it is the opposite of what people assume: Several, but not all, verbs require root and Full Disk Access privileges. The backup system will not even let its own command line read backup history without you granting that terminal Full Disk Access first. A backup tool that locks itself out of its own files unless explicitly let in is a privacy decision, not an accident.

The resting state, measured

What does a Mac with no backup disk look like from the inside? Three commands, three one line answers:

$ tmutil destinationinfo
tmutil: No destinations configured.

$ tmutil listlocalsnapshots /
Snapshots for disk /:

$ defaults read com.apple.TimeMachine
Domain 'com.apple.TimeMachine' not found.

No destination. No snapshots. Not even a preferences file. This is the honest state of Time Machine on a Mac that has never configured it: the engine has been awake for a month, and every part of the system that could remember a backup, the destination list, the snapshot log, the settings, is empty.

That emptiness has a payoff. The local snapshot loop, the one that takes a snapshot of your disk roughly every hour and keeps about a day of them, only runs when Time Machine is on. Zero snapshots here means zero hidden storage, and the system data page measures the other case, where snapshots are one of the reasons the storage bar will not add up. If you want your own answer, one command reads it, and it comes back in under a second.

There is one caveat worth knowing before you panic about any of this. A Mac in this resting state is a Mac with no history. Nothing on it is backed up unless something else is doing the job, and iCloud syncing, which is on by default for many folders, is not a backup. It is a mirror. A mirror shows you the file you have. A backup shows you the file you had.

Born 2007, still counting

The app’s resources hold 41 language folders, and reading a few of them tells the age of the thing. The Catalan folder keeps the English name, Time Machine, untranslated, the way some product names simply never localize. The Arabic folder renames the app entirely, in Arabic script, the clock part of the metaphor surviving translation better than the words around it. And every folder carries the same copyright line, which starts:

Copyright (c) 2007-2025 Apple Inc.

Eighteen years of copyright on a launcher that still calls itself version 1.3. Time Machine shipped with Leopard in 2007, and it has outlived the hardware it was designed for. The AirPort Time Capsule, the wireless backup appliance built to be its other half, was discontinued in 2018 and the engine barely noticed: the destination list today reads disk, AFP share, SMB share, and the last one quietly covers every network attached storage box ever made.

What happens when you plug a disk in

The resting state ends the moment you pick a disk in System Settings. What follows is the shape the manual has always described. The disk is added to the destination list. A first backup runs, initial in the manual’s vocabulary, and it copies everything not excluded, which for a full Mac is hours and for a large photo library is longer. From then on, backups are incremental, each one recording the differences since the last, all of them living side by side in the machine directory the manual defines, and when the disk eventually runs low, it is the oldest states that give way first.

Two settings matter more than the rest, and both live in the Time Machine pane. Back Up Automatically is the switch for the hourly loop, including the local snapshot side of it. The exclusion list, which the manual exposes as addexclusion and isexcluded, is the one to actually read through: the list you see starts short, system internals are handled on their own, and if you have ever wondered whether your Downloads folder is being copied every hour, that list is where the answer lives, and the answer is usually yes.

See for yourself

Everything on this page came from read only commands, and none of them change anything:

tmutil destinationinfo          what disks, if any
tmutil status                   is a backup running right now
tmutil listlocalsnapshots /     the short term history on this disk
ls -l /System/Library/CoreServices/TimeMachine/
plutil -p "/System/Applications/Time Machine.app/Contents/Resources/Menu.plist"
man tmutil                      the constitution, 28 verbs and all

Run the first three on your own Mac and you will know, in about five seconds, which of the two machines this page described you are holding: the one with a month of history on a disk somewhere, or the one with a patient engine, zero destinations, and a doorbell for an app.

Questions

What is Time Machine on my Mac?

Two things with one name, and neither is what the icon suggests. The app in your Applications folder, the one with the clock icon, is a 336 KB launcher whose entire menu holds four commands and whose bundle identifier reads com.apple.backup.launcher. Pressing its Back Up Now button does not back anything up; it rings a bell for a separate process, backupd, a 6.2 MB engine living in /System/Library/CoreServices/TimeMachine that does the actual copying. Time Machine the system was announced in 2007 and the copyright string inside the app still starts that year. On the Mac measured here, a 30 day old macOS 27.0.1 machine, the engine has been running the whole month with no backup disk configured, which is its normal state on most Macs.

How does a Time Machine backup actually work?

The utility's own manual defines the pieces. A backup is a directory or snapshot that represents a single initial or incremental backup of one computer. The first one to a new disk copies everything you asked it to keep. Every backup after that is incremental: it records what changed since the previous one, and the manual's own vocabulary calls each stored state a snapshot, a machine directory holds all of them for one computer, and the whole collection sits on a backup disk, which is an HFS+ or APFS volume, or a share on a network server. On APFS Macs there is a second, shorter loop: local snapshots of the startup disk, stored on the same disk as the original files, taken roughly hourly and kept for about 24 hours so a backup that has not run yet still leaves you something to restore from.

Can I back up to iCloud instead of buying a disk?

No. Time Machine cannot use iCloud as a destination, and this is not a policy buried in a support note, it is visible in the command line tool's own definition of what a destination can be. The setdestination verb accepts exactly three things: an HFS+ or APFS volume plugged into the Mac, or an AFP share, or an SMB share, given as a network URL. iCloud is none of the three. iCloud Drive does sync documents and desktop files to Apple's servers, but that is a mirror of current files, not a history of past states, and the two systems solve different problems. A backup answers the question what did this file look like last Tuesday. Sync answers where is my file right now.

What is backupd in Activity Monitor, and why is it always running?

It is the engine, and always running is the design. Measured on a Mac with no backup disk configured at all: backupd has been up for 30 days without exiting once, as root, holding 3.5 MB of memory, with a total of 5 minutes and 27 seconds of processor time across the whole month, about eleven seconds a day. Its own status report, read with tmutil status, says Running = 0, because a waiting engine is not a working one. When its CPU column does climb, the honest reading is that a backup is genuinely underway: the first one to a new disk can run for many hours, and after that, hourly passes run for minutes. It never needs to be quit, and quitting it would not stop a backup anyway, launchd would start it again.

Is it safe to delete Time Machine snapshots to free up space?

Usually you do not need to, because the system beats you to it. Local snapshots are deleted as they age past about 24 hours or as space is needed, and macOS counts the space they hold as available storage, so they do not consume the room you need for downloads and installs. If you want to see them, tmutil listlocalsnapshots / prints them all, and it came back empty on the Mac measured here, which has Time Machine turned off. The manual does ship verbs for manual cleanup, thinlocalsnapshots and deletelocalsnapshots, and they require the same privileges as the rest of the tool. The safer habit is letting the system do the deleting, and reading the storage picture first, because a full disk with zero snapshots is a different problem than a full disk with forty of them.

Ready? Buy Ribbon for $15, or read all the guides.