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.

Similar Messages

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 getting stuck on random hourly backups?? Please help!

I set up Time Machine the yesterday, it compleated it's initial backup fine, and performed about 10 or so hourly backups, then randomly on one of it's hourly backups it got stuck. It never actually started the backup. The preferences said it was backing up, but the progress bar wasn't moving, and there was no activity on the drive. I stopped the "backup", and from then on I could not get it to do another backup.
So last night I reformatted the external and decided to let TM start over. Once again it finished the initial backup fine, and I went to bed. While I was in bed it finished 3 more hourly backups, and I woke up this morning to find it stuck again, trying to do it's 2:05AM backup. The computer was awake all night, so it should have no problems. The preferences say it is backing up, but never makes any progress, and there is no drive activity.
Here is the relavent errors from my System log:
Nov 1 02:05:50 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Backup requested by automatic scheduler
Nov 1 02:05:50 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Starting standard backup
Nov 1 02:05:57 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Backing up to: /Volumes/Backup/Backups.backupdb
Nov 1 02:05:57 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Ownership is disabled on the backup destination volume. Enabling.
Nov 1 02:05:57 todd-sullivans-imac KernelEventAgent[35]: tid 00000000 received unknown event (256)
*Nov 1 02:05:59 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Event store UUIDs don't match for volume  Macintosh HD*
*Nov 1 02:05:59 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|*
Nov 1 02:09:45 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: No pre-backup thinning needed: 14.57 GB requested (including padding), 132.30 GB available
Nov 1 02:09:46 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: MDBackupBegin() returned result (909) > 0, waiting
Nov 1 02:10:16 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: MDBackupBegin() returned result (906) > 0, waiting
Nov 1 02:10:46 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: MDBackupBegin() returned result (906) > 0, waiting
I bolded the entries that I assume are the problem, but I don't know what it could be. Why does it randomly get stuck on hourly backups. BTW The "waiting" is just repeating over and over etc..... Help! Or it's back to CCC for me. Thanks
EDIT: Tried it a 3rd time, and this time it managed to do 25 hourly backups before getting stuck. does anyone have a clue here, I'd like to get this working. Every time it stops working I have to format the drive and start over to get it to backup again.
Message was edited by: tms2010
Message was edited by: tms2010
Message was edited by: tms2010

The deep traversal is being done because something in the TM data base is corrupted or not trusted. The deep traversal means the TM backupd process has to traverse your whole set of volumes being backed up. This is a very lengthy process.
No matter, it does seem you're hitting a snag of some kind. The best response I can give is for you to send the evidence to Apple feedback for the software engineers to review.
People on this forum are unlikely to know what the problem is nor have a fix for you.
When you formatted your TM backup Volume to you zero it out using Disk Utility. You could be running into an unrecoverable disk i/o error - a bad spot on the backup HD or even a bad spot on your internal HD.

Time Machine gets stuck on 'Making Backup Disk Available'

This has been happening a few days now. Time machine kicks off a backup but it never gets anywhere. It just keeps spinning and saying 'Making Backup Disk Available'
The log says only:
Starting standard backup
Attempting to mount network destination using URL: afp://[email protected]/Jim's%20Time%20Capsule
Mounted network destination using URL: afp://[email protected]/Jim's%20Time%20Capsule
I tried to use Disk Utility to repair the sparsebundle and although it says it needs to be repaired, when I click repair it quickly says it 'Volume Repair Complete' but then gets stuck on ''Updating Boot Support Partitions for the volume as required'. I left it on all night to see if it would ever finish and it never did.
Where do I go from here?
Thanks

Where do I go from here?
if disk utility can not repair the sparse bundle you can try repairing it with disk warrior or a similar tool. if that does not work either you need to trash the sparse bundle and start backups from scratch. there isn't anything else you can do.
Thanks

Initial Time Machine Backup Stuck on "Indexing Backup"

