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).

Similar Messages

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.

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 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 on 'caculating changes'

I upgraded to snow leopard with no problems except that I can't get a time machine backup completed. The message is stuck on 'calculating changes'. I have done a reset of time machine etc. but no luck so far. Any advice? Message in my time machine widget is:
Backing up to: /Volumes/Ivisonbackup/Backups.backupdb
Event store UUIDs don't match for volume:....
Waiting for index to be ready (101)
etc.
Thanks

Hi, and welcome to the forums.
What's the "etc." ?
If it's more of the "Waiting for index . . ." messages, that's likely a problem with your TM volume, or communicating with it.
Start by repairing your backups, per #A5 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of the +Time Machine+ forum).
If that doesn't help, post back with details, including all the messages, your setup (especially the destination for the backups), what you've done, and the results.
Message was edited by: Pondini

Time Capsule / Time Machine very very slow

I'v been having problems with very slow backups using a Time Machine / Time Capsule combo and I've been looking around this forum and the web in order to figure out what it is, but I couldn't find any specifics relating to my situation. Both the preparation and the backing up stages are both very slow.
I hadn't used Time Machine since before Christmas as it become unreliable after updating to Yosemite but thought I'd try and get backups running again. It took about 16 hours to complete it's first backup of 17gb, then today's backup of 475.9mb took 4 hours to prepare and it's only backed up 167.7mb as I write this.
Can anyone with a good technical understanding of OS X, Time Capsule & Time Machine backups tell me what the problem is by looking at the console output below?
Hope someone can help, thanks.
Specs are:-
MacbookPro early 2011
OS X 10.10.1 Yosemite
Time Capsule- 4th gen 2TB
Console:-
Feb 4 00:27:32 xxxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Ejected Time Machine disk image: /Volumes/Data-1/xxxxxxx MacBook Pro.sparsebundle
Feb 4 00:27:33 xxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Ejected Time Machine network volume.
Feb 4 00:27:33 xxxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Running automatic backup verification.
Feb 4 00:27:33 xxxxxxxMacBook-Pro-2.local com.apple.backupd[135]: Attempting to mount network destination URL: afp://xxx%20xxxxx;AUTH=SRP@xxxxxxxx%20Time%20Capsule._afpovertcp._tcp.local/Dat a
Feb 4 00:27:33 xxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Mounted network destination at mount point: /Volumes/Data-1 using URL: afp://xxx%20xxxxx;AUTH=SRP@xxx%20xxxxxx%20Time%20Capsule._afpovertcp._tcp.local /Data
Feb 4 00:28:04 xxxxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Verifying backup disk image.
Feb 4 00:32:50 xxxxxxxx-MacBook-Pro-2.local com.apple.backupd-helper[44]: Not starting scheduled Time Machine backup: Backup already running
Feb 4 08:56:30 localhost com.apple.xpc.launchd[1] (com.apple.backupd-status): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Feb 4 08:56:30 localhost com.apple.xpc.launchd[1] (com.apple.backupd.status.xpc): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Feb 4 08:56:30 localhost com.apple.xpc.launchd[1] (com.apple.backupd-helper.status): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Feb 4 08:56:30 localhost com.apple.xpc.launchd[1] (com.apple.backupd-auto): This service is defined to be constantly running and is inherently inefficient.
Feb 4 08:56:58 xxxxxx-MacBook-Pro-2.local backupd[133]: Property list invalid for format: 200 (property lists cannot contain NULL)
Feb 4 08:56:59 xxxxxx-MacBook-Pro-2.local backupd[133]: Property list invalid for format: 200 (property lists cannot contain NULL)
Feb 4 08:57:00 xxxxxxx-MacBook-Pro-2.local backupd[133]: Property list invalid for format: 200 (property lists cannot contain NULL)
Feb 4 08:57:10 xxxxxxx-MacBook-Pro-2.local backupd[133]: Property list invalid for format: 200 (property lists cannot contain NULL)
Feb 4 08:57:20 xxxxxx-MacBook-Pro-2.local backupd[133]: Property list invalid for format: 200 (property lists cannot contain NULL)
Feb 4 08:59:24 xxxxxx-MacBook-Pro-2.local SystemUIServer[224]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
Feb 4 08:59:24 xxxxxxx-MacBook-Pro-2.local com.apple.prefs.backup.remoteservice[370]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
Feb 4 09:26:41 xxxxxxx-MacBook-Pro-2.local com.apple.backupd-helper[44]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
Feb 4 09:27:11 xxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Starting automatic backup
Feb 4 09:27:11 xxxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Attempting to mount network destination URL: afp://xxx%20xxxxxx;AUTH=SRP@xxxxxxxx%20Time%20Capsule._afpovertcp._tcp.local/Da ta
Feb 4 09:27:13 xxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Mounted network destination at mount point: /Volumes/Data-1 using URL: afp://xxxx%20xxxxx;AUTH=SRP@xxxxx%20xxxxx%20Time%20Capsule._afpovertcp._tcp.loc al/Data
Feb 4 13:06:27 xxxxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Disk image /Volumes/Data-1/xxxxxxxxs MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Feb 4 13:06:40 xxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Backing up to /dev/disk3s2: /Volumes/Time Machine Backups/Backups.backupdb
Feb 4 13:39:28 xxxxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Will copy (323.4 MB) from Macintosh HD
Feb 4 13:39:28 xxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Found 7354 files (432.7 MB) needing backup
Feb 4 13:39:28 xxxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: 799.1 MB required (including padding), 563.6 GB available

