Time Machine Backup Failed, Stuck, or Too Slow: A Complete Mac Troubleshooting Guide

Time Machine is designed to make Mac backups mostly automatic, which is exactly why a failed backup feels so vague. You may see “Preparing backup” for hours, a read-only disk error, a full-disk warning, unavailable files, or a network backup that disconnects halfway through.

The useful approach is to match the fix to the error rather than deleting the entire backup and starting again.

First: is this the first backup?

The first Time Machine backup can be very slow because macOS has to copy a large amount of data.

Apple recommends allowing the initial backup to run while the Mac has time to remain idle. On a laptop, connect power. If the backup target is on the network, a wired Ethernet connection can make the first backup much faster and more stable.

Subsequent backups are usually smaller because Time Machine backs up changes.

If Time Machine stays on “Preparing”

Preparation can take longer after a major macOS update, a large file change, or when Time Machine has a lot to compare.

Give it time before interrupting it.

If it repeatedly remains stuck, check for third-party antivirus or security software. Apple specifically notes that virus scanning can interfere with Time Machine preparation and recommends excluding the backup disk from automatic scanning.

If the backup disk is read-only

A read-only error can indicate a disk or file-system problem.

Open Disk Utility, select the backup disk, and run First Aid.

Do not immediately erase the disk. A repair attempt and a current copy of important files should come before destructive formatting.

If Time Machine says the backup disk is full

Time Machine normally manages older backups, but capacity still matters.

Apple recommends a backup disk with substantially more capacity than the data being protected; its current troubleshooting guidance suggests at least about twice the size of the data you are backing up.

If the disk cannot accommodate the backup history you need, use a larger disk or exclude genuinely unnecessary large data.

Do not exclude irreplaceable folders simply to make the error disappear.

If Time Machine cannot create a local snapshot

A nearly full internal Mac drive can prevent snapshot creation.

Open System Settings > General > Storage and free space on the Mac itself.

Large downloads, virtual machines, video caches, iPhone backups, and application data are common storage consumers.

If some files are “unavailable”

Time Machine may retry later when a locked or encrypted file becomes available.

Apple notes that some encrypted files cannot be accessed for backup while the Mac is locked. Retry while the Mac is unlocked and active.

If a network backup disconnects

Check whether the NAS, supported network destination, or network path remains available in Finder.

Test the Mac on Ethernet if possible. Restart the router or NAS only if doing so will not disrupt other users.

Third-party firewall software can also interfere with network backup traffic.

If the backup drive disappears

For a USB drive:

• Reconnect it directly to the Mac.
• Temporarily remove USB hubs or docks.
• Try another known-good cable.
• Check whether the drive appears in Disk Utility.

If the physical disk itself repeatedly disconnects, do not blame Time Machine until the USB cable, enclosure, power supply, and drive health have been checked.

Why is Time Machine suddenly very slow?

Apple says Time Machine deliberately reduces its impact when the Mac is busy, hot, or low on battery.

Security scanning can slow it substantially. So can a slow USB connection or Wi-Fi path.

If you are using an external USB disk, make sure it is connected through an appropriately fast USB port and cable rather than an old hub bottleneck.

Check whether one folder is constantly changing

Virtual-machine disks, developer build outputs, large database files, caches, and other constantly changing data can create very large incremental backups.

Only exclude such content when it can be recreated or is backed up through another appropriate method.

Do not erase the backup as your first troubleshooting step

A years-long Time Machine history can contain the only easy copy of a file you deleted months ago.

Before starting over, understand the error, run disk checks, verify connectivity, and make sure important data has another backup.

When starting a fresh Time Machine disk does make sense

If the backup disk is physically failing, corrupted beyond repair, too small, or no longer trustworthy, replace it.

Keep the old disk untouched until the new backup has completed and you have verified that important files can be restored.

Test restores, not only backups

A backup strategy is only useful if recovery works.

Occasionally enter Time Machine or use its restore workflow to retrieve a non-critical test file. That confirms you know how restoration works before you need it during a real emergency.

If backups became slow after a macOS update

Update macOS fully, restart the Mac, and check third-party antivirus, storage, and network software for compatible updates. A backup issue that begins immediately after a system update can be caused by an extension or security product rather than the backup disk itself.

Do not downgrade macOS or reformat the backup just because the timing looks suspicious; isolate the surrounding software first.

Official references

Apple Support — If you cannot back up or restore with Time MachineOfficial reference Apple Support — If a Time Machine backup is slowOfficial reference