I have Mac Mini running 10.7.2. I just got an external hard drive and am trying to run an initial back up using Time Machine. I am running my computer in Safe Mode as it won't start in regular mode. I formatted the HD and began to run Time Machine back up. HD is connected via USB 2.0 wire.
It has now been 12 hours and is still on Indexing Backup... Is this normal for initial back up? I know it takes a long time for initial but this doesn't seem right.What do I do to correct if it isn't correct? Should I stop and try again?

Thank you very much. With your info I gave up on the back up and ran Disk and Permission Repair for the 3rd or 4th time and crossed my fingers and restarted my machine and it WORKED! I ran time Machine back up and when I woke up this morning it was all done! Yeahhhh!
I wasn't sure what was causing it not to start in regular mode and as I'm not too much of a techie I was scared that I was teetetering on the brink of losing everything. The machine would run so I didn't think it was a hard drive issue, but not knowing for sure I was concerned and after losing everythign once before years ago, I was worried. I have it backed up on line but wanted a 2nd (local) version that wouldn't entail tying up bandwidth for days. In the end it worked out!
But the short answer is, Time Machine Backup does NOT work in Safe Mode...

Time Machine gets stuck at backing up 4 kb of 200.8 gb?

I am running Time Machine for the first time on a recently re-installed system (I had to restore from a prior Time Machine back-up). I am trying to run Tim eMachine on the re-installed system, and it gets hung-up on 4 kb of 200.8 gb in the back-up process. I have two externl hard drvies, and on the other hard drive, if I use it as the back-up destination, it gets hung-up on 0kb out of 104mb.
Very odd. Thoughts?