Feb 4 08:56:30 localhost com.apple.xpc.launchd[1] (com.apple.backupd-status): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
There is an 8 hour gap between this message and the one before it.
This message is related to the use of encryption. If you are still getting it even after you have turned encryption off then something is still hanging around. And it is a big problem.
The previous log entry that it may also be the concern is
Feb 4 00:28:04 xxxxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Verifying backup disk image.
So it is doing a full verify of the backup.. that is extremely time consuming over wireless. It takes much longer to verify than to do the backup. That is because of the long gap since the last backup. When you wait so long it is sometimes better to simply start over.
It is essential when this happens to be using ethernet with wireless turned off.
Make sure IPv6 is set correctly to link-local only in the ethernet settings of the computer.
Why your latest one is so slow is again a Yosemite bug mystery.
However I would like you to test actual network speed copying files to the TC.
Stop the present backup.. if it is still running. Then via finder simply copy a file to the TC hard disk.. a single very large file say 100-1000MB and give me a network speed using activity monitor.
Yosemite has real network issues on top of real TM issues.
Test by doing a TM backup to a USB drive plugged into the computer. If this is dramatically faster the issue is mostly network rather than TM.
If it still fails to backup in reasonable time periods.. and for people having big issues.. I recommend give up on TM until apple have managed to patch the bugs. Use an alternative like Carbon Copy Cloner.. I would do that even if TM does work if you want a backup you can trust.

External drive and time capsule/time machine

Just purchased external hard drive and moved iPhoto library and iMovie clips to external hard drive. Have been using time capsule/time machine to back up computer. Added new external hard drive to time machine backup, but backups seem to hang up when preparing files for external drive. What is going on? Still running Snow Leopard, on iMac.

Hello, vascocaco.
If I understand correctly, you're wondering if you can use your Time Capsule's internal hard disk both for Time Machine backups and as an ordinary drive. Is this your question?
You can, but Time Machine backups may take longer.
To do it, you should partition your Time Capsule's hard disk to create one volume for the backups and one for other files.

My Time capsule/time machine stopped backing up and states no disk found-now I can't even get connected to time capsule

My Time capsule/time machine stopped backing up and states no disk found-now I can't even get connected to time capsule. When I go into sys pref and time machine nothing comes up and it just keeps stating rescan

Go to to your Users/Home/Library/Application Support/iWeb folder in the Finder and then enter Time Machine. Go back to the last backup that has the domain file, select it and use the Restore button.
OT

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.

