Time Machine is stuck at calculating changes

It will try all day to back up but never gets past calculating changes. I am not sure where to even start. Can you help me?

kcboy713 wrote:
Could it be a problem if it says I have 25g of 1000g available and my full back up is 106g?
Is this Drive used exclusively for TM or do you have other stuff on it... ?
Also some more Details about the Drive and your Mac would be helpful...

Similar Messages

Time Machine Backup Hangs at "Calculating Changes"

Since upgrading to SL, I am unable to backup. I am using a WD MyBook HD linked to a TC for backing up my MacBook Pro 13" UB. Prior to upgrading all was operating normally.
The process hangs at "Calculating changes 99%" . It will not progress beyond that point. I have to manually stop the backup.
Here is the log:
Sep 1 09:13:25 twnMacBook com.apple.backupd[768]: Starting standard backup
Sep 1 09:13:25 twnMacBook com.apple.backupd[768]: Attempting to mount network destination using URL: afp://Tod%[email protected]/My%20Book
Sep 1 09:13:41 twnMacBook com.apple.backupd[768]: Mounted network destination using URL: afp://Tod%[email protected]/My%20Book
Sep 1 09:13:46 twnMacBook com.apple.backupd[768]: Disk image /Volumes/My Book/twnMacBook_00254bca016c.sparsebundle mounted at: /Volumes/Backup of twnMacBook
Sep 1 09:13:46 twnMacBook com.apple.backupd[768]: Backing up to: /Volumes/Backup of twnMacBook/Backups.backupdb
Sep 1 09:13:53 twnMacBook com.apple.backupd[768]: Event store UUIDs don't match for volume: Macintosh HD
Sep 1 09:13:53 twnMacBook com.apple.backupd[768]: Waiting for index to be ready (101)
Sep 1 09:14:00 twnMacBook com.apple.backupd[768]: Node requires deep traversal:/ reason:must scan subdirs|new event db|
Any suggestions?

Elkins45 wrote:
I'm having exactly the same problem (hanging at 99%). I have a FW drive connected directly and I did an erase an install because I was having problems with my Leopard install.
I've restarted a hundred times, erased and reinstalled three times and restarted the drive, all to no avail.
Try a "full reset" of Time Machine:
a. Go to TM Preferences, turn TM Off, de-select the drive (select "none"), and click the Options button. Note any exclusions in the +Do Not Back Up+ box, and other option(s) on that panel. Then quit System Preferences.
b. Eject, disconnect, and power-off the drive for a few moments, then reconnect it.
c. Delete the file /Library/Preferences/com.apple.TimeMachine.plist (in your top-level Library folder, not your home folder).
d. Go back to TM Preferences, re-select your drive, re-enter any exclusions and other options.
e. Do a +*Back Up Now*+ or wait for the next scheduled backup.
If that doesn't help, try the Console app, as in my previous post, but do not filter for Backupd. See if there's anything else suspicious there. If so, copy and post a reasonable amount here.

Time Capsule / Time Machine stuck on 'calculating changes'

Time Machine has not backed up to my Time Capsule for the last several weeks on my MacBook Pro. It is constantly stuck on 'calculating changes' for hours. I have tried other suggestions I have found in the forum like verify and repair disc on both my internal HDD and on the time capsule drive. No errors were found on either drive. I normally backup via wifi and I have also tried plugging directly into the time capsule with an ethernet cord. It doesn't make any difference either with wifi or ethernet.
The time capsule drive is full, but I just assumed that Time Machine would erase the oldest backups and continue. I don't know if this is an issue with the problem I am having. I downloaded the time machine widget as suggested in other posts on this topic, the log is posted below. There are errors about the disc being full and an error writing to the backup log. I don't know why it can't right to the log or what could be wrong. After looking at the logs, it appears that what is shown below just continues to repeat about every two hours (time machine seems to give up after about 2 hours and starts over again with the same result).
I am thinking of erasing the time capsule disc and trying to start over, but would like to figure why this has happened before I erase the disc. I am also worried about erasing my only backups, even if they are three weeks old. Entering time machines still seems to give me all of my older backups like nothing is wrong, but I haven't restored from one so they may not work if I tried.
Any help would or insight into this would be greatly appreciated.
Starting standard backup
Attempting to mount network destination using URL: afp://Kason%[email protected]/Data
Mounted network destination using URL: afp://Kason%[email protected]/Data
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/Data/MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
Exception writing exclusions cache. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
Unable to create exclusions cache data.
Failed to write exclusions cache. Continuing anyway.
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandl

jaxx323 wrote:
The time capsule drive is full, but I just assumed that Time Machine would erase the oldest backups and continue.
Ordinarily it will. Do you have other data on the drive? If so, it appears that other data has completely filled the drive, so much so that Time Machine can't even start the hidden log it keeps there.
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
Usually when that happens, the backup crashes.
First, cancel the backup. If it won't cancel after a few moments, see #D6 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html].
Then connect via an Ethernet cable if at all possible. Time Machine needs to do some intensive work, and it will be slow even via Ethernet, but 2-3 times slower via WIFI.
If there's other stuff on the drive, you could copy some of it elsewhere temporary and delete it. You only need to free up 50 MB or so.
But your best bet is to delete your oldest backup(s), then "compact" the sparse bundle they're in, to make some space. See #12 of [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html].
Since it's been several weeks, you may want to delete roughly one old backup for each of those weeks, then "compact" the sparse bundle. If you only delete one, then Time Machine will have to delete more, but it will delete one, dismount the sparse bundle, compact it, then remount it to see if there's enough room. That gets repeated over and over until there's enough space.
Once this is sorted out, if there is other stuff on your TC's internal HD, see #Q3 in [Using Time Machine with a Time Capsule|http://web.me.com/pondini/TimeMachine/TimeCapsule.html] (or use the link in *User Tips* at the top of this forum).

Time machine is getting stuck whilst 'calculating changes'

Updated my external HDD to use for TIme Machine. 3 weeks later and TM is trying to back up but getting stuck on 'calculating changes. I can't access or eject the drive whist that's happening so have to just pull the USB and restart.
After that it's fine, but I'm worried that not ejecting properly might damage the drive or the content. Any ideas?

Check this post for advice:
Time Machine - Troubleshooting

Time Machine stuck in "Calculating Changes"

I am backing up time machine to a 1 tb Seagate GoFlex Desk. It is formatted to MacOS extended journaled. It works about 80% of the time, but a couple of times a day I check and it is stuck in "calculating changes". The only solution i have found is unplugging it which gives me the message "You need to eject". I just reinstalled the os hoping that would take care of it, but no dice. I did try logging out to see if that reset it, and it got stuck at my blank desktop background. But when I unplugged the harddrive, it finished logging out. Anyone have any solutions to these very annoying problems?

Hi jtupnsmoke - I have the exact same problems and am also using the Seagate 1TB Flex Drive- have had unplug the drive and have had the improperly ejecting the drive message, etc. I'm stuck in calculating changes once again. It is the only problem I've had that I wasn't able to fix with help from all of the great people on these boards. I'm about ready to plug in my old OWC Neptune external drive and see if it makes a difference.

Stuck on "calculating changes"

Hi there,
I have time machine set up on an external USB drive and I'm stuck on "calculating changes" when I try to make a backup. It was normal until a couple of days ago, when the drive suddenly disconnected from the Imac in the middle of a backup (I think it was due to an oscilation on the power supply or something like that, not physically disconnected). Ever since then, I'm not able to make new back ups.
I already ran a disk test (on disk utility) and it is normal. I also tried to remove and add the disk on the time machine preferences, but still nothing.
I got a log from Time Machine Buddy:
*Starting standard backup*
*Backing up to: /Volumes/Backup e Dados/Backups.backupdb*
*Event store UUIDs don't match for volume: Macintosh HD*
*Waiting for index to be ready (100)*
*Waiting for index to be ready (100)*
*Waiting for index to be ready (100)*
*Waiting for index to be ready (101)*
*Waiting for index to be ready (100)*
*Waiting for index to be ready (101)*
Any ideas on how to fix this?
Thanks,

Edu C wrote:
Hi there,
Hi, and welcome to the forums.
I already ran a disk test (on disk utility) and it is normal
Do you mean you ran +*Repair Disk+* (not permissions) on the TM drive? If not, try that.
*Event store UUIDs don't match for volume: Macintosh HD*
That's normal after a disconnection; it just means Time Machine isn't sure it got everything the last time.
*Waiting for index to be ready (100)*
*Waiting for index to be ready (100)*
*Waiting for index to be ready (100)*
*Waiting for index to be ready (101)*
*Waiting for index to be ready (100)*
*Waiting for index to be ready (101)*
These mean Time Machine is indexing your backups (because of the abnormal disconnection). It should complete that and proceed with the backup, which will probably take a lot longer than usual.
If Disk Utility didn't find a problem with the file system, the drive itself may be damaged. How old is it?
If you haven't yet, try cancelling the backup, ejecting, disconnecting and powering it off for several minutes. Then Restart your Mac and try again. Make sure all connections are snug and secure; try different ports, cables, and combinations of the two (a plug that works fine in one port may not make good contact in another).

