Backing Up a Mac Properly

A backup is a promise a machine makes about a day it hopes never arrives, and like most promises it is only worth the rehearsal behind it. Time Machine, built into every Mac since 2007, is one of the genuinely good backup systems shipped inside a consumer operating system, and it is also one of the most underused, because setting it up feels like the whole task while it is only the first third. This guide covers the whole arc: the setup, the sizing of the drive, the honest limits of what gets protected, and the rehearsal that turns a backup from a belief into a fact.

What Time Machine actually does

Once a destination drive is chosen, Time Machine keeps an evolving history of the machine. It works in layers: hourly backups for the past day, daily backups for the past month, weekly backups beyond that, with older versions thinning out as the drive fills. Every backup is complete in the sense that the current state of every file can be reconstructed, and historical in the sense that changed files keep their earlier versions until space runs short. It also keeps local snapshots on the Mac's own disk, which is why a file deleted an hour ago can sometimes be recovered with no external drive attached at all. The interface for all this is a single Time Machine window that lets a user step backwards through the state of a folder, an application's documents, or the whole machine. Apple's own guide to backing up with Time Machine documents the mechanics current for each system version, and it is the reference to consult alongside this one.

Choosing and sizing the drive

The drive question has two parts, connection and capacity. Any drive the Mac sees can serve, though a drive that stays attached, or a network drive such as a router or a dedicated storage box, is what lets the hourly rhythm actually run. On capacity the honest arithmetic is simple: a destination smaller than the source cannot hold a full copy, and a destination barely larger cannot hold history. Two to three times the size of the data being protected is the comfortable working range, which lets weeks or months of versions accumulate before thinning begins. The exclusions deserve a deliberate pass on setup: folders of throwaway material, virtual machine images that change every hour, and downloaded installers can be left out, which buys real history for the files that matter. System Settings reports the destination's free space, and a yearly glance at it is part of the maintenance rhythm this magazine keeps recommending.

What it does not cover

The limits are worth naming precisely, because a false sense of coverage is worse than none. Time Machine backs up the Mac it is configured on, to the drive it is pointed at; it is not an offsite copy, and a fire, a flood or a theft that takes the desk takes both copies together. It backs up what exists at backup time; the photograph imported yesterday and the drive that failed this morning can miss each other by hours. And it is silent about other people's data: an iPhone's messages and photos are covered to the extent they are synchronised to the Mac or to a cloud account, not further. None of these limits is a flaw, they are simply the shape of one backup, and recognising the shape is what leads to the next section.

The 3-2-1 idea, adapted for a home desk

Professionals describe adequate backup with a small formula, three copies of the data, on two different media, with one copy offsite, and the formula adapts to a home Mac without ceremony. The first copy is the Mac itself. The second is the Time Machine drive, a different medium in the sense that matters, an independent disk whose failure is unconnected to the machine's. The third, the offsite copy, can be as plain as a second external drive kept at a relative's house or the office, refreshed monthly, or a cloud backup service for readers who prefer the automation; either satisfies the formula, because either survives the event that takes the house. The adaptations are honest about proportion: a working writer's machine needs the full formula, and a machine holding nothing but applications and a synchronised browser profile already lives half in the cloud. The formula is a set of questions, not a purchase list, and the answers differ by household.

The rehearsal that makes it real

Here is the step almost everyone skips, and the one that separates a backup from a hope: rehearse a restore, deliberately, on a quiet evening. The drill has three parts, in rising order of seriousness. Recover one file: open the Time Machine window, step back a day, and bring back a file that was deleted, confirming the interface and the muscle memory. Recover one folder: restore a documents folder from a week ago to a different location, confirming that history, not just the latest state, is really there; the Finder-level check of what came back is a one line ls for readers who followed the Terminal basics guide. And once, on a new machine or after a major upgrade, run the full restore, booting into recovery and rebuilding the system from the backup, because the middle of a crisis is the wrong time to learn that path. An hour spent on this drill changes the psychology of the machine: after it, the data is provably recoverable rather than presumably so, which is the entire point.

The small settings that matter later

Two settings earn their place at setup time and pay off years later. The first is encryption of the backup, offered when the destination is chosen: an encrypted backup protects the drive's contents if the drive itself is lost or stolen, which for a portable disk carried in a bag is not a hypothetical. The key is the recovery password, and it belongs in whatever system the household uses for such things, because an encrypted backup without its key is a paperweight. The second is the backup frequency: the hourly default suits a working machine, and readers whose work lands in bursts sometimes add a mid task manual backup, available from the menu bar icon, before a large change such as an operating system upgrade. Neither setting costs anything at setup, and both are awkward to retrofit after the bad day.

Backups and the wider workshop habit

A backup is the quietest member of the maintenance family this section keeps. The slow machine investigation in the checklist guide begins, rightly, with a backup before any large cleanup, and the scheduler story in the MacAT retrospective is at bottom the same lesson: the jobs that matter are the ones that run without anyone remembering them. Time Machine is that principle, built into the system, priced at the cost of one drive. The reader who sets it up this evening, sizes the drive honestly, adds one offsite habit, and rehearses the restore once, has done more for their future self than any amount of worry would.