Your Time Machine Drive Just Filled Up What Should You Do

It’s inevitable—your Time Machine backup drive is going to fill up. Time Machine is smart about backing up only files that have changed, but after months or years of usage, the drive will run out of space. What happens then?

Before we explain, some background. On its first backup, Time Machine copies everything on your startup drive to the backup drive. After that, Time Machine keeps hourly backups for the past 24 hours, daily backups for the past month, and weekly backups for all previous months. If you modify the same file multiple times per day, every day, you’ll have numerous versions of it in your backup set so that you can go back to any particular version.

So the first thing that Time Machine does when your backup drive fills up is start deleting those older versions, beginning with the oldest ones. It warns you when this starts happening and tells you what your oldest remaining backup is. In general, this approach works well, since you probably don’t need all the older versions of changed files as long as Time Machine always retains the most recent version in the backup.

Eventually, however, even this technique runs into the wall of hard drives having only so much capacity. When that happens, backups will start failing, and this notification will appear after every backup attempt.

Blog Photo

Click the Details button in that notification to open the Time Machine pane of System Preferences, and you’ll learn more.

Blog Photo

You have four options at this point, but two of them may not be all that helpful.​

Delete Old Backups

One possible solution—albeit likely a short term one—is to delete old backups. You might be tempted to look in the Backups.backupdb folder on your Time Machine drive and delete some of the dated folders inside. Don’t. You have no idea what you’ll be deleting, and you’ll likely corrupt the entire Time Machine backup, rendering it useless.

Instead, use a utility like GrandPerspective or OmniDiskSweeper to identify folders or files that are both large and unnecessary. Navigate to one of those items in the Finder, select it, and then choose Enter Time Machine from the Time Machine menu bar icon. Once in Time Machine, click the Action menu (the gear icon) in the toolbar and choose Delete All Backups of Item.

Blog Photo

Alas, this approach may not have much of an effect, since it’s difficult to know how many backups Time Machine has stored.​

Exclude Large Folders from the Backup

Another approach that Apple mentions is excluding items from the Time Machine backup. To do this, open System Preferences > Time Machine and click the Options button. Then drag the desired file or folder into the “Exclude these items from backups” list and click Save.

Blog Photo

The only problem with this advice is that it’s helpful only before your backup drive fills up. Time Machine won’t reclaim space used by newly excluded items that already exist in your backup.​

Start Over, Either on a New Drive or after Erasing Your Existing Backup Drive

One of the great features of Time Machine is that it stores previous versions of files, as we’ve discussed. But you probably know if you’re the sort of person who needs to go back to such previous versions, or if you just use Time Machine so you can restore all your data in the event of a drive failure. If the latter is true and you don’t much care about previous versions of files, a good solution is just to start over, either on a new drive or after erasing your current drive.

Obviously, erasing your current drive means that you won’t have any Time Machine backup at all until a new one completes, which is a risk. And, of course, if that drive filled up once, it will do so again, potentially fairly quickly unless you exclude some large folders. But, if you want to go down that path, open Disk Utility, select your Time Machine drive in the sidebar, and click Erase. Then go into the Time Machine preferences again, click Select Disk, and pick your newly erased drive. You may have to select it under Backup Disks and click Remove Disk first.

Blog Photo

Getting a new, larger backup drive and starting over with it is easier and more sensible, though more expensive. Once you’ve connected the new drive, just open the Time Machine preferences, click Select Disk, and select the new drive.​

Blog Photo

Or, rather, in an ideal world that would be true. You need to make sure that the new backup drive is formatted properly for Time Machine. Choose About This Mac from the Apple menu, and then click System Report to open the System Information app. In its sidebar, click Storage, select the drive at the top, and make sure File System is Journaled HFS+ and Partition Map Type is GPT (GUID Partition Table).

Blog Photo

If the drive isn’t formatted correctly for Time Machine, open Disk Utility, select the drive in the sidebar, click Erase, and choose Mac OS Extended (Journaled) from the Format pop-up menu and GUID Partition Map from the Scheme pop-up menu. Then click Erase to ready it for Time Machine use. (This will, of course, delete all the data on the drive, so make sure that’s OK first!)

Blog Photo

Finally, make sure the permissions on the new drive are set correctly. Select the drive icon in the Finder, choose File > Get Info, click the triangle next to Sharing & Permissions, and make sure the “Ignore ownership on this volume” checkbox is unselected. You may need to click the lock icon and enter an administrator username and password.

Blog Photo

Copy Your Existing Backup to a New, Larger Drive

What if you want to retain all those old backups? That’s entirely possible, though it will take a long time to copy. Follow these steps:

  1. Connect both the old and the new backup drive to your Mac via Thunderbolt, USB, or Firewire.
  2. Make sure the drive is formatted properly for Time Machine, and if it’s not, reformat it in Disk Utility as noted above. Also, verify that the permissions are set correctly, as above.
  3. Turn off Time Machine so it doesn’t try to back up while you’re copying its data. In the Time Machine preference pane, deselect Back Up Automatically, or click the Off/On switch, depending on what version of macOS you’re running.
  4. Drag the Backups.backupdb folder from the old drive to the new one to copy it. You may be prompted for your administrator name and password.
  5. When it finishes, a day or two later, follow the instructions above to select the new drive in the Time Machine preferences and make sure to turn Time Machine back on.