Stuck on calculating changes - Waiting for index to be ready

I've got a Time Machine which had my disk properly backed up (~500 Gigs). Then, I used Entourage Time Machine to save my email database to a set of local XML files (tens of thousands of new files). Since then, it's stuck on Calculating Changes; I tried stopping it, removing the .plist file, stopping/restarting the service, etc. I restarted it again and now it's once again on Calculating Changes for 12 hours now. Time Machine Buddy says "Waiting for index to be ready". Could it possibly really be doing what it needs to do or is it stuck somehow and is there anything else I can do??
thanks in advance,
Mike

Michael Levin wrote:
Then verify your internal HD and repair your backups, per #A5 in Troubleshooting.
did that - repaired the disk, no problems found.
Uh, you need to check your internal, too, if you didn't. It's probably ok, but it's best to be sure. Then Restart your Mac.
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
A few of those may not be a problem, especially after a failed backup. The backups have to be indexed for TM to work right.
why isn't the index ready - could it have anything to do with Spotlight (which is also going like mad, but at least now gives a time estimate) - is that the index it's talking about??
Perhaps. Both Spotlight and Time Machine use the mds process to index.
|
Ok, so I disabled Spotlight, deleted all the .Spotlight files on all volumes, and restarted Time Machine having excluded the Entourage database and 56 Gigs worth of .xml files of individual messages.
56 GB? Holy moley!
Event store UUIDs don't match for volume: Main Internal Drive (Leopard)
Forcing deep traversal on source: "Main Internal Drive (Leopard)" (mount: '/' fsUUID: 22E61BEA-43E3-3C1C-985D-4589FACE5629 eventDBUUID: D2A7E78E-C39A-46A3-B273-CCEE5048369C), {1, 1, 1, 0}
Node requires deep traversal:/ reason:must scan subdirs|require scan|
Normal after a failed backup; Time Machine's not sure what was where when the "lights went out," so has to compare everything on your system to the backups to figure out what needs to be backed-up.
No pre-backup thinning needed: 24.38 GB requested (including padding), 983.14 GB available
The deep traversal completed. It found about 20 GB to back up (plus 20% for workspace -- the "padding" in the message).
Error: Flushing index to disk returned an error: 0
That's another problem writing the index to the TM drive.
Try a +*Repair Disk+* on it again, and make sure all connections are snug and secure, and try the backup again.
If this continues, it's beginning to look like a problem with the disk or connections. Try different ports, cables, and combinations of the two -- cables do deteriorate, and a plug that works fine in one port may not make good contact in another one.

I have been using time machine to back up my Mac Book Pro 3.1 to my Time Capsule. Now the Time machine hangs up on "calculating time remaining".

I have been using time machine to back up my Mac Book Pro 3.1 to my Time Capsule. Now the Time machine hangs up on "calculating time remaining".
Mac Book Pro - 3.1-15-inch 2.4/2.2GHz), Processor 2.2 GHz Intel Core 2 Duo
Operating system : OS X 10.10.1
Time Machine Version 1.3, Copyright 2007-2014 Apple Inc., Modified Tuesday, September 9, 2014 at 6:03 PM
Time Capsule: 500 GB C 2007
This Time Machine software worked satisfactory until Monday Nov, 10 2014 and I have backups until that time. For several years, the software deleted the oldest back up to save the latest one. This is acceptable to me as I have off site storage that is updated every 3 months. How do I get Time machine working again?

