Reachable Is Not Recoverable: A Time Machine Backup Review

The proposal sounded practical: keep an older iMac running on the local Ethernet network, attach an existing hard drive, and let the computers in a multi-device environment use it for Time Machine.

The idea was workable; the initial capacity assumption was not.

Our review began with a distinction that is easy to miss: a reachable storage share is not necessarily a configured backup destination, a completed backup is not necessarily current, and none of those states proves that a file can be restored.

In the environment we examined, the network share was online and visible. It was already carrying a substantial amount of data and had roughly half of its usable capacity free. The selected workstation’s storage requirement approached the remaining space. Time Machine, however, reported no configured destination.

That evidence changed the recommendation immediately.

Capacity comes from evidence

Apple advises using backup storage with at least twice the storage capacity of the Mac being protected. A fixed pilot limit had appeared reasonable when looking only at the network drive’s free space. A second technical review caught the flaw: the proposed limit was smaller than the selected workstation’s existing data, and far below the capacity needed for useful backup history.

The correction was simple but important. The plan stopped naming an arbitrary quota and instead required a complete inventory of every eligible Mac. The pilot must now be either a smaller computer whose full capacity fits the backup pool with adequate reserve, or a larger backup destination must be installed.

Good infrastructure work is not the absence of corrections. It is a process that exposes assumptions early, records the evidence, and updates one authoritative plan before anyone acts.

The safe role for an older iMac

The iMac can serve as a secondary local recovery tier and a convenient fast-restore target. It should not become the primary location for working files, the only copy of critical information, or the assumed backup server for every device.

The host and client Macs also need a compatibility check. The reviewed share used SMB. Apple recommends shared-Mac destinations when both Macs run macOS 11 or later; AFP is unsupported in macOS 27 or later.

A safe pilot sequence

Inventory each device by type, operating system, full capacity, used space, criticality, and current backup method.
Separate Macs from mobile devices, which use iCloud Backup or encrypted Finder backups rather than Time Machine.
Verify the host Mac’s operating system, disk health, encryption, Ethernet connection, sleep behavior, restart behavior, and power protection.
Preserve all existing data before changing the drive’s layout or sharing configuration.
Create a dedicated Time Machine folder and a dedicated non-administrator account.
Choose one capacity-qualified pilot Mac and let its initial encrypted backup finish before adding another device.
Restore a disposable test file and verify its contents.
Add a separate encrypted offsite copy for critical business information.

SMB should never be forwarded directly to the public internet. A local backup in the same building also does not protect against theft, fire, electrical damage, or ransomware affecting both the source and the destination.

Size first, purchase second

A larger multi-terabyte system may be reasonable, but no capacity is justified until the device inventory is complete. The correct size follows the Macs being enrolled, their full storage capacity, expected growth, the desired history, and an operational free-space reserve.

For this review, the final decision was deliberately conservative: keep the current network drive in its existing role, do not erase or repurpose it, do not enroll the capacity-mismatched workstation, and do not describe the environment as backed up. Begin with the inventory, select a properly sized pilot, complete an encrypted backup, and prove restoration.

That is not slower infrastructure work. It is how a backup project avoids becoming a recovery failure.

Primary sources

Editor’s note: Operational identifiers, usernames, internal paths, precise host names, and private inventory details were intentionally omitted. The underlying review made no disk, credential, network, or backup-configuration changes. No storage product or vendor sponsored this analysis.