• Skip to main content
  • Skip to primary sidebar
  • Home
  • About
    • Stephen Foskett
      • My Publications
        • Urban Forms in Suburbia: The Rise of the Edge City
      • Storage Magazine Columns
      • Whitepapers
      • Multimedia
      • Speaking Engagements
    • Services
    • Disclosures
  • Categories
    • Apple
    • Ask a Pack Rat
    • Computer History
    • Deals
    • Enterprise storage
    • Events
    • Personal
    • Photography
    • Terabyte home
    • Virtual Storage
  • Guides
    • The iPhone Exchange ActiveSync Guide
      • The iPhone Exchange ActiveSync Troubleshooting Guide
    • The iPad Exchange ActiveSync Guide
      • iPad Exchange ActiveSync Troubleshooting Guide
    • Toolbox
      • Power Over Ethernet Calculator
      • EMC Symmetrix WWN Calculator
      • EMC Symmetrix TimeFinder DOS Batch File
    • Linux Logical Volume Manager Walkthrough
  • Calendar

Stephen Foskett, Pack Rat

Understanding the accumulation of data

You are here: Home / Everything / Apple / “Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you.”

“Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you.”

August 11, 2010 By Stephen 6 Comments

Time Machine is one of my favorite Mac OS X features. Sure, it’s not loaded with features and customizability, but it works for the most part. Plus, it’s so easy to set up that it encourages the average computer user to actually have a backup. Anything that encourages backups is great news in my book!

Have you seen this dialog box? Is it an error or a help?

But Apple recently rolled out a “Time Capsule Backup Update”, and included it in Mac OS X 10.6.4, that is causing confusion and concern. In the name of improving “the reliability of your Time Capsule backup,” this update has the unfortunate side-effect of detecting errors in existing backup bundles and forcing users to start a new backup. It happened with two of my Macs so far, so I was keen to find out what’s going on.

Verifiably Bad

Time Machine may look simple, but it’s an incredibly complex piece of software. It uses multiple kernel-level features and builds a complete files-level copy of your data in a “bundle” that acts like a virtual drive. Rather than storing files multiple times (which would be space-inefficient) or hard-linking them (which is efficient for space but would take a long time), OS X adds directory-level hard links, a fairly new concept. So if no changes have been made in your /Applications directory, it just creates a single link to a previous copy. OS X also includes a new daemon to monitor changes on a directory basis, which is also fairly cool in a geeky sort of way.

This intricate but powerful system can lead to trouble, however. If a backup process is interrupted while it is working, the relationships between directories, files, and dates can become corrupted. This is especially common for network-mounted drives, explaining Apple’s reluctance to allow non-Apple NAS units to be backup targets. But even local direct-attached drives can sometimes become corrupted over months of operation.

As (poorly) explained in Apple’s Knowledge Base article HT4076, corruption can cause previous Time Machine backups to be unavailable. So Apple introduced a more-robust mechanism to check backup integrity and rolled it out in Software Update and as part of OS X 10.6.4. It scans old backups and, if errors are found, flags them read-only and starts a new backup bundle. See this Apple Support Discussion thread and this web site for more information.

What You Should Do

Let’s cut through the confusion caused by Apple’s typical lack of explanation.

Should you install this update? Yes! Corrupt backup images are bad, regardless of the cause, and you need to know whether yours is good or not. Installing the update might cause you to start a new backup bundle, but at least you’ll know your data is safe!

Should you click “Start New Backup”? Not yet! If you see the dialog above, your existing Time Machine backup is corrupt, and you might not be able to recover data from it. But you can save a copy of the corrupt bundle and, perhaps, extract some data from it if needed.

Ask yourself if Time Machine has saved data you might need before deciding what to do next:

  1. If you are sure you won’t need anything backed up before today, click “Start New Backup” and let Time Machine do its thing.
  2. Otherwise, click “Back Up Later” and save a copy before letting Time Machine start a new backup. Just look for a file called “computername.sparsebundle” (for network backups) or “Backups.backupdb” (for local ones) and create a copy with a different name. You can open sparsebundle files with DiskImageMounter and browse them like any other disk. More information is available here.

There you go. If you click “Start New Backup” when you see this dialog box, Time Machine will erase all of your old backup data and start a new bundle. It won’t be corrupt, but it will be empty.

Note that you can manually initiate a Time Machine backup integrity check by option-clicking the “Time Machine” icon in the menu bar and selecting “Verify Backups.”

Stephen’s Stance

Backups are good.

Corrupt backups are bad.

Time Machine encourages backups, and works pretty efficiently, so it’s good.

This update ensures that Time Machine’s backups aren’t corrupt, so it’s good.

‘Nuff said.

You might also want to read these other posts...

  • GPS Time Rollover Failures Keep Happening (But…
  • Electric Car Over the Internet: My Experience Buying…
  • Tortoise or Hare? Nvidia Jetson TK1
  • Ranting and Raving About the 2018 iPad Pro
  • Introducing Rabbit: I Bought a Cloud!

Filed Under: Apple Tagged With: Apple, backups, data corruption, OS X, Time Capsule, Time Machine

Primary Sidebar

This is our mission: To be the Daleks of God

Shriekback

Subscribe via Email

Subscribe via email and you will receive my latest blog posts in your inbox. No ads or spam, just the same great content you find on my site!
 New posts (daily)
 Where's Stephen? (weekly)

Download My Book


Download my free e-book:
Essential Enterprise Storage Concepts!

Recent Posts

Electric Car Over the Internet: My Experience Buying From Vroom

November 28, 2020

Powering Rabbits: The Mean Well LRS-350-12 Power Supply

October 18, 2020

Tortoise or Hare? Nvidia Jetson TK1

September 22, 2020

Running Rabbits: More About My Cloud NUCs

September 21, 2020

Introducing Rabbit: I Bought a Cloud!

September 10, 2020

Remove ROM To Use LSI SAS Cards in HPE Servers

August 23, 2020

Test Your Wi-Fi with iPerf for iOS

July 9, 2020

Liberate Wi-Fi Smart Bulbs and Switches with Tasmota!

May 29, 2020

What You See and What You Get When You Follow Me

May 28, 2019

GPS Time Rollover Failures Keep Happening (But They’re Almost Done)

April 6, 2019

Symbolic Links

    Featured Posts

    What’s the Difference Between a Jailbroken and an Unlocked Phone?

    May 5, 2012

    Rocking Out With the Topping VX1 Desktop/Bookshelf Amplifier

    October 6, 2015

    What’s the Deal with Containers?

    October 21, 2016

    What is VMware VASA? Not Much (Yet)

    November 11, 2011

    Ranting and Raving About the 2018 iPad Pro

    November 11, 2018

    Sony QX100 Lens Camera: Ruined by a Flaky iOS App

    October 7, 2013

    Storage Changes in VMware vSphere 5

    July 16, 2011

    The Myths of Standardization

    December 15, 2011

    Download My Free E-Book, “Essential Enterprise Storage Concepts”!

    April 4, 2017

    A Fairy Tale of Two Storage Protocols

    September 23, 2014

    Copyright © 2021 · Log in