Time Machine Not Backing Up on macOS Tahoe: Safe Fixes

If Time Machine stops backing up on macOS Tahoe, identify the failing destination and read the exact error before changing anything. A missing USB drive, an unreachable NAS, a nearly full startup disk and unfinished cloud syncing need different responses. Keep your existing backups intact while you diagnose the problem. Deleting the backup package might remove the only copy of a file you need later.

This guide is a preservation-first troubleshooting workflow, reviewed on November 1, 2026. It covers macOS Tahoe 26 without assuming every failure is a Tahoe bug. Where Apple documents a difference for newer macOS releases, it is identified separately. The decision tables and restore drill are practical recommendations, not claims of testing on a particular Mac.

Key Takeaways

• Start with the error message, destination type and date of the last successful backup.
• Keep the old backup untouched until a replacement is usable. Do not edit files inside a backup package.
• Treat a connection failure, a space warning and a cloud-sync delay as separate problems.
• A completed backup is only part of the check: recover a disposable sample file before relying on the setup.
• Do not paste passwords into Terminal commands or disable security protections as a generic fix.

First, Protect What You Already Have

Before trying repairs, write down which files exist only in the backup. Perhaps you deleted an old project from your Mac last month, or your current laptop contains only part of a previous computer's library. In those cases, the backup disk is also an archive. Erasing it would destroy information that a fresh backup of today's Mac cannot recreate.

If a disk is repeatedly disconnecting, making unusual noises or failing to read important files, stop experimenting with that device. Keep it available for recovery assessment and protect current work on a separate healthy destination. A repair attempt and a data-recovery attempt have different goals; do not confuse making a disk reusable with recovering its contents.

For ordinary failures without those warning signs, make a short record:

Record	Why it matters
Exact message and when it appeared	Distinguishes discovery, preparation, copying and restore failures
Last successful backup date	Shows how much recent work may be unprotected
Destination name and connection	Prevents troubleshooting the wrong disk when several are configured
macOS version and NAS or enclosure model	Lets support check the actual combination
Last relevant change	A new hub, network, account password or security app gives a useful lead
Any exclusions already configured	Explains why a successful job may omit an important folder

Take a screenshot rather than paraphrasing an error. Keep account names, server addresses and file paths private when posting it publicly. Do not attach an entire diagnostic archive to a forum merely because somebody asks for logs.

Choose the Right Troubleshooting Branch

Use this table as a triage tool. It combines the checks below; it is not a promise that a particular symptom has only one cause.

What you see	Investigate first	Safe next move	Avoid
USB or Thunderbolt disk vanishes	Cable, power and connection path	Test the drive directly on the Mac	Formatting a disk that intermittently disappears
NAS cannot be found or disconnects	Network reachability and supported backup share	Confirm the Mac and NAS can communicate	Editing the sparsebundle's internal metadata
Backup is preparing or slow	Whether work is progressing and what changed	Observe one attempt under stable conditions	Repeatedly cancelling and restarting it
Cloud-sync message	The affected sync service	Resolve syncing before expecting a complete backup	Turning off cloud storage without understanding the consequences
Destination is full	Capacity or NAS quota	Plan a larger destination or deliberate exclusions	Deleting backup folders in Finder
Snapshot cannot be created	Startup-disk space and disk health	Inspect the source disk, not just the destination	Deleting every snapshot as a first response
Backup finishes but files are missing	Chosen date, destination and exclusions	Test a known included sample	Assuming a green status covers every file

Your first milestone is a repeatable observation: for example, “the disk stays mounted directly but disappears through this hub.” That is more useful than making five changes at once and not knowing which mattered.

Check Status Without Resetting Time Machine

Open System Settings > General > Time Machine. Review the destination and configured options. Apple's Time Machine settings reference identifies the controls for backup frequency, destinations and excluded items.

Use the Time Machine menu to inspect progress or the latest completed backup. It also provides Back Up Now and the option to stop or skip the current attempt. Before physically disconnecting a backup disk, eject it or shut down the Mac. These controls are documented in Apple's Time Machine setup guide.

If you need to change a cable, stop the current attempt through the interface first. Once the new connection is stable, run one manual backup and record the outcome. If an attempt is progressing normally, do not restart it just because an online guide supplies an arbitrary deadline.

A useful troubleshooting note has four parts: the observation, the one change you made, the next result and the setting you restored. For example: “failed through dock; connected directly; next job completed; dock left out pending cable test.” This makes the result understandable to someone helping you later.

USB and Thunderbolt Backup Disks

Separate connection problems from backup problems

Apple's backup troubleshooting checklist recommends a direct connection rather than a USB hub. Check that the cable is secure and that an enclosure requiring external power has it. If the disk remains unavailable, investigate the storage connection before resetting Time Machine.

Change one component at a time: first bypass the dock, then test an appropriate known-good cable, then another compatible port. Label the disk if you own several identical enclosures. Do not select a different-looking device in Disk Utility simply because you expected your backup disk to appear there.