Hmm. Why did you have to restore? If there was a problem with your installation of OSX, it (or part of it) may have been backed-up and restored.
You might want to install a fresh version of OSX (that won't disturb anything else), per Installing the ''combo'' update and/or Reinstalling OSX.

Time machine taking too long (indexing)

I run my time capsule to back up both of my computers
a Imac 2GHz intel core duo running 10.6.8 and
an Imac 3.4GHz intel core i7 running 10.7.4
both are connected wirelessly to the Time Capsule
Recently, on the older machine, backups have stalled. I can work on it for a while, doing disk repairs and disk permissions with the Snow Leopard installation disk utility and 'fix' it for multiple backups - and all is well. Then it stalls on 'indexing backup' again. Meanwhile, the new machine running Lion is just fine. I just noticed it again.
Last successful backup was 0517 this morning (EST) and this was at approx 1700 (5 evening). I sat at the computer and was working away when Snow Leopard became really slow and I noted that the Time Capsule was indicating indexing backup, I let it run for 45 minutes and it was still indexing backup, so I quite Time Machine and restarted at 1845 (645 evening). The restart of Time Machine allows Snow Leopard to regain its usual speed, Time machine reported a file count of 202 files that had changed and went to 'indexing backup' a half hour later it is still at 'indexing backup' (about 9 emails were received - how that relates to 202 files I am not sure)
Why does it work multiple times just fine and then all of a sudden stall? When it does stall it simply (over time I presume) eats up all available memory (1.5 gb) with page swaps each one getting bigger and bigger until all memory is gone. I can 'free memory' and recover to about 600 free (running email and browser app in the background) but the time machine does it all over again if I allow it to run.
As I said, I have used Disk Utility (with the Snow Leopard Installation disk to allow repair of the boot volume) and have repaired the disk and repaired permissions - several times. (some disk permissions are repaired - no disk repairs reported) After each time, I go back and restart Time Machine and 'poof' within an hour it performs a backup with no problems. I note that backups are performed on schedule for the next few days with no problems, and then bingo, the system is totally bogged down again, and Time Machine is stuck on indexing backup once again. I have not noticed any commonality as to when the problem occurs - sometimes after a day, sometimes after several days. And meanwhile, the Lion machine is performing flawlessly
At the moment my kludge to work around is to turn off Time Machine so as not to use up all the memory and then periodically use the installation disk routine to 'repair' (disk and permissions) and then backup, but this is NOT solving the problem long term of course.
The first time I noticed this (about two months ago) the disk repair did note a disk error the system was claiming 2 bytes less free space than there was, but after that time, all the disk repairs report fine.

Indexing can take a long time over wireless. You would do much better with ethernet connection.
Maybe the hard drive is failing.. The fact that the disk passes tests does not mean it is ok. As a disk ages it can have issues reading, where the same sector has to read multiple times.
I guess the ideal would be replace the machine.. it is several years old and really due for replacement.
Or at least the hard disk... although the cost of doing that job might not be worth it.
As a test I would do a backup using TM to a USB local disk plugged into it... that is good practice anyway when you are getting poor reliability on backups.
You can create a disk image using a other tools.. CCC or superduper.
A clone of the existing drive again can be worth it.
You can set to boot from FW drive and ignore the internal.. see if the problems go away.
Pondini is usually helpful although he doesn't have specific on this indexing issue.
http://pondini.org/TM/Troubleshooting.html

Time Machine error : Waiting for index to be ready (100)

Hello,
I'm having issues with Time Machine, the backup starts, an amount of data is backup and complete (ex 80Mb of 80Mb backuped up), then Time Machine goes back in indexing and get stuck in "Waiting for index to be ready (100)".
Here's what the console output for backupd looks like:
02/12/10 10:37:46 com.apple.backupd[213] Starting standard backup
02/12/10 10:37:46 com.apple.backupd[213] Attempting to mount network destination using URL: afp://[email protected]/tm-pedral
02/12/10 10:37:48 com.apple.backupd[213] Mounted network destination using URL: afp://[email protected]/tm-pedral
02/12/10 10:37:48 com.apple.backupd[213] Warning: Destination /Volumes/tm-pedral does not support Server Reply Cache
02/12/10 10:37:55 com.apple.backupd[213] QUICKCHECK ONLY; FILESYSTEM CLEAN
02/12/10 10:37:59 com.apple.backupd[213] Disk image /Volumes/tm-pedral/pedral-mac_34159e0fb504.sparsebundle mounted at: /Volumes/Time Machine Backups
02/12/10 10:37:59 com.apple.backupd[213] Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
02/12/10 10:38:20 com.apple.backupd[213] No pre-backup thinning needed: 795.5 MB requested (including padding), 357.72 GB available
02/12/10 10:41:07 com.apple.backupd[213] Copied 1842 files (79.2 MB) from volume Macintosh HD.
02/12/10 10:41:07 com.apple.backupd[213] No pre-backup thinning needed: 716.5 MB requested (including padding), 357.72 GB available
02/12/10 10:41:07 com.apple.backupd[213] Waiting for index to be ready (100)
02/12/10 10:42:09 com.apple.backupd[213] Waiting for index to be ready (100)
02/12/10 10:43:11 com.apple.backupd[213] Waiting for index to be ready (100)
02/12/10 10:44:13 com.apple.backupd[213] Waiting for index to be ready (100)
02/12/10 10:45:15 com.apple.backupd[213] Waiting for index to be ready (100)
02/12/10 10:46:17 com.apple.backupd[213] Waiting for index to be ready (100)
This backup-up has been working for days in the same conditions.
I've tried everything in #D2 in Time Machine - Troubleshooting but nothing changed. How to get more details on what's happening.
Thanks!
Laurent

pedral wrote:
Hello,
Hi, and welcome to the forums.
02/12/10 10:37:48 com.apple.backupd[213] Warning: Destination /Volumes/tm-pedral does not support Server Reply Cache
What are you backing-up to? That message indicates it may not be fully compatible with Time Machine.
If you've done everything in #D2, and it's a NAS, check with the maker. They may have updates or other troubleshooting info. Or it may be a hardware problem.

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.

4s won't reboot after ios7 update. I have restored 4 times. Every time it gets stuck on Apple icon with update bar at 10%

4s won't reboot after ios7 update. I have restored 4 times. Every time it gets stuck on Apple icon with update bar at 10%
HELP!

That's one of the weird things.. it recognizes it maybe 10% of the time. And usually, only after I do the two-button reset. Problem is.. since it won't charge above 2%, anytime I try to do a restore or anything like that using iTunes, my device shuts off and I lose whatever progress I'd made.
So, an update... after reading through a bunch of similar complaints (there are literally 1000's of them so there's NO WAY this isn't somehow ios7 related, thanks a lot APPLE ) I decided to try a restore in recovery mode. After 3 hours and several disconnections... I ended up having to just set it up as a new iPad, as the restore did nothing. Weirdly though... as I was doing the restore in recovery mode.. I noticed I'd gotten up to a 10% charge.. higher than it's been since September, so after setting it up as a new device, I turned it off and plugged it in using the wall charger. 2 hours later and I was up to 38%. Still not great, as my iPad, before ios7 could've fully charged twice in the amount of time it took for me to now get 28% more of a charge. And that's with a fully cleaned out device.. so that really ***** and I'm now more confused than ever.
But I'm gonna leave it overnight charging and see what I come up with tomorrow. Sadly, when I paid $600 for it in February, I never expected to have to play "wait and see" with it...

Time Machine backup to Time Capsule gets stuck

Hi all,
I'm backing up my MBP via ethernet to a Time Capsule. The incremental backups take forever and are driving me nuts. The backups seem to be getting stuck midway. The disk sounds like it's spinning but the progress bar doesn't move. Also, it seems to be copying over too many files every hour, like >60000 or so (log below). I doubt that so many files get modified every hour.
I've tried everything (I could think of and find on the discussion boards) like deleting the sparsebundle, deleting the entire backup drive, playing with the backup frequency, nothing works.
Please help!!
Thanks,
DB
11/27/08 10:02:57 PM /System/Library/CoreServices/backupd7045 Starting standard backup
11/27/08 10:02:57 PM /System/Library/CoreServices/backupd7045 Network mountpoint /Volumes/TC Backup Disk not owned by backupd... remounting
11/27/08 10:02:57 PM /System/Library/CoreServices/backupd7045 Network volume mounted at: /Volumes/TC Backup Disk-1
11/27/08 10:03:07 PM /System/Library/CoreServices/backupd7045 Disk image /Volumes/TC Backup Disk-1/Dhiren's MBP_002332d43774.sparsebundle mounted at: /Volumes/Backup of Dhiren's MBP
11/27/08 10:03:07 PM /System/Library/CoreServices/backupd7045 Backing up to: /Volumes/Backup of Dhiren's MBP/Backups.backupdb
11/27/08 10:04:39 PM /System/Library/CoreServices/backupd7045 No pre-backup thinning needed: 570.5 MB requested (including padding), 426.79 GB available
11/27/08 10:14:44 PM /System/Library/CoreServices/backupd7045 _*Copied 87124 files (20.3 MB) from volume Macintosh HD.*_
11/27/08 10:14:48 PM /System/Library/CoreServices/backupd7045 No pre-backup thinning needed: 559.1 MB requested (including padding), 426.69 GB available
11/27/08 10:15:02 PM /System/Library/CoreServices/backupd7045 Unable to rebuild path cache for source item. Partial source path:
11/27/08 10:15:02 PM /System/Library/CoreServices/backupd7045 Error: (-39) SrcErr:YES Copying (null) to (null)
11/27/08 10:15:14 PM /System/Library/CoreServices/backupd7045 Copied 1067 files (10.6 MB) from volume Macintosh HD.
11/27/08 10:15:22 PM /System/Library/CoreServices/backupd7045 Starting post-backup thinning
11/27/08 10:15:22 PM /System/Library/CoreServices/backupd7045 No post-back up thinning needed: no expired backups exist
11/27/08 10:15:22 PM /System/Library/CoreServices/backupd7045 Backup completed successfully.
11/27/08 10:15:26 PM /System/Library/CoreServices/backupd7045 Ejected Time Machine disk image.
11/27/08 10:15:32 PM /System/Library/CoreServices/backupd7045 Ejected Time Machine network volume.
11/27/08 10:15:32 PM /System/Library/CoreServices/backupd7045 Ejected Time Machine network volume.

Hi all,
I'm backing up my MBP via ethernet to a Time Capsule. The incremental backups take forever and are driving me nuts. The backups seem to be getting stuck midway. The disk sounds like it's spinning but the progress bar doesn't move. Also, it seems to be copying over too many files every hour, like >60000 or so (log below). I doubt that so many files get modified every hour.
I've tried everything (I could think of and find on the discussion boards) like deleting the sparsebundle, deleting the entire backup drive, playing with the backup frequency, nothing works.
Please help!!
Thanks,
DB
11/27/08 10:02:57 PM /System/Library/CoreServices/backupd7045 Starting standard backup
11/27/08 10:02:57 PM /System/Library/CoreServices/backupd7045 Network mountpoint /Volumes/TC Backup Disk not owned by backupd... remounting
11/27/08 10:02:57 PM /System/Library/CoreServices/backupd7045 Network volume mounted at: /Volumes/TC Backup Disk-1
11/27/08 10:03:07 PM /System/Library/CoreServices/backupd7045 Disk image /Volumes/TC Backup Disk-1/Dhiren's MBP_002332d43774.sparsebundle mounted at: /Volumes/Backup of Dhiren's MBP
11/27/08 10:03:07 PM /System/Library/CoreServices/backupd7045 Backing up to: /Volumes/Backup of Dhiren's MBP/Backups.backupdb
11/27/08 10:04:39 PM /System/Library/CoreServices/backupd7045 No pre-backup thinning needed: 570.5 MB requested (including padding), 426.79 GB available
11/27/08 10:14:44 PM /System/Library/CoreServices/backupd7045 _*Copied 87124 files (20.3 MB) from volume Macintosh HD.*_
11/27/08 10:14:48 PM /System/Library/CoreServices/backupd7045 No pre-backup thinning needed: 559.1 MB requested (including padding), 426.69 GB available
11/27/08 10:15:02 PM /System/Library/CoreServices/backupd7045 Unable to rebuild path cache for source item. Partial source path:
11/27/08 10:15:02 PM /System/Library/CoreServices/backupd7045 Error: (-39) SrcErr:YES Copying (null) to (null)
11/27/08 10:15:14 PM /System/Library/CoreServices/backupd7045 Copied 1067 files (10.6 MB) from volume Macintosh HD.
11/27/08 10:15:22 PM /System/Library/CoreServices/backupd7045 Starting post-backup thinning
11/27/08 10:15:22 PM /System/Library/CoreServices/backupd7045 No post-back up thinning needed: no expired backups exist
11/27/08 10:15:22 PM /System/Library/CoreServices/backupd7045 Backup completed successfully.
11/27/08 10:15:26 PM /System/Library/CoreServices/backupd7045 Ejected Time Machine disk image.
11/27/08 10:15:32 PM /System/Library/CoreServices/backupd7045 Ejected Time Machine network volume.
11/27/08 10:15:32 PM /System/Library/CoreServices/backupd7045 Ejected Time Machine network volume.

Since upgrading to Mavericks, my Time Machine is stuck on "Preparing Backup".

Since upgrading to Mavericks, every time I attempt to run a Time Machine backup, I can only get it to go as far as "Preparing Backup". I've left it like that for hours just to see if it's slow. I've also stopped and restarted Time Machine multiple times to no avail....it just gets stuck at that point. Please help.

Since upgrading to Mavericks, every time I attempt to run a Time Machine backup, I can only get it to go as far as "Preparing Backup". I've left it like that for hours just to see if it's slow. I've also stopped and restarted Time Machine multiple times to no avail....it just gets stuck at that point. Please help.

Time Machine hang- Waiting for Index to become available (100)

Hi- I'm trying to create a new Time Machine backup to a new external HD (FW800). I've formatted the drive as Mac OS Extended and told TM to use this as the backup drive. I should note that I've done TM backups in the past with a different drive which was a USB2.0 drive, but just got this FW800 and thought it would be much faster to use.
Anyway, now I'm getting the dreaded 'Waiting for Index to become available (100)' message from the TM buddy widget. This keeps repeating every few seconds. I let it run overnight and about 14 hours later, TM backed up 6G from a 150G total. As I watched the backup run, it's copying over about 1M every few minutes. How can this be? I've read through some of the forum entries and I tried placing the external drive in the Spotlight exclusion, and I also uninstalled any traces of Norton that I had installed. Nothing is making this backup go any faster.
So why in the past, has the first backup run fairly quickly, and now this is running like it will take several days to complete?
Please- any help will be greatly appreciated!! thanks.

BrianMBM wrote:
As far as the communication issue, the external drive mounts just fine, and I can access it in the finder, so I don't believe physical connection is the culprit here.
Not necessarily. A marginal connection may work, but with lots of retries, resulting in things being quite slow. It's fairly rare, but can happen.
I just don't understand why just months ago, the first TM backup started right away and now this is taking forever- Is this a change that was released in an update from Apple in how TM works?
No. In fact, they're supposed to be somewhat faster on Snow Leopard.
How can I delete every trace of previous TM backups and completely start from scratch?
You can erase the drive. If you're going to do that anyway, you might as well reformat it, with the GUID *Partition Map Scheme.* APM should work fine, but if you ever want to use it as a boot drive, GUID is preferred for an Intel Mac.
There's obviously something that's causing this indexing thing to take so long that's never happened in the past.
Try the reformat. (You'll probably have to exclude it from Spotlight again.)
Is it a multi-interface drive? If so, try connecting via USB temporarily.
If that doesn't help, try just copying a large file or folder and see how fast it is. If that's slow, too, you know it isn't Time Machine but something else associated with your F/W card, port, cable, or drive.

Time machine gets to 43.45 gb then stops

Hi, I can't get Time Machine to proceed further than 43.45gb. I've set up my external drive using Disc Utility (Partitioned as GUID as I'm on an intel imac). Time Machine Buddy gives the following log:
Starting standard backup
Backing up to: /Volumes/Untitled 1/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Event store UUIDs don't match for volume: One
Backup content size: 372.3 GB excluded items size: 19.5 MB for volume One
No pre-backup thinning needed: 446.74 GB requested (including padding), 465.29 GB available
Waiting for index to be ready (909 > 0)
CoreEndianFlipData: error -4940 returned for rsrc type open (id 128, length 12, native = no)
Currently without a backup at the moment, so any help would be much appreciated.
cheers,
Kev.

Hi,I just looked again at the Time Machine buddy log, and there's a little more information there:
Starting standard backup
Backing up to: /Volumes/Untitled 1/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Event store UUIDs don't match for volume: One
Backup content size: 372.3 GB excluded items size: 19.5 MB for volume One
No pre-backup thinning needed: 446.74 GB requested (including padding), 465.29 GB available
Waiting for index to be ready (909 > 0)
CoreEndianFlipData: error -4940 returned for rsrc type open (id 128, length 12, native = no)
Stopping backupd to allow ejection of backup destination disk!
Indexing a file failed. Returned -1120 for: /Users/freya/Library/Preferences/ByHost/com.apple.Classic.001ec203bb37.plist, /Volumes/Untitled 1/Backups.backupdb/kevin’s iMac/2009-06-28-104635.inProgress/05030F97-8383-43AB-8CF1-0158245D1BC8/One/User s/freya/Library/Preferences/ByHost/com.apple.Classic.001ec203bb37.plist
Aborting backup because indexing of file failed.
Stopping backup.
Copied 284647 files (43.5 GB) from volume One.
Copy stage failed with error:11
Any ideas?
Kev.

Time machine gets stuck on indexing

Similar Messages

Maybe you are looking for