Skip navigation

Never-ending Time Machine backup to Time Capsule

8134 Views 20 Replies Latest reply: Mar 16, 2013 6:03 AM by AppleForumAlias RSS
1 2 Previous Next
zenaloha Level 1 Level 1 (0 points)
Currently Being Moderated
Sep 21, 2012 8:22 AM

This first occurred three days ago prior to updating to 10.8.2 and updating did not resolve the issue. I'm running OS X 10.8.2 on a late 2009 Macbook with a Time Capsule. All software / firmware is up to date. The Time Machine backup starts as usual, preparing the backup and calculating the total amount of data to be backed up, however, when the actual data backed up gets close to the total amount to backup, the total amount starts to increase ad infinitum. For example, yesterday after updating to 10.8.2, the total amount of data to backup was 4.2 gb. Once the amount backed up was 3.9 gb, the total amount and the amount backed up started to increase together (4.1 of 4.4; 6.5 of 6.8; 9.8 of 10.1, etc). This went on for over an hour and I eventually had to stop the backup since it looked like there was no end in sight. Any ideas? I've tried toggling Time Machine off and on, restarting both Macbook and Time Capsule to no avail. Thanks!

  • kezarmyaj Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 21, 2012 11:30 AM (in response to zenaloha)

    I also started experiencing this same issue a few days ago.  it is making me crazy.

  • pwwwayne Level 1 Level 1 (30 points)
    Currently Being Moderated
    Sep 21, 2012 12:14 PM (in response to kezarmyaj)

    I am gathering some info and help with this issue on a thread

    16 days to Backup!

    at https://discussions.apple.com/message/19673010#19673010

  • kezarmyaj Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 22, 2012 8:07 AM (in response to kezarmyaj)

    Im guessing this is just something to deal with thanks to the 10.8.2 update?  tried to downgrade, but of course my backups are 'in progress' because it never finishes. 

     

  • kezarmyaj Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 25, 2012 2:10 PM (in response to zenaloha)

    any luck with this yet?

  • kezarmyaj Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 25, 2012 7:23 PM (in response to zenaloha)

    well I finally just said f it and deleted everything and started over.  started a new backup and everything works fine now.  I did a wired connection with my time capsule rather than wireless and it only took an hour or so to do 120 gb.

  • Builder1 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 25, 2012 8:15 PM (in response to zenaloha)

    Since the last two updates for Mt. Lion my time machine has been an ongoing problem of unreliable back-ups. I back up my iMac and MacBook Pro to a 2TB Time Capsule. Since the updates, my computers randomly cannot find the back-up disk. When I shut off time machine and turn it back on, somethimes one or both Macs may or may not find the disk and when it does, they try to back up from the beginning. (thats 720GB of iMac back up!) it says back up will take 5 days, usually after 7-10 hours of back up the computer will freeze and the backup has to start over, it will not pick up from where it left off. I have tried erasing the back up disk and starting over but the problem still remains. I succsessfully backed up all 80GB from my MBP but since then it has not been able to find the disk to do any further back ups.

  • Builder1 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 25, 2012 8:20 PM (in response to pwwwayne)

    Your Mac will stay on for 16 days to back up without freezing? Any Mac I have ever had has never been able to stay on for more than a day or two withour freezing or restarting itself... This is my big problem when trying to re-back up all 720GB form my iMac. both of my Macs were backing up fine until recet updates. Now Im forced to start over but my iMac wont last the 5 days to back up without freezing or sutting it self down...

  • Mathias Körber Level 1 Level 1 (5 points)
    Currently Being Moderated
    Oct 11, 2012 7:47 AM (in response to zenaloha)

    I am getting the same now, after upgrading to ML. The first backup went well, so did the second, but now Isee exactly this issue.

     

    I can 'stop' the backup, but then the next backup gets the same issue.

  • Mathias Körber Level 1 Level 1 (5 points)

    I found that the backup keeps updating this file:

     

    bash-3.2# pwd

    /Volumes/TM 1/Backups.backupdb/vadeMACumPro2/2012-10-11-222844.inProgress/CC5A8E79-E692-4A8 C-ADFA-5A3EA7A58475

    bash-3.2# ls -l

    total 16

    -rw-------   1 root  _unknown   533 Oct 11 23:13 .com.apple.TMCheckpoint

    -rw-------   1 root  _unknown  2441 Oct 11 22:53 .exclusions.plist

    drwxr-xr-x@ 11 root  _unknown   544 Oct 11 23:03 Macintosh HD

     

     

    bash-3.2# cat .c*oint

    <?xml version="1.0" encoding="UTF-8"?>

    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

    <plist version="1.0">

    <dict>

        <key>SnapshotNumberOfBytesCopied</key>

        <integer>11156872947</integer>

        <key>SnapshotNumberOfBytesToCopy</key>

        <integer>11156872855</integer>

        <key>SnapshotNumberOfBytesToRepresent</key>

        <integer>0</integer>

        <key>SnapshotNumberOfItemsCopied</key>

        <integer>258169</integer>

        <key>SnapshotNumberOfItemsToCopy</key>

        <integer>258167</integer>

    </dict>

    </plist>

     

     

    What is interesting are the last two numbers. Two more file Copied than ToCopy.  I wonder whether there is a back check (equality instead of >) in the test that ends the backup?

     

     

    A few minutes later this file looks like this:

     

    bash-3.2# ls -lt

    total 16

    -rw-------   1 root  _unknown   533 Oct 11 23:18 .com.apple.TMCheckpoint

    drwxr-xr-x@ 16 root  _unknown   748 Oct 11 23:18 Macintosh HD

    -rw-------   1 root  _unknown  2441 Oct 11 22:53 .exclusions.plist

     

    bash-3.2# cat .*oint

    <?xml version="1.0" encoding="UTF-8"?>

    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

    <plist version="1.0">

    <dict>

        <key>SnapshotNumberOfBytesCopied</key>

        <integer>12390444693</integer>

        <key>SnapshotNumberOfBytesToCopy</key>

        <integer>12390420706</integer>

        <key>SnapshotNumberOfBytesToRepresent</key>

        <integer>0</integer>

        <key>SnapshotNumberOfItemsCopied</key>

        <integer>297334</integer>

        <key>SnapshotNumberOfItemsToCopy</key>

        <integer>297275</integer>

    </dict>

    </plist>

  • Mathias Körber Level 1 Level 1 (5 points)

    A colleague pointed out:

     

    # - if you read the console logs for backupd, you'll see that when that

    # - hapepens, it's doing a huge post-backup prune. Since HFS+'s hard link

    # - methodology is TERRIBLE this takes a hundred years and there's no way to

    # - ETA it. It's best to format your time machine drive if it has a backup

    # - from a previous Mac OS on it.

     

    and true, I had a (fresh) backup on this external disk from LION.

     

    I will try this and see if ithat cures it (if it later comes back).

     

    And no, I have not looked at the mentioned log yet, will do that later...

  • Mathias Körber Level 1 Level 1 (5 points)
    Currently Being Moderated
    Oct 16, 2012 2:15 AM (in response to zenaloha)

    sadly it isn't. I have it again, after starting a totally fresh backup on a new backup disk that never saw a previous OS backed up.

1 2 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.