Time machine hung on calculating changes (stuck at 99%)

Im experiencing a few problems with time machine which is currently set to back up wirelessly to a time capsule. This has been working great for about a year now never any problems with any backup in the past but over the last day i can not get a backup to complete.
N.B; i have been staying away for the past two weeks as i am at university so i'm aware the first backup will be large with a two week gap. Though this is not usually a problem. The other change is i have recently changed the net work set up, before Time capsule was connected to another router (BT Voyager 205) in bridge mode, now i have a new router (BT home hub 2.0) and have re-configured time capsule to simply join the wireless network for back up and storage purposes.
Heres what i have tried:
Powering down the time capsule and my laptop several times
unselecting the disk in the time machine options, selecting none and then re-selecting the disk
a full reset of time machine (followed the steps found here; http://discussions.apple.com/thread.jspa?threadID=2057525)
Heres the console log messages:
05/03/2010 12:09:02 com.apple.backupd[281] Starting standard backup
05/03/2010 12:09:02 com.apple.backupd[281] Attempting to mount network destination using URL: afp://James%20Clough@James%20Clough's%20Time%20Capsule.afpovertcp.tcp.local/Data
05/03/2010 12:09:02 com.apple.backupd[281] Mounted network destination using URL: afp://James%20Clough@James%20Clough's%20Time%20Capsule.afpovertcp.tcp.local/Data
05/03/2010 12:10:41 com.apple.backupd[281] Disk image /Volumes/Data-1/James MacBook_0023df8f4ff4.sparsebundle mounted at: /Volumes/Backup of James MacBook
05/03/2010 12:10:47 com.apple.backupd[281] Backing up to: /Volumes/Backup of James MacBook/Backups.backupdb
05/03/2010 12:10:53 mds[36] (Normal) DiskStore: Rebuilding index for /Volumes/Backup of James MacBook/Backups.backupdb
05/03/2010 12:13:35 com.apple.backupd[281] Event store UUIDs don't match for volume: Macintosh HD
05/03/2010 12:16:33 com.apple.backupd[281] Node requires deep traversal:/ reason:must scan subdirs|new event db|
05/03/2010 12:16:36 mds[36] (Normal) DiskStore: Creating index for /Volumes/Backup of James MacBook/Backups.backupdb
05/03/2010 12:20:16 com.apple.backupd[281] Node requires deep traversal:/Users/James/Pictures/iPhoto Library reason:contains changes|must scan subdirs|found in deep scan|missed reservation|
also noticed for the first time that when clicking into spotlight search at the right of the screen i see:
"Indexing backup of James' Macbook"
with an estimating time bar below which keeps spinning giving no time, just says estimating??
thankyou to anyone who can help shed some light on this problem.

vengenceJC wrote:
also noticed for the first time that when clicking into spotlight search at the right of the screen i see:
"Indexing backup of James' Macbook"
with an estimating time bar below which keeps spinning giving no time, just says estimating??
The combination of symptoms sounds like your backups may be corrupted. Cancel the backup and Repair them per #A5 in the Troubleshooting Tip.
You might want to exclude the drive from Spotlight indexing temporarily, until the backup is done, via +System Preferences > Spotlight > Privacy.+
And since Time Machine has to do a "deep traversal," connect to the Time Capsule via Ethernet if at all possible -- both the "deep traversal" and actual backup will be faster that way.

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...

Why does time machine stall on "calculating changes"?

I have just purchased a Lacie d2 quadra 2Tb, and have connected Time Machine.
It has successfully backed up my desktop. However, on about the third incremental backup it stall on calculating changes. I have read that this could be when a deep traversal scan is occuring, so I let it continue for 12 hours before rebooting!
I have repartitioned and zeroed out the disk, and verified permissions etc, but to no avail.
I have 2 other external drives, and a Time Capsule that work flawlessly with TM.
Any other suggestions to remedy this would be most welcome.

Thanks for your reply Dave. Well, I am on that path with Lacie. The two other drives are theirs also, but who knows. They recommended th zeroing out etc.
I am also in discussion with Apple, who are tackling it from the Time Machine end, and something that might require a tweak with my system.

Time capsule backup failure after moving and changing internet access

I bought a 1GB time capsule to backup my MacBook Pro using time machine and also archived files so I would have these when I had to move across country to work temporarily. The time capsule was working fine in my home after the original backup through an ATT DSL, but I then moved across country and set up a Comcast cable DSL and now Time machine records under Backing up: Preparing and the latest backup records failure. Is there a way of fixing this without erasing the entire Time Capsule and then taking 2-3 days of backing up again and will I have access to these when I return to my original home with the capsule and MacBook Pro. I have tried resetting all the backup modes and options.

Linda,
According to the logs, you are going to need to initiate a backup, and then let it do it's thing uninterrupted, perhaps all day of over night. Time Machine needs to do a "deep traversal". See this article.
*_Time Machine May Report "Preparing..." For a Long Time_*
First, it’s good to determine WHY Time Machine is "Preparing..." for an extended period of time. Examining the Console logs during this event can reveal what is actually going on behind the scenes. It may be “Preparing…” for a genuinely good reason. How long is 'too long' to wait for Time Machine to finish "Preparing..."? Some times, "Preparing..." is required to perform the normal housekeeping that Time Machine does periodically. Other times, it really is "stuck" and never proceeds after many hours.
*”Deep Traversal” (Recent Crash / Forced Restart / System Update / Extended Period Between Backups)*
According to the following KB article it can sometimes take quite a long time if Time Machine begins a “deep traversal” and has to compare data inventories. This may apply to your situation, particularly if many Gigs of data are involved. [http://support.apple.com/kb/TS1516]
You see, Time Machine *+does not+* ordinarily perform file-by-file comparisons to determine what has changed and thus determine what needs to be backed up. Rather, Time Machine relies on FSEvents notifications. This is a log that the system uses to keep track of changes to directories. Rather than scan tens of thousands of files for changes each time, Time Machine simply looks at this log and narrows its’ scan to only the directories that have experienced changes since the last backup. Otherwise, Time Machine would have to be running constantly just to catch every change on its own and thus eat up precious CPU.
Every event that FSEvents records has its’ own ID which includes a time stamp. At the end of every backup, Time Machine stores the last event ID that it processes. When the next backup is initiated, Time Machine looks at this stored ID and determines that it only needs to backup events that have occurred after the time stamp on this last event ID.
If, due to a system crash, power failure, forced restart, or some other major system event, Time Machine cannot find this last event ID in the system logs then it will consider the FSEvents log “untrustable” and it will go into what’s called “deep traversal”. The Console logs may report +“Event store UUIDs don't match”.+ In this event, Time Machine will by-pass the system log entirely and perform its’ own file-by-file comparison to determine what has changed since its’ last backup. Obviously, if tens or hundreds of Gigs are involved, then this process can take quite some time and should be allowed to proceed.
Additionally, it appears that if Time Machine has to go back too far to find the last event ID, then it will give up and simply go into “deep traversal” and do the file-by-file scan on its’ own. This can occur if Time Machine has not been able to perform its’ hourly backups for some time, as is the case for users who only backup once a week or so. This is also the case with major Mac OS system updates that change thousands of files at one time. There are simply too many events logged by the system for Time Machine to bother looking for the last known event ID.
Cheers!

Time Capsule, Time Machine & Lion

When I installed Lion, Time Machine would get stuck on backing up (Console would report "waiting for index to be ready over and over). I erased the the existing Time Machine Back up and started over to see if that Fixed the problem. While it does back up now, it indexes everytime, is this normal. This takes a lot of time almost to the point where it is time to back up again. Console still reports waiting for index to be ready. I copied what console shows. It is backing up to a Time Capsule via wifi. Please help
11/10/11 7:21:25.785 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
11/10/11 7:27:31.821 PM com.apple.backupd: 1.05 GB required (including padding), 1.42 TB available
11/10/11 7:27:31.821 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:28:32.261 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:29:34.097 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:30:35.399 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:31:35.449 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:32:37.180 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:33:37.883 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:34:38.874 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:35:40.915 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:36:41.803 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:37:43.029 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:39:02.990 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:40:04.262 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:41:06.392 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:42:48.224 PM com.apple.backupd: Copied 2540 files (12.7 MB) from volume Macintosh HD.
11/10/11 7:43:28.122 PM com.apple.backupd: 1.03 GB required (including padding), 1.42 TB available
11/10/11 7:43:28.123 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:44:28.373 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:45:30.040 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:46:31.590 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:47:33.622 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:48:33.835 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:50:47.156 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:51:47.364 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:52:47.870 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:53:48.955 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:54:49.311 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:55:51.191 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:56:56.408 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:57:56.582 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:58:57.086 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 7:59:58.003 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:01:51.368 PM com.apple.backupd: Copied 2486 files (11.5 MB) from volume Macintosh HD.
11/10/11 8:02:03.027 PM com.apple.backupd: Starting post-backup thinning
11/10/11 8:02:30.912 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups/Backups.backupdb/Macintosh/2011-11-09-190010 (17.1 MB)
11/10/11 8:02:30.912 PM com.apple.backupd: Post-back up thinning complete: 1 expired backups removed
11/10/11 8:02:31.727 PM com.apple.backupd: Backup completed successfully.
11/10/11 8:02:39.313 PM com.apple.backupd: Ejected Time Machine disk image.
11/10/11 8:02:39.865 PM com.apple.backupd: Ejected Time Machine network volume.
11/10/11 8:21:03.134 PM com.apple.backupd: Starting standard backup
11/10/11 8:21:04.867 PM com.apple.backupd: Attempting to mount network destination URL: afp://Jim%20George@Jim%20George's%20Time%20Capsule._afpovertcp._tcp.local/Data
11/10/11 8:21:18.104 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Data using URL: afp://Jim%20George@Jim%20George's%20Time%20Capsule._afpovertcp._tcp.local/Data
11/10/11 8:21:27.441 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
11/10/11 8:21:30.353 PM com.apple.backupd: Disk image /Volumes/Data/Macintosh.sparsebundle mounted at: /Volumes/Time Machine Backups
11/10/11 8:21:30.391 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
11/10/11 8:27:07.191 PM com.apple.backupd: 1.04 GB required (including padding), 1.42 TB available
11/10/11 8:27:07.191 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:28:07.901 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:29:08.520 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:30:08.521 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:31:08.948 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:32:09.495 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:33:09.870 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:34:11.792 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:35:13.128 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:36:13.170 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:37:14.241 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:38:14.896 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:39:16.217 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:40:17.141 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:41:17.247 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:42:35.449 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:43:35.753 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:44:39.042 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:48:55.227 PM com.apple.backupd: Copied 2995 files (18.6 MB) from volume Macintosh HD.
11/10/11 8:49:39.536 PM com.apple.backupd: 1.05 GB required (including padding), 1.42 TB available
11/10/11 8:49:39.536 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:50:40.941 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:51:41.931 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:52:43.078 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:53:43.333 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:54:45.281 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:55:46.397 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:56:46.675 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:57:48.137 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:58:48.794 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 8:59:49.721 PM com.apple.backupd: Waiting for index to be ready (100)
11/10/11 9:00:51.823 PM com.apple.backupd: Waiting for index to be ready (100)

Jim George wrote:
When I installed Lion, Time Machine would get stuck on backing up (Console would report "waiting for index to be ready over and over). I erased the the existing Time Machine Back up and started over to see if that Fixed the problem. While it does back up now, it indexes everytime, is this normal.
No.
You might want try deleting the index. See the pink box in #D2 of Time Machine - Troubleshooting.

Time Capsule / Time Machine stuck on 'calculating changes'

Similar Messages

Maybe you are looking for