MacHow-To

Time Machine backup on Mac: a practical, no-nonsense guide

By Alistair Hartmann · August 25, 2026 · 11 min read

If you treat Time Machine as “set it and forget it,” you’ll eventually forget the one detail that matters: will you actually get your files back? This guide focuses on getting a reliable Time Machine backup in place—one that completes on schedule, can be restored quickly, and won’t surprise you with disk errors or week-long initial runs.

Choose the right disk (and size it properly)

Time Machine works with external USB/Thunderbolt drives, network volumes (SMB shares on a NAS), or another Mac shared as a Time Machine destination. For most people, a simple USB-C external drive is the least fragile and the fastest path to a dependable backup.

• Capacity: Pick 2–3× the amount of data you intend to protect, not the size of your entire disk. If you keep 600 GB of data on a 1 TB internal drive, buy a 2 TB or 4 TB backup disk. The extra space holds versions and makes pruning less aggressive.
• Drive type: A 3.5-inch desktop HDD in a decent USB 3.2 Gen 2 (10 Gbps) enclosure is the best value per terabyte and handles sustained writes better than many portable 2.5-inch SMR drives. Portable SSDs are fast and silent, but overkill unless you’re moving a lot of data or backing up over short windows. If you pick HDD, lean toward conventional magnetic recording (CMR) models for steadier performance.
• Cable and port: Connect with USB-C if possible, and avoid cheap hubs. A flaky hub can cause intermittent disconnects that silently poison backups.

Format the destination correctly

Since macOS 11 Big Sur, Time Machine prefers APFS-formatted destinations and gets major performance gains when it can use snapshots natively. If your drive is new, format it first:

1. Open Disk Utility and select the physical drive (not just a volume).
2. Click Erase.
3. Format as “APFS (Encrypted)” and give it a name you’ll recognize (for example, “TM-Office-2TB”).
4. Set a strong password and store it in your password manager.

Why encrypt at the drive level? It protects all versions at rest. Turning on encryption after backups begin takes time and leaves earlier data briefly unencrypted.

You can still back up to older HFS+ volumes, but if you’re starting fresh on modern macOS, use APFS.

Set up a reliable Time Machine backup

• Open System Settings > General > Time Machine.
• Click Add Backup Disk and choose your formatted volume (or network share).
• Enable “Back up automatically.”
• Click Options and exclude noisy or disposable folders (more on that below). This keeps versions meaningful and initial runs faster.

Time Machine will start an initial full backup. Let it finish with the display allowed to sleep but the Mac set to stay awake on power.

Keep the Mac awake while big backups run

Large first backups stall when the computer sleeps too aggressively.

• On a Mac notebook: System Settings > Battery > Options > check “Prevent automatic sleeping on power adapter when the display is off.” Keep the lid open and plug in power.
• On a desktop Mac: System Settings > Displays > Advanced > Prevent automatic sleeping when the display is off (or use the Energy Saver options on older macOS).

If the drive is bus-powered, plug it straight into the Mac. Avoid chaining it behind other high-draw peripherals.

While a first backup runs, you might browse the best online casino bonus or tidy your photo library—just don’t let the Mac sleep.

What to exclude (and what never to exclude)

Time Machine’s strength is versioning user data, not re-backing up throwaway caches.

Good candidates to exclude:

• Large, frequently regenerated data: node_modules, DerivedData (Xcode), Photoshop scratch disks, Lightroom preview caches.
• Virtual machine images you replace often. Consider backing those up separately on a different cadence, or take periodic manual snapshots/clones outside Time Machine.
• Temporary media staging folders and download folders where you don’t need versions.

Never exclude:

• Your home folder’s Documents, Desktop, and Library for apps that store data there (Mail, Messages, some third-party app data).
• Photos Library and Music Library packages, unless you have a separate, verified strategy for them.
• Cloud storage folders you treat as your only copy. iCloud Drive and Dropbox sync is not a backup.

Tip: For persistent excludes at the filesystem level, use Terminal:

• Add: tmutil addexclusion -p “/path/to/folder”
• Remove: tmutil removeexclusion “/path/to/folder”

Understand APFS snapshots and “mysterious” disk space

When your backup disk isn’t connected, macOS takes hourly local snapshots on your internal APFS volume so it can still give you versions. These snapshots live in your container’s “Other Volumes” and appear to eat space.

They auto-prune when space is needed. If you genuinely must clear them:

• List: tmutil listlocalsnapshots /
• Delete one: sudo tmutil deletelocalsnapshots YYYY-MM-DD-HHMMSS
• Aggressively thin: sudo tmutil thinlocalsnapshots / 9999999999

If you routinely need to thin snapshots, that’s a sign the main backup drive isn’t connecting often enough or is undersized.

Scheduling and cadence without extra software

Time Machine runs hourly, consolidates daily backups after 24 hours, weekly after a month, then prunes oldest when space is low. There’s no built-in scheduler to change the hourly tick. If you need fewer backups, exclusions usually solve the real problem (too much churn), and a larger destination helps versions go farther back.

If you must run manual jobs:

• Start now: tmutil startbackup —auto
• Stop a run: tmutil stopbackup
• Show status: tmutil status

For desktops, a daily snapshot is fine if the machine stays on. For notebooks, connect the drive whenever you’re at your desk so backups don’t stack up.

Verify your backups the practical way

There’s no point holding terabytes of bit-rot. Make verification mechanical:

• Do a small test restore monthly. Enter Time Machine from the menu bar, restore a few files to a temporary folder, open them, and confirm integrity.
• Try a “dry-run” Migration Assistant check before you need it. Open Migration Assistant and ensure your backup is detected and enumerates your user/data.
• Use tmutil compare to see what would be backed up and to spot unexpectedly huge churn:
  • tmutil compare -s -r / “/Volumes/TM-Office-2TB/Backups.backupdb/YourMac/Latest/YourDisk”

If verification fails or Migration Assistant can’t read the structure, stop trusting that disk. Copy what you can, erase, and start fresh.

Network Time Machine on a NAS (SMB), without tears

Backing up to a NAS is convenient but introduces more moving parts.

• Use SMB, not AFP. Modern macOS expects SMB. Your NAS should explicitly support Time Machine over SMB and advertise via Bonjour/mDNS.
• Create a dedicated share per Mac or per user. Set a size quota on the share so one Mac can’t consume the whole array.
• Let Time Machine create the sparsebundle. It will be named after your Mac and MAC address; don’t rename it.
• Wire the first backup. Connect the Mac via Ethernet to the router or directly to the NAS if supported. First runs over Wi‑Fi can take days.
• Keep the NAS healthy. Enable its own snapshots or RAID scrubs and SMART monitoring. Time Machine relies on the NAS storing the sparsebundle flawlessly; if the NAS silently corrupts data, your backup won’t save you.

If you get repeated corruption on a NAS, consider reverting to a directly-attached disk for primary backups and leaving the NAS as a secondary target.

Rotation: one on-site, one off-site

One disk isn’t a strategy; it’s a single point of failure.

• Buy two identical disks. Label them clearly (e.g., “TM-A” and “TM-B”).
• Keep TM-A connected daily. Swap with TM-B weekly. Store the idle disk off-site (work, family member’s house, a safe).
• Encrypt both volumes and keep the passwords in your manager. Test restores from both.
• If a theft, spill, or power event kills your Mac and one disk, the other still exists.

This low-tech rotation beats any single high-tech backup.

Restoring files, folders, and whole Macs

Different restore paths fit different disasters:

• Single file or folder: “Enter Time Machine” from the menu bar inside the Finder window showing the folder you care about. Navigate the timeline, preview, and restore. If a packaged library (like Photos), restore to a new location and open it with Option key in the app to avoid overwriting.
• System rollback after a bad install: Restart, hold the appropriate keys to enter macOS Recovery (on Apple silicon: hold the power button), choose Restore from Time Machine. Pick the date that predates the failure.
• New Mac migration: On first boot, choose “From a Mac, Time Machine backup, or startup disk.” Wire the drive. Migrate only what you need (users, applications, other files) to keep cruft from following you forever. If you already set up the Mac, run Migration Assistant later.

Network restores are much slower than from a directly-attached disk. When time is critical, plug in the drive.

When Time Machine isn’t enough

Time Machine is versioned and local. It’s not off-site unless you carry a rotated disk off-site. It’s also not an archival system for data you delete deliberately and expect to retrieve years later.

Complement it with:

• Cloud backup (true backup, not sync). A continuous off-site copy protects against theft, fire, and disasters that take both your Mac and your local disks.
• Periodic cold storage. For static archives (e.g., old video projects), consider a separate external disk stored offline, with at least two copies in different places.
• Occasional clones. Bootable clones are uncommon on Apple silicon due to signed system volumes and owner authorizations, but a data-only clone gives you a quick way to get working if a disk dies mid-project.