If the drive works directly, you have narrowed the problem; you have not yet proved whether the dock, its power supply, the cable or its interaction with other attached equipment is responsible. Reconnect only the components needed to reproduce the failure. For a broader storage diagnosis, see our external SSD troubleshooting guide.

Understand APFS without erasing good history

Apple describes APFS and APFS Encrypted as preferred formats for Time Machine. Its disk-format guide also documents support for Mac OS Extended formats and says an existing Mac OS Extended Time Machine disk is not automatically required to be erased. A Windows-formatted disk is not a usable Time Machine destination without reformatting. See Apple's supported disk formats.

That is different from saying every Tahoe failure means the disk must be converted to APFS. Before accepting any erase prompt, identify the physical disk, check what else it contains and decide whether losing the existing history is acceptable. When preserving that history matters, use a different disk for the new backup instead.

Do not confuse a local disk's format with the file system used internally by a NAS. Network backup support depends on the server's documented Time Machine implementation; selecting APFS in Disk Utility is not a general NAS repair procedure.

NAS and Network Backup Failures

Apple supports third-party NAS destinations that explicitly provide Time Machine over SMB. Follow the instructions for your NAS model and installed firmware rather than copying unrelated SMB tuning values. Apple also states that AFP network backups are not supported in macOS 27 or later; that newer-version boundary should not be presented as a Tahoe-only rule. See Apple's network backup compatibility guidance.

Work through these questions in order:

1. Is this the same network on which the backup previously worked?
2. Can the NAS be reached at all, independently of Time Machine?
3. Is the intended Time Machine share still enabled for the correct account?
4. Has an account password, access policy, quota or server update changed?
5. Does the NAS vendor document the installed macOS and firmware combination?

A Finder connection to an ordinary share is useful evidence, but it does not prove the share is configured for Time Machine. Similarly, seeing the NAS administration page does not establish that its backup service is available. Ask the vendor to distinguish network discovery, authentication, quota and backup-container errors.

Keep the backup account's credentials in the normal authentication interface. Do not include a password in a command URL, screenshot or support message. Changing the Mac's name, renaming the backup package or editing the package's machine-identity file is not a general solution for a network disconnect.

If you previously completed a network backup, Apple documents Option-clicking the Time Machine menu and choosing Verify Backups. This is a network-backup check, not a universal button for every USB disk. Use it when applicable and retain any error it returns. Keep the Mac on the same network as the destination while investigating. Apple's connection checks explain this distinction.

For supporting network diagnosis, see our SMB and NAS guide. If you still depend on older AirPort hardware, plan the transition separately using our Time Capsule migration guide.

Preparing, Slow Backups and Cloud Sync

When waiting is reasonable

A first backup and a later incremental job are not equivalent workloads. Apple notes that large files modified frequently, and apps repeatedly accessing the backup disk, can make jobs take longer. Its slow-backup guide recommends examining those workloads and consulting the app developer when necessary.

Compare like with like. Record whether this is the first backup to a destination, whether you recently imported a large library, and whether the backup reports changing progress. A single unchanged display is not enough to identify a broken backup. Conversely, a repeated identical failure at the same point deserves investigation rather than endless waiting.

Do not delete files ending in .inProgress or modify a backup's directory structure. If progress remains unclear, retain the error and support context, stop through the Time Machine interface when necessary, and make one controlled retry after addressing the identified condition.

When cloud syncing blocks completion

Apple says cloud-sync services can delay Time Machine until syncing finishes. Keep the Mac powered and online. If protected files are unavailable, try a manual backup while the Mac is unlocked. These are documented responses, not proof that iCloud Drive itself is broken. Apple's troubleshooting guidance covers both messages.

If you choose to exclude a sync folder temporarily, write down precisely what is being left out and how you will protect it meanwhile. A successful backup with that exclusion does not resolve the underlying sync failure. Remove the exclusion after syncing recovers and verify that a later backup includes the needed file.

Do not sign out of iCloud or toggle storage optimization merely to get rid of a backup warning. First establish which service and folder are involved. Our iCloud Drive guide provides separate context for sync troubleshooting.

Full Disks, Exclusions and Local Snapshots

Source space and destination space are different

A warning about the Mac's startup disk is not solved by increasing a NAS quota. A warning about the backup destination is not solved by removing a few downloads from an unrelated external disk. Identify which device the message names before you act.

Time Machine manages older backups as its destination fills. If capacity remains insufficient, Apple recommends using a new backup disk; selective exclusions are another option. See what to do when the backup disk is full.

Prefer a larger separate destination when old versions matter. Excluding a folder is a coverage decision, not a free performance improvement. For each proposed exclusion, ask: “If the Mac disappeared today, where would this folder come from?” If you cannot answer, do not exclude it simply to make the warning disappear.

Apple's exclusion instructions place the list under Time Machine Options. Add only the intended item, and remove it from that list when you want it backed up again. Keep a small record of temporary exclusions so they do not become permanent omissions.

Do not start by deleting snapshots