I have spent a couple of days trying to respond to Linc Davis. Finally I figured it out . The following is a copy of data from my console from the initiation of a time machine backup until it gets stuck trying to calculate the time remaining. There is no indication that anything starts saving. I copied about 3 minutes of data. This is probably way too much data, but I do not know what is relevant.
Thanks for the help,
calcool
12/22/14 3:16:54.655 PM com.apple.backupd[551]: Starting manual backup
12/22/14 3:16:55.057 PM com.apple.backupd[551]: Attempting to mount network destination URL: afp://”name”%20”lastname”@Home%20Network%20Time%20Capsule._afpovertcp._tcp.loca l./Time%20Capsule
12/22/14 3:16:57.262 PM mds[33]: (Volume.Normal:2464) volume:0x7fed5ab54000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Time Capsule
12/22/14 3:16:57.565 PM com.apple.backupd[551]: Mounted network destination at mount point: /Volumes/Time Capsule using URL: afp://”name”%20”lastname”@Home%20Network%20Time%20Capsule._afpovertcp._tcp.loca l./Time%20Capsule
12/22/14 3:17:08.000 PM kernel[0]: hfs: mounted Backup of “name” “lastname”’s MacBook Pro on device disk3s2
12/22/14 3:17:09.625 PM com.apple.backupd[551]: Disk image /Volumes/Time Capsule/”name” “lastname”’s MacBook Pro (2).sparsebundle mounted at: /Volumes/Backup of “name” “lastname”’s MacBook Pro
12/22/14 3:17:11.112 PM com.apple.backupd[551]: Backing up to /dev/disk3s2: /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb
12/22/14 3:17:24.931 PM “name”[593]: audit warning: soft /var/audit
12/22/14 3:17:24.944 PM “name”[594]: audit warning: allsoft
12/22/14 3:17:24.958 PM “name”[596]: audit warning: closefile /var/audit/20141222201654.20141222201724
12/22/14 3:17:26.544 PM com.apple.backupd[551]: Event store UUIDs don't match for volume: Macintosh HD
12/22/14 3:17:34.767 PM com.apple.backupd[551]: Deep event scan at path:/ reason:must scan subdirs|new event db|
12/22/14 3:17:34.768 PM com.apple.backupd[551]: Reading cached event database from: /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb/”name” “lastname”’s MacBook Pro (2)/2014-12-22-151726.inProgress/F85FEA51-E137-471A-84DA-A2C00E4ECB42/.1BEF88C6 -20C3-3DDC-AE30-05EAB2AFCC15.eventdb
12/22/14 3:17:38.115 PM com.apple.backupd[551]: Using cached disk scan
12/22/14 3:17:39.114 PM com.apple.backupd[551]: Saved event cache at /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb/”name” “lastname”’s MacBook Pro (2)/2014-12-22-151726.inProgress/5BC46A53-25E8-4C4A-8947-AFB221D1FA0C/.1BEF88C6 -20C3-3DDC-AE30-05EAB2AFCC15.eventdb
12/22/14 3:17:39.355 PM com.apple.backupd[551]: Not using file event preflight for Macintosh HD
12/22/14 3:19:14.782 PM CoreServicesUIAgent[294]: unexpected message <OS_xpc_error: <error: 0x7fff77befc60> { count = 1, contents =
"XPCErrorDescription" => <string: 0x7fff77beff70> { length = 18, contents = "Connection invalid" }
}>
12/22/14 3:20:15.207 PM locationd[182]: Location icon should now be in state 'Active'
12/22/14 3:20:17.267 PM locationd[182]: Location icon should now be in state 'Inactive'
12/22/14 3:20:17.884 PM locationd[182]: Location icon should now be in state 'Active'
12/22/14 3:20:18.483 PM sandboxd[296]: ([310]) com.apple.metada(310) deny mach-lookup com.apple.cfnetwork.cfnetworkagent
12/22/14 3:20:21.646 PM com.apple.metadata.SpotlightNetHelper[310]: [SLSUGGESTIONS] Location managed failed with error Error Domain=kCLErrorDomain Code=0 "The operation couldn’t be completed. (kCLErrorDomain error 0.)"
12/22/14 3:20:23.892 PM WindowServer[143]: disable_update_timeout: UI updates were forcibly disabled by application "Spotlight" for over 1.00 seconds. Server has re-enabled them.
12/22/14 3:20:26.526 PM WindowServer[143]: common_reenable_update: UI updates were finally reenabled by application "Spotlight" after 3.63 seconds (server forcibly re-enabled them after 1.00 seconds)
12/22/14 3:20:28.298 PM sandboxd[296]: ([310]) com.apple.metada(310) deny mach-lookup com.apple.cfnetwork.cfnetworkagent
12/22/14 3:20:29.094 PM com.apple.xpc.launchd[1]: (com.apple.quicklook[599]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
12/22/14 3:20:30.670 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:30.670 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:32.294 PM com.apple.InputMethodKit.UserDictionary[600]: -[PFUbiquitySwitchboardEntryMetadata setUseLocalStorage:](808): CoreData: Ubiquity: “name”~00000000-0000-1000-8000-001B63947FCF:UserDictionary
Using local storage: 1
12/22/14 3:20:32.317 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:32.769 PM locationd[182]: Location icon should now be in state 'Inactive'
12/22/14 3:20:34.580 PM Console[601]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
12/22/14 3:20:35.540 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
12/22/14 3:20:36.388 PM com.apple.xpc.launchd[1]: (com.apple.auditd[604]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.auditd
12/22/14 3:20:36.693 PM “name”[608]: audit warning: soft /var/audit
12/22/14 3:20:36.718 PM “name”[607]: audit warning: allsoft
12/22/14 3:20:37.045 PM “name”[610]: audit warning: closefile /var/audit/20141222201724.20141222202036
12/22/14 3:20:37.438 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:42.437 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
12/22/14 3:20:42.437 PM QuickLookSatellite[611]: Invalid Connection ID 0
12/22/14 3:20:42.477 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
12/22/14 3:20:42.477 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
12/22/14 3:20:42.612 PM QuickLookSatellite[611]: [QL] No sandbox token for request <QLThumbnailRequest stackshot.log>, it will probably fail
12/22/14 3:20:42.613 PM QuickLookSatellite[611]: [QL] No sandbox token for thumbnail request file:///Library/Logs/stackshot.log, it will probably fail
12/22/14 3:20:42.615 PM QuickLookSatellite[611]: [QL] No sandbox token for request <QLThumbnailRequest stackshot-syms.log>, it will probably fail
12/22/14 3:20:42.615 PM QuickLookSatellite[611]: [QL] No sandbox token for thumbnail request file:///Library/Logs/stackshot-syms.log, it will probably fail

What to do when time machine seems stuck on "Preparing Backup"

This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos. This means that the only backup will be for the system, profiles, and the app. I have been running this for a few months andhas been doing OK until up to now.
My problem is that my time machine seems to get stuck on "Preparing Backup". The latest backup was done last Nov 8, 2011, whcih is about 11 days from now. I am also aware that the time machine drive has only about 200 mb space left, but I am not worried at all because I've always TM to delete the oldest backup to free up space. My oldest backup was still Sept 8, and I'm ok if that will be deleted.
So I'd like to find out why it still stuck on "Preparing backup" ,and I am wondering if deleting a backup can solve it. Can it? what do I do to solve this?
Also, I use my computer alot , so it is basically running for about 18 hours a day, but still time machine didn't quite work well. I have tried reparing the disk using disk utility, but that didn't help.

Comments inline below.
Pondini wrote:
joshua raphael wrote:
This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos.
You may want to revisit that strategy:
A backup on the same drive isn't very secure -- when (not if) the HD fails, you risk losing everything.
In most cases, if there's a problem with OSX the best way to fix it is to just install a fresh version. But you can't do that from that backup.
Indeed!
Backing-up apps that way will also be useless in some cases. 3rd-party apps that came with their own installers put other files in other places (and sometimes "helper" apps as well). Unless you know what and where they all are, and restore them, too, the restored app won't work properly, if at all.
I think you're confusing each other with terminology. iTunes music and iPhoto pictures are NOT "Libraries", which has a specific meaning when it comes to OS X. "Libraries", in OS X normally refers to /Libraries and ~/Libraries folders. This is not where iTunes music and iPhoto pictures are stored. iTunes music and iPhoto pictures are stored within ~/Music and ~/Pictures, respectively.
I have tried reparing the disk using disk utility, but that didn't help.
Disk Utility changed a bit in Lion. When you select an entire disk, it only repairs the partition map, not all the volumes. You must repair each one separately.
Wow, good to know. (What a stupid change to make, for backwards compatibility, if for no other reason!)
See #D1 in Time Machine - Troubleshooting to figure out why the backups are hanging.
Whew. This editor makes it so hard to make comments inline. The key thing when time machine seems stuck is patience. Sometimes it needs to be left to run overnight. Unfortunately, it doesn't log or report it's progress very well.
Opening Time Machine settings in Preferences plus a command like this left running in Terminal.app is how I monitor progress. And even so, there is very little logging indicating progress.
sudo tail -f /Volumes/Time Machine/Backups.backupdb/My\ Computer/2012-07-11-133352.inProgress/.Backup.363731632.496216.log
The parts in italics will need to be adjusted. Tab completion makes this easy, e.g type
sudo tail -f /Volumes/
and hit tab, type the first few letters of the relevant volume name, hit tab...
Also, I have a hypothesis which needs testing.
I know that Time Machine gets confused if one deletes large files from a backup - specifically, Time Machine doesn't recognize that the size of the backup has changed.
I know because this made restoring a thinned out time machine backup ("thinned out" by deleting files from within the GUI while inside the Time Machine) to a small SSD harder than it should have been. I had to restore to a big disk and then clone that volume to the SSD - even though the SSD had enough space, Time Machine didn't think so; it didn't "understand" that it had been thinned.
My hypothesis is that Time Machine also gets confused if the Time Machine partition is resized. I shrunk a Time Machine partition (no it wasn't on my main disk!) and about that time, Time Machine stopped working. After thinning the volume, it started working again.

Time Machine is stuck (blocked) since I migrated to OS X Lion / What are the tips ?

Hi,
Since I migrated from SL to Lion on yesterday, Time Machine is stuck (my last - and only one backup in Lion is blocked at 17 kB whereas there still remains more than 17 GB to backup !).
I still can explore the backups by entering Time Machine but any new backup seems to be stuck.
Should I reformat my Time-machine USB external disk ?
Regards,
Franz
PS: OS X Lion is great...

os-app92 wrote:
Hi,
Since I migrated from SL to Lion on yesterday, Time Machine is stuck (my last - and only one backup in Lion is blocked at 17 kB whereas there still remains more than 17 GB to backup !).
I still can explore the backups by entering Time Machine but any new backup seems to be stuck.
See #D2 in Time Machine - Troubleshooting.

Time Machine not backing up iPhoto changes (Events, pictures, etc..)

So I finally decided to buy a external hard drive (WD) and backup some of my data to it using Time Machine. The initial backup went well with no problems but what I noticed is as I added events and pictures they were not appearing in Time Machine.
I could open time machine and view that my iPhoto had the current events when the date selected was "Today (now)", but as I went back in time the events that SHOULD of been there were not.
Browsing the folders on the backups showed the iPhoto database to be 13.5gb when actually the new size on my iMac was 19.5gb.
So why does Time Machine not detect these changes? For my backups I have excluded all folders except for the Users folder which contains the iPhoto library. Time Machine is not detecting the changes and backing it up. How can I fix this?

Yeah. At first I thought it was:
http://web.me.com/pondini/Time_Machine/D5.html
Because I was doing that earlier. But then realized I did repair permissions, not disk. But anyways decided to reboot (because I haven't up to this point).
Once it came back up I tried doing another backup. Didn't see it. Opened iPhoto again and exited it (checked Force Quit to make sure it wasn't open). Told it to do a BACKUP NOW. This time it saw a difference of like 7mb.
After it was done, went to iPhoto -> File -> Browse Backups. Went back a couple minutes when I did the backup and my event now has a place holder within the Events but it is pure black. I double clicked the event and it opened up and saw there were 3 files in there. They had default icons and were not showing as pictures like they were. (even though they display fine in iPhoto).
Time Machine seems very flakey to me. My machine is fully updated also.

Time machine stuck on 'calculating changes'

I have been using Time Machine backups to a 2TB Time Capsule for over a year, and one of my 4 computers has recently stopped backing up. The other 3 are still backing up fine, and I ran disk utility on the Time Capsule which stated that it was working fine as well. Backing up my MacBook Pro is now stuck in an endless (over 24 hrs) 'calculating changes'. I have tried directly connecting it via ethernet to the Time Capsule, but still have the same problem. I'd prefer not to start from scratch as the base backup is around 250GB. Any advice?

Well, I repaired the disk -- but still having the same problem. Seems to be getting stuck at the same place in the log:
Starting standard backup
Attempting to mount network destination using URL: afp://Mark%[email protected]/Data
Mounted network destination using URL: afp://Mark%[email protected]/Data
Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin, 262): no suitable image found. Did find:\n /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: mach-o, but wrong architecture
Cannot find function pointer VRPreviewCFPlugInFactory for factory 20D1C6B2-6A02-11D7-B5A6-000393D45566 in CFBundle/CFPlugIn 0x10050db60 </Library/Plug-ins/DiskImages/NUMPlugin.bundle> (bundle, not loaded)
Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin, 262): no suitable image found. Did find:\n /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: mach-o, but wrong architecture
Cannot find function pointer VRPreviewCFPlugInFactory for factory 20D1C6B2-6A02-11D7-B5A6-000393D45566 in CFBundle/CFPlugIn 0x10050db60 </Library/Plug-ins/DiskImages/NUMPlugin.bundle> (bundle, not loaded)
2010-09-12 18:23:53.015 diskimages-helper[256:2103] Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin, 262): no suitable image found. Did find:
/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: mach-o, but wrong architecture
2010-09-12 18:23:53.018 diskimages-helper[256:2103] Cannot find function pointer VRPreviewCFPlugInFactory for factory 20D1C6B2-6A02-11D7-B5A6-000393D45566 in CFBundle/CFPlugIn 0x1003193a0 </Library/Plug-ins/DiskImages/NUMPlugin.bundle> (bundle, not loaded)
2010-09-12 18:23:53.189 diskimages-helper[256:2103] Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin, 262): no suitable image found. Did find:
/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: mach-o, but wrong architecture
2010-09-12 18:23:53.190 diskimages-helper[256:2103] Cannot find function pointer VRPreviewCFPlugInFactory for factory 20D1C6B2-6A02-11D7-B5A6-000393D45566 in CFBundle/CFPlugIn 0x1003193a0 </Library/Plug-ins/DiskImages/NUMPlugin.bundle> (bundle, not loaded)
QUICKCHECK ONLY; FILESYSTEM CLEAN
2010-09-12 18:23:55.265 diskimages-helper[263:2103] Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin, 262): no suitable image found. Did find:
/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: mach-o, but wrong architecture
2010-09-12 18:23:55.267 diskimages-helper[263:2103] Cannot find function pointer VRPreviewCFPlugInFactory for factory 20D1C6B2-6A02-11D7-B5A6-000393D45566 in CFBundle/CFPlugIn 0x10051bae0 </Library/Plug-ins/DiskImages/NUMPlugin.bundle> (bundle, not loaded)
2010-09-12 18:23:55.402 diskimages-helper[263:2103] Error loading /Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPlugin: dlopen(/Library/Plug-ins/DiskImages/NUMPlugin.bundle/Contents/MacOS/NUMPl

Time Machine gets stuck on cleaning up

Hi, I can't complete a back up successfully with Time Machine. I get stuck on the 'cleaning up' phase and then it stays there forever. I actually went to work and when I came home it was still in the same state. Then I can't stop the back-up cleanly. I have to go in to Activity Monitor to force quit.
Following the advice on pondini.org I have installed the Buddy widget. It tells me that....
Starting standard backup
Network destination already mounted at: /Volumes/Data
Failed to attach to image: /Volumes/Data/gemzap_001f5bed6067.sparsebundle, DIHLDiskImageAttach returned: 35
Disk image /Volumes/Data/gemzap_001f5bed6067.sparsebundle mounted at: /Volumes/Backup of gemzap
Backing up to: /Volumes/Backup of gemzap/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason:must scan subdirs|new event db|
Node requires deep traversal:/Users/gemzap/Pictures/iPhoto Library reason:contains changes|must scan subdirs|found in deep scan|missed reservation|
Following advice on here, I have also done a verify/repair disk on both my macbook and the time capsule external drive. Both reported to be ok.
Any ideas? Any help would be much appreciated!
Many thanks
gemzap

No luck I'm afraid.... I dismounted (then completely unplugged) the time capsule. Then reconnected, clicked in to the timecapsule drive to make sure it wasn't napping, and tried again. The messages on the time machine read as follows..
22:25 Making back up disk available
Calculating changes
22:27 Scanning 800,713 items
Preparing xxx items
22:58 Cleaning up - for 8 hours.
So at 7am this morning I clicked stop back up. But again that hasn't don't anything, so have just done a force quit in Activity Monitor.
Time Machine buddy says...
Starting standard backup
Attempting to mount network destination using URL: afp://Gemma%[email protected]/Data
Mounted network destination using URL: afp://Gemma%[email protected]/Data
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/Data-1/gemzap_001f5bed6067.sparsebundle mounted at: /Volumes/Backup of gemzap
Backing up to: /Volumes/Backup of gemzap/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/Users/gemzap/Pictures/iPhoto Library reason:must scan subdirs|missed reservation|
Node requires deep traversal:/ reason:must scan subdirs|new event db|
I'm at a loss.
Should I try deleting the gemzap_001f5bed6067.sparsebundle file? Could that help?
Many thanks
gemzap

Time Machine is stuck in a Loop

Time Machine seems to be stuck in a loop and hasn't backed up in 13 days. Here's the information:
Name: Time Machine Backups
Available: 6.33 GB of 319.73 GB
Oldest BackUp: July 19, 2009
Latest Backup: October 15, 2009
_*Backing Up: ➊Calculating changes, ➋Cleaning up, ➌Making backup disk available*_
The last line goes from 1 to 2 to 3 then starts over. The Backup never occurs. I checked and both my MBP and the external drive are connected to the Airport Extreme wirelessly. I can even see the drive in Finder. I disconnected everything and restarted both the Airport Extreme and the drive. I then re-connected and the same thing keeps happening. I have a MBP 15in 2.66 Early 2009 and running OS X 10.6.1. I bought the Airport Extreme when they were first sold. All software is up to date.
Help!!

*Ok I disconnected the TM drive from the Airport Extreme and connected it to my MBP. I ran Disk Utility on the TM using Repair Disk . It found errors and fixed them all. I re-connected the drive to the Airport Extreme and attempted another backup. Here is the log:*
+Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine%20Backups+
+Mounted network destination using URL: afp://[email protected]/Time%20Machine%20Backups+
+Disk image /Volumes/Time Machine Backups/JohnDoe’s MacBook Pro_002500ce290a.sparsebundle mounted at: /Volumes/Backup of JohnDoe’s MacBook Pro+
+Backing up to: /Volumes/Backup of JohnDoe’s MacBook Pro/Backups.backupdb+
+Event store UUIDs don't match for volume: Macintosh HD+
+Node requires deep traversal:/ reason:must scan subdirs|new event db|+
+Compacting storage: 21.73 GB requested (including padding), 5.87 GB available before compacting+
+Stopping backup.+
+Backup canceled.+
+Ejected Time Machine disk image.+
+Compacting backup disk image to recover free space+
*Then it started over. Here is the long after it stared over:*
Starting standard backup
Network destination already mounted at: /Volumes/Time Machine Backups
Disk image /Volumes/Time Machine Backups/JohnDoe’s MacBook Pro_002500ce290a.sparsebundle mounted at: /Volumes/Backup of JohnDoe’s MacBook Pro
Backing up to: /Volumes/Backup of JohnDoe’s MacBook Pro/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason:must scan subdirs|new event db|
Starting pre-backup thinning: 21.73 GB requested (including padding), 5.87 GB available
Found partially deleted backup - trying again to delete: 2009-07-27-052350
Error -47 deleting backup: /Volumes/Backup of JohnDoe’s MacBook Pro/Backups.backupdb/JohnDoes MacBook Pro/2009-07-27-052350
Deleted backup /Volumes/Backup of JohnDoe’s MacBook Pro/Backups.backupdb/JohnDoes MacBook Pro/2009-07-27-052350: 5.87 GB now available
Found partially deleted backup - trying again to delete: 2009-07-28-011547
Error -47 deleting backup: /Volumes/Backup of JohnDoe’s MacBook Pro/Backups.backupdb/JohnDoes MacBook Pro/2009-07-28-011547
Deleted backup /Volumes/Backup of JohnDoe’s MacBook Pro/Backups.backupdb/JohnDoes MacBook Pro/2009-07-28-011547: 5.87 GB now available
Found partially deleted backup - trying again to delete: 2009-07-29-002053
Error -47 deleting backup: /Volumes/Backup of JohnDoe’s MacBook Pro/Backups.backupdb/JohnDoes MacBook Pro/2009-07-29-002053
Deleted backup /Volumes/Backup of JohnDoe’s MacBook Pro/Backups.backupdb/JohnDoes MacBook Pro/2009-07-29-002053: 5.87 GB now available

Time machine gets stuck on indexing

Since the last weeks my time machine will not backup anymore..
I have searched around but couldn't find out what will fix it..
This is what the module had to say:
Starting standard backup
Attempting to mount network destination using URL: afp://admin@TM_Twan.local/MyShare
Mounted network destination using URL: afp://admin@TM_Twan.local/MyShare
Warning: Destination /Volumes/MyShare does not support TM Lock Stealing
Warning: Destination /Volumes/MyShare does not support Server Reply Cache
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/MyShare/MacBook Pro van Antoine van der Lee.sparsebundle mounted at: /Volumes/Time Machine-reservekopieën
Backing up to: /Volumes/Time Machine-reservekopieën/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
I hope you guys can help me..
Kind regards,
Twan

AJvanderLee wrote:
There was only one thing i could not do, i could not repair my backups, because they didn't appear in the disk utility..
What are you backing-up to? If you can see the +sparse bundle+ your backups are in via the Finder, use the instructions in #A5 for repairing the backups on a Time Capsule. If you can't see it, you can't repair them with DIsk Utility (or most 3rd-party disk repair apps). Check with the maker of the NAS for help.
Further, i thought it would be something with the message "Event store UUIDs don't match for volume: Macintosh HD"
That's normal after a failed/cancelled backup, and will be repeated each time until one completes successfully. See #A6 in Troubleshooting for details.
Besides, my spotlight is now indexing my harddisk and seems to get stuck on "calculating time for indexing"
This is because i excluded my harddisk from spotlight, restarted my mac and then included my harddisk again for spotlight. So it needed to reindex it, but i'm not sure that it will work, because it allready toke the whole day for it and is still saying the same thing..
That sounds like a problem with a file or the directory structure on your internal HD. Did you verify your internal HD, per #3 in the green box? If so, and if it says it's ok, exclude your internal HD from Spotlight indexing until you get your backups working; then you can figure out what's wrong with Spotlight.

Time Machine is stuck at calculating changes

Similar Messages

Maybe you are looking for