If you rely heavily on Photos or Final Cut libraries, keep an additional, app-aware export or library duplicate on separate media.

Common failure modes and safe fixes

• Preparing backup takes forever: The first run can be slow, but if it’s stuck for many hours with little disk activity, stop the backup (tmutil stopbackup), eject the drive, run Disk Utility First Aid on both the backup and internal disks, reboot, and try again. Exclude any massive, constantly-changing folders.
• “Backup failed” with I/O errors: Check the cable and port. Try another cable before blaming the drive. Run First Aid. If errors persist, replace the drive; don’t negotiate with failing hardware.
• “Not enough space”: Prune wisely. It’s safer to add a larger destination than to delete random versions. If you must delete old backups on a directly-attached disk, do it through the Time Machine interface (gear menu) or with tmutil delete, not by deleting folders in Finder.
• Backup disk won’t mount: Check if it shows in Disk Utility. If it mounts read-only, copy what you can, then erase and recreate the backup volume. Don’t keep backing up to a flaky filesystem.
• NAS sparsebundle corruption: Create a new share and start fresh. If you need any history, mount the old sparsebundle read-only and copy out must-keep files, then retire it.

Photos, Mail, and other app-specific quirks

• Photos: Back up the Photos Library like any other file. To restore, hold Option when opening Photos and choose the restored library. If you use iCloud Photos, Time Machine still protects edits and metadata as they existed at backup time.
• Mail: Time Machine captures on-disk mail stores and envelopes. Restoring individual messages works well via the Enter Time Machine interface in Mail.
• Xcode and containers: Many developer containers live in ~/Library/Containers and ~/Library/Developer. Don’t exclude these unless you’re certain you can recreate them from source control.

Time Machine with external and secondary internal volumes

If you have more than one data volume:

• Add all volumes you want protected in Time Machine’s settings.
• For external media projects, consider a dedicated backup disk for that media to avoid bloating your primary backup history.
• APFS volumes on the same physical SSD share wear. If you keep a secondary internal APFS data volume, ensure your backup strategy accounts for both and that you have off-site copies of anything irreplaceable.

Security and privacy

Encryption is non-negotiable on portable drives. Using APFS (Encrypted) at format time gives you whole-volume protection. With network backups, use user accounts and quotas on the NAS share. Don’t expose a Time Machine share to the internet.

Keep your backup passwords and NAS admin credentials in a password manager. If you lose the encryption password, Apple cannot help you recover the data.

Space management without killing history

To regain room gracefully:

• Tighten exclusions on churn-heavy folders.
• Add a second destination in Time Machine. It alternates automatically, increasing historical depth without throwing anything away.
• Upgrade the destination drive. Disk cost is almost always lower than the time cost of a partial history when you need it.

Avoid manual pruning unless necessary; it’s easy to remove the one snapshot you’ll later miss.

Restores after macOS upgrades and hardware repairs

After logic board replacement or certain repairs, your Mac may appear as a “new” machine to Time Machine. If you need to continue an existing backup set:

• Use tmutil inheritbackup to assign the new system to the existing backup.
• Use tmutil associatedisk to associate your current data volume with the historical data in the backup.

This prevents Time Machine from starting a brand-new history and wasting space.

Advanced tmutil recipes worth knowing

For readers who want command-line control, these are the ones to learn:

• List all backups:
  • tmutil listbackups
• See destinations:
  • tmutil destinationinfo
• Start/stop:
  • tmutil startbackup —auto
  • tmutil stopbackup
• Compare live files to last backup (summary and report only deltas):
  • tmutil compare -s -r /
• Bind a new system to an existing backup set after repairs or a replacement Mac:
  • tmutil inheritbackup “/Volumes/TM-Office-2TB/Backups.backupdb/YourMac”
  • tmutil associatedisk -a / “/Volumes/TM-Office-2TB/Backups.backupdb/YourMac/Latest/YourDisk”
• Thin local snapshots aggressively (when absolutely necessary):
  • sudo tmutil thinlocalsnapshots / 9999999999
• Delete a specific backup (use with care):
  • sudo tmutil delete “/Volumes/TM-Office-2TB/Backups.backupdb/YourMac/2026-07-19-130015”

Keep paths exact. A typo in a delete command removes the wrong thing. Practice on a test volume before using tmutil for destructive operations.