Local snapshots live on the Mac, not on the external backup disk. Apple says their space is treated as available and snapshots are removed automatically as they age or space is needed. They can help recover a recent file while the backup disk is unavailable, but they do not protect against loss of the Mac itself. Apple's snapshot explanation is the appropriate starting point.

For a snapshot-creation error, inspect startup-disk space and disk health instead of assuming old snapshots must be purged. Avoid scripts that delete every snapshot. Keep the distinction between “freeing space on this Mac” and “preserving recoverable versions” explicit. Our System Data storage guide covers the broader storage investigation.

Troubleshooting Common Issues

The backup disk is read-only or reports errors

Use Disk Utility's First Aid, with important data protected beforehand. Apple's procedure works upward through the device's volumes, containers and finally the device; startup-disk repairs require macOS Recovery. Follow the actual device layout rather than copying a guessed disk identifier from a Terminal example. See Apple's Disk Utility repair procedure.

First Aid can repair certain file-system problems; it is not a guarantee of hardware health or recoverability. If it cannot repair the disk, preserve any unique history before considering an erase. Seek recovery advice when the failing disk holds the only copy of important data.

Security software or a VPN may be involved

Do not switch off the firewall globally or create broad scan exclusions on speculation. Record the app and version, check its vendor guidance and ask your administrator before changing managed protections. If an approved diagnostic change is necessary, make it narrow, temporary and reversible, then restore the setting after the test.

A backup succeeding after a change is evidence to investigate, not proof that the product is generally incompatible. Avoid carrying an experimental security configuration forward as a permanent repair.

A new backup succeeds but the old history does not appear

Check that you selected the intended destination and date. Do not rename or merge backup folders manually. Keep the old device intact while establishing what history is accessible and which Mac created it. A new backup protects current files; it does not recreate earlier deleted versions.

You are considering starting again

Before replacing a backup, complete this checklist: identify unique historical files; confirm another copy of current essentials; choose the replacement destination; keep the old disk labelled and untouched; complete a new backup; and perform the restore drill below. Only then decide what to do with the older device.

Verify the Repair With a Sample Restore

This is a suggested acceptance test using a disposable file, not a report of a test performed on your Mac.

1. Create a small, uniquely named text document in a local folder included in backups. Write a recognizable sentence inside it.
2. Run a backup and confirm that the completed backup is later than the sample's creation time.
3. Move the original sample into a separate temporary folder so you will not overwrite it during the check.
4. Open the original folder, enter Time Machine, select the relevant backup date and restore the sample.
5. Open the restored document and compare its contents with the original. Record the destination, backup date and result.

Apple's restore instructions for Tahoe explain browsing the timeline, selecting an item and restoring it to its original location. Use a disposable sample precisely because restoring an older version of real work can create an unwanted replacement.

The test establishes a limited but useful result: one chosen file was recoverable through the workflow. It does not prove every file, exclusion or older backup is sound. Separately inspect the coverage of your most important folders and keep an independent copy of irreplaceable material. See our Mac backup strategy guide for planning beyond a single destination.

FAQ

Should I erase the backup disk to fix Time Machine?

Not as an opening step. First determine whether it contains historical files absent from your Mac. Preserve those before changing the disk. When possible, establish a working backup on another destination and test recovery there. Erasing the original disk removes history that a new backup of current files cannot replace.

Does macOS Tahoe require every backup disk to be APFS?

Apple prefers APFS or APFS Encrypted, but its documentation also describes supported Mac OS Extended formats and existing backups. Do not interpret a general backup error as an automatic instruction to reformat. Confirm the destination type first: a directly attached disk and a vendor-managed NAS require different checks.

How long should Preparing Backup take?

There is no useful universal deadline for every library, disk and network. Compare the workload with earlier jobs and watch whether progress changes. An initial backup after a large import is different from a small daily update. A recurring explicit error is a stronger diagnostic signal than an arbitrary number of minutes.

Can I delete the sparsebundle or incomplete backup files?

Do not manually modify them as routine troubleshooting. You risk sacrificing history without resolving the connection, capacity or access issue that caused the failure. Keep the package intact, collect the exact error, and use the supported Time Machine interface and NAS-vendor guidance. A different destination is preferable to experimenting on your only backup.

Is a local snapshot enough while the backup disk is broken?

Treat it as a possible short-term recovery aid, not independent protection. It remains on the same Mac whose data you need to protect. Keep current important files on another healthy destination while you resolve the external or network backup problem, especially if the original backup is no longer readable.

When can I consider the problem resolved?

Use three checks: the intended destination completes a new backup, the folders you need are not accidentally excluded, and a disposable sample restores correctly. Record what changed and restore temporary diagnostic settings. If jobs fail again under normal conditions, the successful test narrowed the issue but did not establish a lasting repair.

Conclusion

A reliable repair preserves your options. Identify the failing layer, make one reversible change at a time, and keep older backups intact while you establish a usable replacement or restore the existing workflow. Finish with a real sample-file recovery rather than stopping at a completed-job message.

Related reading: Mac backup strategy and external SSD troubleshooting.