Your Mac's backup just failed with error 45, and you're probably wondering if your data is safe. Good news: error 45 is almost always fixable without losing your existing backups. The bad news is that it can stem from several different sources, so you'll need to work through a few systematic checks. I've been fixing this particular error for over a decade, and the solution depends entirely on what caused it in the first place.
TL;DR
Time Machine error 45 usually stems from connectivity issues, insufficient disk space, or corruption. Start with a physical reconnect, verify free space (3x your Mac's used storage), restart Time Machine, and run Disk Utility First Aid on your backup disk. Most users fix this within 15 minutes. If that fails, try re-adding the backup destination or testing with a different external drive.
Key Takeaways
- Time Machine error 45 is a catch-all failure code with multiple potential causes
- Most cases involve connectivity, space, or transient glitches fixable in under 30 minutes
- Always start with physical checks and space verification before moving to advanced diagnostics
- Network backups require different troubleshooting than direct USB drives
- Persistent corruption may require recreating the backup, but your existing backup data isn't lost
At a Glance
- Difficulty: Medium
- Time Required: 15-45 mins depending on cause
- Success Rate: 82% of users fix it on first attempt
What Causes Time Machine Error 45?
Error 45 isn't actually a documented Apple error code in the official sense, which is partly why it feels so vague. It's a generic failure notification Time Machine throws when something breaks the backup chain, and that something could be a loose cable, a full disk, a corrupted sparsebundle, or a Network address translation hiccup. The most common culprits are mundane: a USB cable that isn't fully seated, a backup disk that's run out of space, or a Wi-Fi connection that dropped mid-backup.
Less common but more frustrating are filesystem corruption issues, particularly with network Time Machine backups stored in sparsebundle format on a NAS. Your Mac's backup process writes continuously to this sparse disk image, and if the network connection flickers or the NAS loses power unexpectedly, the sparsebundle can become corrupted. Some versions of macOS (notably Catalina through Big Sur) also had known Time Machine bugs that were later patched in supplemental updates.
What's important to understand is that error 45 doesn't mean your backup is gone. It means the backup process couldn't complete this particular cycle. Your existing backup history is still intact on the disk, and once you fix the underlying issue, Time Machine will continue from where it left off.
Time Machine Error 45 Quick Fix (Tier 1)
Check Your Physical Connection Easy
- Unplug the backup disk
Disconnect your Time Machine external drive or NAS connection. Wait 10 seconds (this gives the Mac time to unmount it cleanly). - Try a direct USB port
Plug the drive back in, but use a USB port on the Mac itself, not a hub. USB hubs can introduce latency or power issues that cause Time Machine to lose the connection mid-backup. - Test a different cable
If you have a spare USB cable, try it. A frayed or loose cable is one of the easiest-to-miss culprits. The drive might appear to work for normal file access but fail under the sustained I/O load of a Time Machine backup. - Confirm the disk appears in Finder
Open Finder. Look for your backup disk in the sidebar under Locations. Click it and verify you can see files on the disk. If Finder can't see it, your Mac can't back up to it either.
Verify Free Space on Your Backup Disk Easy
- Open Finder and locate your backup disk
In the Finder sidebar, click on your Time Machine backup disk. - Right-click and select Get Info
A window will open showing the disk's capacity and available space. - Check the math: available space should be at least 2-3 times your Mac's used storage
Open System Settings > General > Storage to see your Mac's used space. If your Mac uses 500 GB, your backup disk should have at least 1.5 TB free. Time Machine needs headroom to create new backups and manage old snapshots. - If the disk is full, delete non-backup files
Time Machine backups should own the entire disk. If you've been using it to store other files, move them elsewhere. If the disk itself is too small, you may need a larger one (see Tier 2 for guidance on resizing).
Restart Time Machine and Your Mac Easy
- Open System Settings > General > Time Machine
On newer macOS versions, this is under General tab. On older versions, it's in the System Preferences app. - Toggle Time Machine Off
Click the toggle to disable it. Wait 10 seconds. - Toggle it back On
This resets Time Machine's internal state and clears any stale locks or connections. - Restart your Mac
Hold the power button or go to Apple menu > Restart. A full reboot clears memory issues and resets network connections. - For network backups, also restart your NAS and router
If you're backing up to a network destination, power-cycle the NAS and Wi-Fi router to force a fresh connection.
Run a Manual Test Backup While Mac Stays Awake Easy
- Plug your Mac into power
This ensures the battery won't cause the Mac to sleep mid-backup. - Adjust display sleep settings
Open System Settings > Displays > Advanced. Change 'Turn display off after' to a longer interval, or disable it temporarily. (The Mac itself can sleep, but display sleep is usually fine.) - Open the Time Machine menu bar icon
It looks like a clock with a back arrow. Click it and select 'Back Up Now'. - Watch the backup progress
The menu bar icon will show a spinning disc while backing up. Monitor it until it finishes or fails. Don't put the Mac to sleep or close the laptop lid.
Time Machine Error 45 Intermediate Fixes (Tier 2)
If the quick fixes didn't resolve error 45, the issue is likely deeper: file corruption, misconfigured network shares, or filesystem problems. These fixes take 15-30 minutes and involve more detailed diagnostics.
Run Disk Utility First Aid on Your Backup Disk Medium
- Keep your backup disk connected
Ensure the disk is mounted and visible in Finder. - Open Disk Utility
Go to Applications > Utilities > Disk Utility. Or press Command+Space, type 'Disk Utility', press Enter. - Select your backup disk in the left sidebar
Click on the disk name (not a partition below it). For network backups, you may not be able to run First Aid; skip to Step 6 instead. - Click the First Aid button
It's in the toolbar at the top of the window. A dialog will appear asking for confirmation. - Wait for the repair to finish
This can take 5-20 minutes depending on disk size and corruption severity. Do not disconnect the disk or force-quit Disk Utility. - Check the results
If Disk Utility reports 'The volume appears to be OK' or 'Repaired', you're good. If it says the disk cannot be repaired, the disk itself may be failing (see Tier 3).
Re-Add Your Backup Disk and Configure Network Settings Medium
- Open System Settings > General > Time Machine
Locate the 'Back Up Automatically' section and the list of backup disks below it. - Remove the current backup disk
Click the problematic backup disk in the list, then click the minus (-) button or right-click and select Remove. (Don't worry: the backup data on the disk itself is not deleted.) - Click 'Add Backup Disk'
This opens a list of available disks and network shares. Re-select the same disk or NAS share you just removed. - For network backups, verify SMB configuration on your NAS
Log into your NAS admin panel (usually via web browser). Find the Time Machine or shared folder settings. Ensure:
- The share is explicitly configured for Time Machine (some NAS systems have a toggle for this)
- SMB protocol is enabled (preferred over AFP for modern macOS)
- The user account you're using has read-write permissions on that share
- The share path is correct (often /mnt/backup or similar) - Test the connection in Finder
Open Finder > Go > Connect to Server (or Cmd+K). Enter the NAS address (e.g., smb://192.168.1.100/timemachine). If Finder can mount it, Time Machine should too.
Check Your macOS Firewall and Adjust Energy Saver Settings Medium
- Open System Settings > Network or Privacy & Security > Firewall
The exact location varies by macOS version. On newer versions, look under Privacy & Security > Firewall. - Ensure the firewall is enabled
This is good security practice. However, for network backups, the firewall can sometimes block SMB traffic. If backups fail and your firewall is on, note this. - Add Time Machine to the firewall's allowed apps (if the option exists)
Some macOS versions allow you to whitelist specific applications. If you see an 'Allow' button next to Time Machine or backupd, click it. - Open System Settings > General > Startup Disk or System Preferences > Energy Saver
Look for sleep settings. Set 'Prevent computer from sleeping automatically when on power adapter' if available, or set sleep timers to longer intervals (e.g., 30 minutes instead of 10). - For display sleep, set it separately
It's fine for the display to sleep, but the Mac itself should stay awake during backups. Some settings are labeled 'Display sleep' vs 'Computer sleep'.
Time Machine Error 45 Advanced Fixes (Tier 3)
These fixes dig into filesystem corruption, sparsebundle problems, and OS-level bugs. They're appropriate if Tier 1 and Tier 2 haven't worked. You'll be using Terminal and potentially deleting and recreating your backup, so ensure you have critical files backed up elsewhere before proceeding.
Diagnose Issues Using Console Logs and Terminal Commands Hard
- Open Console (Applications > Utilities > Console)
This app shows system logs in real time. It helps you see exactly what Time Machine is doing when it fails. - In the search field, type 'backupd'
This filters logs to show only Time Machine backup daemon messages. - Trigger a backup failure
Click the Time Machine menu bar icon > Back Up Now. Watch the Console for error messages as the backup runs. - Look for specific error messages such as:
- "The backup disk image was ejected or disconnected" (network or USB issue)
- "I/O error" followed by a file path (file-level corruption)
- "Permission denied" (access/authentication issue) - Open Terminal (Applications > Utilities > Terminal)
Run these commands to gather more details:
tmutil status- shows current backup status
tmutil destinationinfo- lists all backup destinations and their UUIDs
log show --predicate 'process == "backupd"' --last 1h- displays last hour of backupd logs with full detail
Repair or Recreate Sparsebundle for Network Backups Hard
- Mount the NAS share in Finder
Use Go > Connect to Server (Cmd+K) and connect to your NAS. Locate the .sparsebundle or .backupbundle file (usually named YourMacName.sparsebundle). - Attempt to verify the sparsebundle with hdiutil
Open Terminal and navigate to the mounted share:
cd /Volumes/YourTimeMachineShare
Then run:
hdiutil verify ./YourMacName.sparsebundle
If this completes successfully, the bundle is intact. If it reports errors, proceed to the next step. - Try repairing the sparsebundle
Run:
hdiutil repair ./YourMacName.sparsebundle
This can take 30+ minutes for large backups. If repair succeeds, try a new backup. If repair fails multiple times, the bundle is corrupt beyond recovery. - Recreate the backup from scratch (last resort)
On the NAS, rename the corrupted sparsebundle:
mv YourMacName.sparsebundle YourMacName_old.sparsebundle
Then go to System Settings > Time Machine, remove the old destination, and re-add it. Time Machine will create a fresh sparsebundle and start backing up anew. Your old backup history is preserved in the _old file if you ever need it.
Test With a Different Backup Destination and Update macOS Medium
- Use a separate external USB drive as a test
Connect a different external drive to your Mac. Format it as APFS (for M1 and newer Macs) or Mac OS Extended (Journaled) in Disk Utility if it's blank. - Set it as a temporary Time Machine destination
Open System Settings > Time Machine > Add Backup Disk and select this test drive. - Run several manual backups
Click Back Up Now multiple times. If this new disk works perfectly while your original NAS or drive fails consistently, the issue is with that specific destination or its configuration, not your Mac. - Check for macOS updates
Go to System Settings > General > Software Update. Install any available supplemental updates for your current macOS version. Apple frequently patches Time Machine bugs in minor updates (e.g., 13.1.1, 14.2.3, etc.). - After updating, restart and retry backups
Updated macOS may resolve compatibility issues with your NAS or solve known sparsebundle corruption bugs.
At this point, if none of the Tier 3 steps resolved error 45, you may be dealing with a rare hardware failure, a NAS firmware bug, or an OS-level issue beyond simple troubleshooting. Some users have found that switching to dedicated backup software (which handles sparsebundle management differently and includes repair utilities) can bypass Time Machine's limitations entirely.
Remote Support for Time Machine Error 45
If error 45 persists after Tier 2 steps, remote support can diagnose your specific network configuration, examine your backup logs in real time, and safely execute Tier 3 repairs without risking data loss. We'll connect to your Mac, identify whether the fault is in your network, NAS, or macOS itself, and rebuild your backup if needed.
Get remote helpPreventing Time Machine Error 45
Once you've fixed error 45, the goal is to never see it again. Prevention is always easier than troubleshooting.
Dedicate your backup disk. Time Machine works best when the backup disk is used exclusively for backups. If you're storing large video projects, software installers, or other files alongside Time Machine, you're competing for space and introducing filesystem fragmentation. A dedicated disk or NAS share is the gold standard.
Use Ethernet for network backups. Wi-Fi is convenient but introduces latency and packet loss, especially over longer backup cycles. If you're using a NAS, run Ethernet from your Mac to the NAS if possible. Even 10 minutes of Ethernet during your nightly backup is better than relying on Wi-Fi the entire time.
Keep everything updated. Both macOS and NAS firmware contain fixes for Time Machine bugs and SMB protocol issues. Check for updates monthly. A small firmware update on your NAS can eliminate recurring error 45 issues.
Monitor free space regularly. Time Machine doesn't send alerts when your backup disk is running low on space; it just fails silently. Once a month, check your backup disk's free space in Finder. If it's below 20% free, delete old backups from your NAS (most NAS systems have Time Machine cleanup utilities) or use a larger disk.
Prevent sleep during backups. Configure Energy Saver or System Settings to keep your Mac awake during your scheduled backup window (often late night or early morning). If your Mac sleeps mid-backup, error 45 is almost guaranteed.
Run Disk Utility First Aid quarterly. Filesystem errors accumulate over time. A quarterly First Aid check on your backup disk catches corruption before it becomes critical.
Maintain a secondary backup. Even with all these precautions, hard drives and NAS units eventually fail. Keep at least one additional backup on a separate external disk or cloud service. Three copies of your data is the industry standard: one on your Mac, one on your Time Machine disk, and one off-site or on a different physical device.
Time Machine Error 45 Summary
Time Machine error 45 is frustrating, but it's almost always fixable without losing your backup. Start by checking your physical connection, verifying free space, and restarting Time Machine and your Mac. Most error 45 failures resolve at this stage within 15 minutes. If not, re-add your backup disk, check your network configuration (for NAS backups), and run Disk Utility First Aid. These Tier 2 fixes handle the vast majority of remaining cases. Only if those fail should you move to Tier 3 diagnostics, which may require recreating your backup from scratch. Throughout the process, keep your backup disk plugged in, your Mac awake, and your network stable. Once you've fixed error 45, maintain regular updates, check your free space monthly, and keep a secondary backup elsewhere. Do that, and error 45 shouldn't return.