One final note. It may be tempting to use an alternative method of copying the Backups.backupdb folder, but resist the urge. Time Machine uses special drive structures to work its magic, and only the Finder is guaranteed to copy them correctly.

AI Usage Transparency Report

Pre-AI Era · Written before widespread use of generative AI tools

AI Signal Composition

Rep Tone Struct List Instr
Repetition: 52%
Tone: 45%
Structure: 59%
List: 4%
Instructional: 98%
Emoji: 0%

Score: 0.09 · Low AI Influence

Summary

Time Machine backup drive filling up due to large files and versions of changed files. Solutions include deleting old backups, excluding large folders from the backup, starting over with a new drive or erasing the existing one, and copying the existing backup to a new larger drive.

Related Posts

Setting up Ollama on macOS

Recently, after some bad experiences with OpenAI's ChatGPT and CODEX, I decided to look into and learn more about running local AI models. On its face it was intimidating, but I had seen a lot of people in the MacAdmins community posting examples of macOS setups, which really helped lower the bar for me both in terms of approachability and just making me more aware of the local AI community that exists out there today.

Read more

AI Agent Constraints and Security

I really feel like in this era of AI it's essential to write about and share experiences for others who are leveraging AI, especially now that AI usage seems almost ubiquitous. Specifically, when it comes to AI in development and the rapid growth of AI-driven automations in the IT landscape, I believe there's a need for open discussion and exploration.

Read more

ABM Warranty 0.4.1

The 0.4.x release series for ABM Warranty is focused on operational scale. The earlier 0.3 releases were about trust, correctness, and stabilizing the foundation. Version 0.4.1 builds directly on that work by making the app more practical for consultants, internal IT teams, and managed service providers who need to support multiple environments without losing isolation, control, or visibility. This includes improvements to user interface and workflow, as well as enhanced reporting capabilities to help these users manage their workflows more efficiently.

Read more

Vibe Coding with Codex: From Fun to Frustration

So there I was, a typically day, a typical weekend. As a ChatGPT customer, I had heard good things about Codex and had not yet tried the platform. To date my experience with agentic coding was simply snippit based support with ChatGPT and Gemeni where I would ask questions, get explanations and support with squashing bugs in a few apps that I work on, for fun, on the side. There were a few core features in one of the apps I built that I wanted to try implementing but the...

Read more

Why Apple Fleet Risk Isn’t a Security Problem—Until It Is

Security and risk are often treated as interchangeable concepts in modern IT environments, but they are not the same discipline. Security focuses on controls, enforcement, and prevention. Risk management, by contrast, is concerned with likelihood, impact, and consequence across operational, financial, and organizational domains. Frameworks such as those published by NIST make this distinction explicit: risk assessment is not a technical exercise, but a business one. Technology informs risk decisions, but it does not define them.

Read more

ABM Warranty 0.3.1

The 0.3.x release series for ABM Warranty is about tightening guarantees. Where earlier releases focused on surfacing data and making long-running operations observable, 0.3.x focuses on ensuring that what you see is complete, consistent, and safe to trust—particularly as the app is used in larger, slower, and more varied environments. This shift in focus aims to provide a more reliable foundation for users who require higher levels of assurance from their warranty management system.

Read more

ABM Warranty 0.2.0

ABM Warranty 0.2.0 is a feature release focused on visibility, safety, and scale. This version does not change what ABM Warranty is meant to be, but it significantly improves how the app behaves under real-world conditions—large device counts, API throttling, long-running imports, and the kinds of failure modes Apple IT admins actually encounter. The improvements in this release are designed to make the app more reliable and efficient, allowing it to handle complex scenarios without breaking or becoming unresponsive.

Read more

Running a Beta Program: Lessons Learned

Shipping software in isolation is comforting. You control the inputs, the environment, and the narrative you tell yourself about how things work. The moment you invite other people in—especially people who don’t share your assumptions—you lose that comfort. You also gain something far more valuable. Running a public beta for ABM Warranty through Apple’s TestFlight program forced me to confront that tradeoff head-on, and it fundamentally changed how quickly and confidently the app matured.

Read more

The Day I Unmanaged a Mac Into a Corner

There are a few kinds of mistakes you make as a Mac admin. There are the ones that cost you time, the ones that cost you sleep, and then there are the ones that leave you staring at a perfectly good laptop thinking, “How did I possibly make this *less* manageable by touching it?” These mistakes often stem from a lack of understanding or experience with macOS, but they can also be the result of rushing through tasks or not taking the time to properly plan and test.

Read more