TimeMachine 'Preparing Backup' forever

It is showing 'Preparing Backup' for about two hours before I lost patience and cancelled it. And during that two hours, there's even no disk activities or CPU usage so I guess something's broken. Has anyone had the same problem?
PS: I'm running Mavericks(upgraded at day one). The last backup was several days ago and I actually did nothing(no system update or something)

Well this is awkward. Before posting this I rebooted my machine, unplugged the external drive and it is working now...(the previous several times of reboot didn't work though, weird)

Similar Messages

"Preparing Backup" forever

So recently something went wrong with my Time Capsule. It's been working great for a few months, but now when it goes to back up, it says "preparing backup" and just spins and spins.
The backup disk appears in the left side of finder windows, with the little spinning arrows to show it's being accessed, and the icon in the top right of my screen shows the spinning clock.
But ... no backups. Just "preparing backup" forever, on both of my computers.
Any ideas?
10.5.4, the time capsule is running 7.3.2

I've had this problem twice now - and have solved it the same way both times. BL is it can be done but takes time, as described by colonia. Also got message 'disk image could not be mounted' after being stuck in 'preparing' for 30+mins.
My TC's name was >27 characters - for some reason it needs to be less, so I changed it (using Airport Utility). Then manually mounted the disk by double clicking on the sparsebundle file; don't skip the volume check - but it will take hours (took mine overnight) to check the files and volume.
I then restarted both TC and iMac and it backed up straight away. This method has worked 2 times now.
Seems both times I got into trouble was when the iMac was switched off during a backup - should be more robust I reckon. Also, the above unapproved method took me hours of trial-and-error faffing about to figure out; thought I'd left all that behind when I ditched Microsoft.
Apple need to sharpen their act up with this product.

Time Machine prepares backups forever

I have had Time Machine set up on my MacBook Pro for over a year without any problems, and all of a sudden in December, it begins by preparing the backup as it always did, but it never goes any further. I left my laptop open for 2 days and it hadn't gotten any further than preparing the backup. When I check the Time Machine settings it confirms that the last time it backed up was the beginning of December 2010. My roommate also has a Mac (both running Leopard with the latest updates), and his Time Machine is working fine. Any thoughts on what is causing this for my MBP?

Thanks for the link. I downloaded the widget and worked through a few of the error messages listed, as well as doing a restart of Time Machine (#A4). That doesn't seem to have resolved the issue. Below is a copy and paste of the widget. I understand that it's telling me that the drive is full, but it should know to make space on its own to store newer backups.
Starting standard backup
Backup requested by user
Mounted network destination using URL: afp://;AUTH=No%20User%20Authent@Jordan%20Simard's%20AirPort%20Extreme.afpovertcp.tcp.local/Time%20Machine%20Backups
Backup destination mounted at path: /Volumes/Time Machine Backups-1
Disk image /Volumes/Time Machine Backups-1/Jordan Simard’s MacBook Pro_00224135636b.sparsebundle mounted at: /Volumes/Backup of Jordan Simard’s MacBook Pro
Backing up to: /Volumes/Backup of Jordan Simard’s MacBook Pro/Backups.backupdb
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
Event store UUIDs don't match for volume: Jordan's HD
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 (906 > 0)
Waiting for index to be ready (909 > 0)
Waiting for index to be ready (909 > 0)
Waiting for index to be ready (909 > 0)

TimeMachine "Preparing backup..." Causing application memory space warning.

Every night at the office, I run a script that rsyncs files from our production server to my local machine, as a backup just in case, and also until we get a git solution setup. I would then use Time Machine, setup on a partition on the main drive, to keep incremental backups of the files.
Here's the problem though. The initial backup, goes without a hitch. However, every time I run a new rsync, and then start a backup, when I come back the next morning, I find a window has popped up saying "Your Mac OS X startup disk has no more space available for application memory". The backup itself is only 50GB on a 1TB drive (the backup partition half that). I've had activity monitor open, and it looks like whenever backup is running, it takes up at least 2GB of real memory. I don't understand how it works with the initial backup, but the moment I run an rsync and backup the up to date version, it causes these issues.
Ideas?

Thanks, Klaus. No one in that discussion thread actually explains the meaning of this warning or what might cause it. It's quite possible that my friend will never see the same warning again, but it would be good to know what triggered the warning and what should be done about it beyond restarting the computer to delete the swap files.

Time Machine "preparing backup" eternally upon wake from sleep

at a bit of a loss here...
iMac 24" (version which offered 7300GT as BTO option)
10.5.5 with all updates applied
LaCie 500 gig USB 2.0 drive directly attached.
Up until about two months ago, Time machine functioned fined. Then for some reason, the following started to happen. (no known reason, no software update related etc, that I know of)
scenario... Time Machine functions correctly EXCEPT when waking from sleep. If iMac wakes from sleep and attempts a backup immediately (e.g. more than one hour has passed), it gets stuck "preparing backup" forever. I've let it run overnight (actually as long as about 30 hours), it never stops. Finder and other programs become extremely non-responsive, machine is almost unusable. Literally, the only way out is to manually shut down external drive, with attendant warnings/errors.
What I've done:
1) deleted the time machine .plist file
2) erased, repartioned (as a single partition) external drive
3) started brand new time machine backup (takes about three hours)
At this point, time machine will backup up fine... I can force a successful backup, if I leave the machine running, at one hour it does a successful backup.
BUT, as soon as it goes to sleep, time machine is hosed.
The only workable method for using time machine is to turn the external drive and time machine off when not using it, and turn the whole shootin' match on to do what essentially becomes manual backups. These backup are fairly lengthy, as time machine also does lengthy "preparing backup", but they complete in about 30 minutes to one hour.
Given that time machine doesn't give mountable/cloneable backup, I'm probably going to go back to Carbon Copy Cloner. Still, I like the ease/regularity of Time Machine, and would use it if it works.
Any ideas?
thanks

It could be a number of things. There are lots of things that Time Machine does in order to "manage" backups -- apart from just copying data to the backup drive.
It has to manage the transition of hourly backups into daily backups and must also transition daily backups into weekly backups. Each time it does this it has to move a lot of data around. It also has to maintain indexes of everything so you can quickly find backups should you want to perform a restore.
I've also noticed that there are circumstances that can cause TM to question whether it can trust it's existing backup database... I've caught Time Machine saying that it needs to do a "deep traversal" of the backup (basically it wants to check and see what it really has) and this can take a very long time.
Still... 30 hours is an extremely long amount of time. I'm almost wondering if there's a problem with either your USB bus or your drive when they wake up such that you may be getting a huge number of retries on something that should have happened quickly.
I'd suggest you start the "Console" utility, select "All Messages" at the left, and then watch the messages being written to your log file. Not only does Time Machine log all of it's progress messages to the system.log (in more detail than you'd see in the Time Machine UI), but so do lots of other system processes. If you're getting USB bus problems the error messages would likely show up in the same log. I'm especially suspicious about non-TM related causes since you said you've already blown away your TM backups & preferences and started from scratch and you're still getting the problem.
Try re-creating your problem with the Console log messages being displayed and see if you can't see something in the log that would let you get a little closer to the root cause.
Regards,
Tim

Initial backup disrupted, and now "Preparing backup" endlessly

I just got a Time Capsule and my initial backup was interrupted by a dead battery on my laptop.
Now, this AM, it seems to spin "Preparing backup" forever. Should I just wait?

I had a similar problem and no amount of waiting (like over 24 hours) solved the problem. I initially thought that it was just taking a long time to complete a "deep traversal" because of a database inconsistency, but that was not the case. Fortunately, the solution was remarkably simple.
Open time machine preference pane.
Select the "Change disk" button.
Select your time capsule or backup disk and click the "use for backup" button.
Apparently this will cause a reindexing of the database. It will again say "preparing for backup", but if you don't get an error message in the first 3 minutes or so you should be OK.
The next backup will probably still take hours, but after that you should be back to normal. For the first backup I would suggest that you turn off any automatic log off in the security preference pane, and also uncheck Put hard disk to sleep when possible in the energy saver preference pane. After the first "Deep traversal" backup you can go back to normal setting.
This worked for me, I hope it helps you.
Reid

Forever "Preparing Backup" after power outage

I had a power outage last night that lasted a few seconds and shut down my iMac. I have an external Lacie firewire drive hooked up and I keep getting a "preparing backup" message. I decided to leave it running over-night and it remained in this state for 12 hours. I've repaired permissions and that doesn't work. Any ideas? When I check the console it says "node requires deep transversal."
Thanks

It's normal. The power outage got Time Machine's database a little confused, and it has to re-figure out what's been backed up and what hasn't.
There's a Knowledge Base article about this: http://support.apple.com/kb/TS1516
Good luck!

Deep Traversal/Preparing Backup Solution

Hi! There's a fairly common bug where TM will get stuck on "Preparing Backup" because it ostensibly needs to re-index your entire computer to see what's changed, but will never back up. I have developed, through trial and error, a way to deal with this sort of problem with minimal hassle and (in my experience) no adverse effects. I want to share it with everyone.
If TM says "Preparing backup" and your hard disk's activity light is blinking/flashing/etc., LEAVE IT ALONE. It may take some time, but it's actually doing something.
If TM says "Preparing backup" but your hard disk's activity light is NOT blinking/flashing/etc. (i.e. staying on), then it will almost certainly never back up if left to its own devices. (No pun intended.) So:
1. Go to the Time Machine menu (activate it with System Preferences) and select "Stop Backup". It will now stop the backup forever instead of prepare it, but you've given TM some warning. Note that the System Preference panel and the menu will sometimes conflict; that is, the menu will say "Stopping Backup" and the SP will say "Preparing Backup," or vice versa. Ignore that, because I've also found that System Preferences may not close properly while TM is in an endless loop.
2. Disconnect/turn off your backup drive long enough for TM to realize that it's gone. The volume will disappear from the desktop, a "Device Removal" warning will be displayed (ignore), and the TM menu icon will change to an exclamation mark.
3. Reconnect the drive. TM will now Prepare, but only briefly, and then proceed to back up normally.
Also, try to keep the drive attached and on whenever your computer is on, although this might be difficult for laptop users. I hope this helps someone!

I ended up doing this as well. TM worked great for the first 2 weeks and then I started getting the dreaded "preparing..." that would go on for hours. I turned TM off but that didn't help, I couldn't unmount the firewire drive because OS X thinks it's being used, so I just unplugged the drive and plugged it back in. Backups work for about a day and half after doing that.
I just found out in another thread that there's a firmware update for my WD drive that will allow it to work with Leopard. I'm hoping that's the problem, I'll see tonight.

TC Prerparing Backup FOREVER

well not really forever, but it has been 3 days since the system is "Preparing Backup" and seems to be stuck at 99%.... what to do? thanks guys

Try go to the "Go" menu in Finder - and select "Connect to server" (CMD + K) - and enter the name/adress - or better for most choose "Browse".
Then your Time Capsule should hopefully show up.
Select it, to make the connection to the TM. This might help, but not always. However, in some situations it's really a matter of getting the first connection to work.

"Preparing Backup..."

Time machine says "Preparing Backup..." forever. Doesn't back up. Since three days ago. Using MBP only, OWC 750GB FW 800 hard drive. The thing is thinking but not backing up.

Here is what I have. Haven't been able to backup since June 25. All it does is say "Preparing backup." I did install OS X on the backup drive to use as a startup volume in case of emergency, but not sure why that would make a difference.
7/6/08 8:26:01 AM /System/Library/CoreServices/backupd[125] Waiting for index to be ready (915 > 0)
7/6/08 8:26:31 AM /System/Library/CoreServices/backupd[125] Waiting for index to be ready (915 > 0)
7/6/08 8:27:01 AM /System/Library/CoreServices/backupd[125] Waiting for index to be ready (915 > 0)
7/6/08 8:27:31 AM /System/Library/CoreServices/backupd[125] Waiting for index to be ready (915 > 0)
7/6/08 8:28:01 AM /System/Library/CoreServices/backupd[125] Waiting for index to be ready (915 > 0)
7/6/08 2:51:39 PM /System/Library/CoreServices/backupd[228] Starting standard backup
7/6/08 2:51:49 PM /System/Library/CoreServices/backupd[228] Backing up to: /Volumes/FreeAgent Drive/Backups.backupdb
7/6/08 2:51:50 PM /System/Library/CoreServices/backupd[228] Event store UUIDs don't match for volume: Mac Attack
7/6/08 2:51:50 PM /System/Library/CoreServices/backupd[228] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
7/6/08 3:08:02 PM /System/Library/CoreServices/backupd[228] No pre-backup thinning needed: 1.04 GB requested (including padding), 427.33 GB available
7/6/08 3:18:47 PM /System/Library/CoreServices/backupd[228] Error: (-36) copying /Users/kim/Library/Preferences/Microsoft/com.microsoft.Office.prefs.plist to /Volumes/FreeAgent Drive/Backups.backupdb/Mark Rougeux’s iMac/2008-06-28-080130.inProgress/E44DB91E-D2F2-4272-BED5-1B6B4AA1E376/Mac Attack/Users/kim/Library/Preferences/Microsoft
7/6/08 3:18:47 PM /System/Library/CoreServices/backupd[228] Stopping backup.
7/6/08 3:18:47 PM /System/Library/CoreServices/backupd[228] Error: (-8062) copying /Users/kim/Library/Preferences/Microsoft/com.microsoft.Office.prefs.plist to /Volumes/FreeAgent Drive/Backups.backupdb/Mark Rougeux’s iMac/2008-06-28-080130.inProgress/E44DB91E-D2F2-4272-BED5-1B6B4AA1E376/Mac Attack/Users/kim/Library/Preferences/Microsoft
7/6/08 3:18:48 PM /System/Library/CoreServices/backupd[228] Copied 40323 files (710.7 MB) from volume Mac Attack.
7/6/08 3:18:48 PM /System/Library/CoreServices/backupd[228] Copy stage failed with error:11
7/6/08 3:18:54 PM /System/Library/CoreServices/backupd[228] Backup failed with error: 11
7/6/08 3:18:54 PM /System/Library/CoreServices/backupd[228] 11 days since last backup
7/6/08 5:33:25 PM /System/Library/CoreServices/backupd[228] Starting standard backup
7/6/08 5:33:29 PM /System/Library/CoreServices/backupd[228] Volume at path /Volumes/FreeAgent Drive does not appear to be the correct backup volume for this computer. (Cookies do not match)
7/6/08 5:33:34 PM /System/Library/CoreServices/backupd[228] Backup failed with error: 18
7/6/08 6:07:51 PM /System/Library/CoreServices/backupd[404] Starting standard backup
7/6/08 6:07:55 PM /System/Library/CoreServices/backupd[404] Volume at path /Volumes/FreeAgent Drive does not appear to be the correct backup volume for this computer. (Cookies do not match)
7/6/08 6:08:00 PM /System/Library/CoreServices/backupd[404] Backup failed with error: 18
7/6/08 6:16:01 PM /System/Library/CoreServices/backupd[436] Starting standard backup
7/6/08 6:16:10 PM /System/Library/CoreServices/backupd[436] Volume at path /Volumes/FreeAgent Drive does not appear to be the correct backup volume for this computer. (Cookies do not match)
7/6/08 6:16:15 PM /System/Library/CoreServices/backupd[436] Backup failed with error: 18
7/6/08 8:36:00 PM /System/Library/CoreServices/backupd[543] Starting standard backup
7/6/08 8:36:04 PM /System/Library/CoreServices/backupd[543] Volume at path /Volumes/FreeAgent Drive does not appear to be the correct backup volume for this computer. (Cookies do not match)
7/6/08 8:36:09 PM /System/Library/CoreServices/backupd[543] Backup failed with error: 18
7/6/08 8:56:31 PM /System/Library/CoreServices/backupd[593] Starting standard backup
7/6/08 9:14:23 PM /System/Library/CoreServices/backupd[593] Volume at path /Volumes/FreeAgent Drive does not appear to be the correct backup volume for this computer. (Cookies do not match)
7/6/08 9:14:28 PM /System/Library/CoreServices/backupd[593] Backup failed with error: 18
7/6/08 9:17:41 PM /System/Library/CoreServices/backupd[630] Starting standard backup
7/6/08 9:17:41 PM /System/Library/CoreServices/backupd[630] Backing up to: /Volumes/FreeAgent Drive/Backups.backupdb
7/6/08 9:17:42 PM /System/Library/CoreServices/backupd[630] Event store UUIDs don't match for volume: Mac Attack
7/6/08 9:17:42 PM /System/Library/CoreServices/backupd[630] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|

Time Machine stuck on Preparing backup

Since upgrading to Mavericks a couple of months ago, one of my Mac Mini Servers can't backup using Time Machine. (I have another similar server with the same software versions but running different services, that doesn't have this problem). Both are currently running OSX 10.9.5 and Server 3.2.2 with all updates applied.
The problem machine gets stuck indefinitely on "Preparing backup". I've tried leaving it for several days, but it's not actually doing anything – the backupd process is on 0% CPU utilisation. It doesn't write any data to the backup drive – the drive is still empty since it was last reformatted.
It was working fine on Mountain Lion Server, before the upgrade to Mavericks.
So far, I've tried:
• Rebooting
• Reformatting the external USB backup drive and replacing it with another drive
• Verifying the startup drive with Disk Utility
• Deleting com.apple.TimeMachine.plist
• Excluding the startup drive from Spotlight searches
I've tried most of the above several times over the past few weeks to no avail.

I have had this same issue just appear although I have been running Mavericks and Server for almost a year now. I backup across 3 drives, 2 of which are rotated on a weekly basis. I discovered this morning that the non-rotating disk has not backed up in several weeks and one of the rotating disks has not backed up during the same period of time. Interestingly this week's rotating backup drive it appears to be working perfectly fine. The non-rotating disk is now stuck on preparing backup. I have included a portion of my log below. One thing I have noticed is that Spotlight seems to be re-indexing my server with little to no progress being made.
10/22/14 9:26:54.494 AM collabd[368]: [CSConnectionPool.m:196 1067f000 +6351ms] Could not open a connection to Postgres. Please make sure it is running and has the correct access.
10/22/14 9:26:54.559 AM collabd[368]: [CSServiceDispatcher.m:261 1067f000 +0ms] Caught exception "Connection to DB failed" [CSDatabaseError] executing [http]Request{AuthService.enterMagicalAuthRealm()}:
0   CoreFoundation                      0x00007fff84f2e25c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff85715e75 objc_exception_throw + 43
2   CSService                           0x000000010cecd76d -[CSConnectionPool openConnection] + 3309
3   CSService                           0x000000010cece13a -[CSConnectionPool currentConnection] + 98
4   CSService                           0x000000010cf4d839 -[CSAuthService unauthenticatedSession] + 82
5   CSService                           0x000000010cf4de13 -[CSAuthService currentOrNewSession] + 154
6   CSService                           0x000000010cf50c91 -[CSAuthService enterMagicalAuthRealm] + 51
7   CoreFoundation                      0x00007fff84e199ac __invoking___ + 140
8   CoreFoundation                      0x00007fff84e19814 -[NSInvocation invoke] + 308
9   CSService                           0x000000010cec9055 -[CSServiceDispatcher executeRequest:asPartOfBatch:usingServiceImpl:] + 4578
10 CSService                           0x000000010cec9548 -[CSServiceDispatcher executeRequest:] + 120
11 CSService                           0x000000010cf3e218 +[CSServiceDispatchHTTPRouter routeServiceRequest:response:] + 1135
12 CSService                           0x000000010cecfacf __21-[CSServiceBase init]_block_invoke_6 + 48
13 CSService                           0x000000010cf3b2aa __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
14 CSService                           0x000000010cf3e7b4 -[CSHTTPBackgroundResponse bounce:] + 286
15 Foundation                          0x00007fff8dad9dfb __NSThread__main__ + 1318
16 libsystem_pthread.dylib             0x00007fff8b47e899 _pthread_body + 138
17 libsystem_pthread.dylib             0x00007fff8b47e72a _pthread_struct_init + 0
18 libsystem_pthread.dylib             0x00007fff8b482fc9 thread_start + 13
10/22/14 9:26:57.369 AM serveradmin[83827]: [WikiRequestHandler.m:74 754af310 +2929ms] Error getting a session GUID: Connection to DB failed
10/22/14 9:26:57.412 AM collabd[368]: [CSConnectionPool.m:196 1067f000 +2821ms] Could not open a connection to Postgres. Please make sure it is running and has the correct access.
10/22/14 9:26:57.474 AM collabd[368]: [CSServiceDispatcher.m:261 1067f000 +0ms] Caught exception "Connection to DB failed" [CSDatabaseError] executing [http]Request{SettingsService.globalSettingForKey:(projectCreators)}:
0   CoreFoundation                      0x00007fff84f2e25c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff85715e75 objc_exception_throw + 43
2   CSService                           0x000000010cecd76d -[CSConnectionPool openConnection] + 3309
3   CSService                           0x000000010cece13a -[CSConnectionPool currentConnection] + 98
4   CSService                           0x000000010ceeb218 -[CSSettingsService globalSettingForKey:] + 101
5   CoreFoundation                      0x00007fff84e199ac __invoking___ + 140
6   CoreFoundation                      0x00007fff84e19814 -[NSInvocation invoke] + 308
7   CSService                           0x000000010cec9055 -[CSServiceDispatcher executeRequest:asPartOfBatch:usingServiceImpl:] + 4578
8   CSService                           0x000000010cec9548 -[CSServiceDispatcher executeRequest:] + 120
9   CSService                           0x000000010cf3e218 +[CSServiceDispatchHTTPRouter routeServiceRequest:response:] + 1135
10 CSService                           0x000000010cecfacf __21-[CSServiceBase init]_block_invoke_6 + 48
11 CSService                           0x000000010cf3b2aa __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
12 CSService                           0x000000010cf3e7b4 -[CSHTTPBackgroundResponse bounce:] + 286
13 Foundation                          0x00007fff8dad9dfb __NSThread__main__ + 1318
14 libsystem_pthread.dylib             0x00007fff8b47e899 _pthread_body + 138
15 libsystem_pthread.dylib             0x00007fff8b47e72a _pthread_struct_init + 0
16 libsystem_pthread.dylib             0x00007fff8b482fc9 thread_start + 13
10/22/14 9:26:57.475 AM serveradmin[83827]: [WikiRequestHandler.m:300 754af310 +2ms] Could not get project creators from collabd, Connection to DB failed
10/22/14 9:26:57.996 AM collabd[368]: [CSConnectionPool.m:196 1067f000 +505ms] Could not open a connection to Postgres. Please make sure it is running and has the correct access.
10/22/14 9:26:58.026 AM collabd[368]: [CSServiceDispatcher.m:261 1067f000 +0ms] Caught exception "Connection to DB failed" [CSDatabaseError] executing [http]Request{AuthService.enterMagicalAuthRealm()}:
0   CoreFoundation                      0x00007fff84f2e25c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff85715e75 objc_exception_throw + 43
2   CSService                           0x000000010cecd76d -[CSConnectionPool openConnection] + 3309
3   CSService                           0x000000010cece13a -[CSConnectionPool currentConnection] + 98
4   CSService                           0x000000010cf4d839 -[CSAuthService unauthenticatedSession] + 82
5   CSService                           0x000000010cf4de13 -[CSAuthService currentOrNewSession] + 154
6   CSService                           0x000000010cf50c91 -[CSAuthService enterMagicalAuthRealm] + 51
7   CoreFoundation                      0x00007fff84e199ac __invoking___ + 140
8   CoreFoundation                      0x00007fff84e19814 -[NSInvocation invoke] + 308
9   CSService                           0x000000010cec9055 -[CSServiceDispatcher executeRequest:asPartOfBatch:usingServiceImpl:] + 4578
10 CSService                           0x000000010cec9548 -[CSServiceDispatcher executeRequest:] + 120
11 CSService                           0x000000010cf3e218 +[CSServiceDispatchHTTPRouter routeServiceRequest:response:] + 1135
12 CSService                           0x000000010cecfacf __21-[CSServiceBase init]_block_invoke_6 + 48
13 CSService                           0x000000010cf3b2aa __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
14 CSService                           0x000000010cf3e7b4 -[CSHTTPBackgroundResponse bounce:] + 286
15 Foundation                          0x00007fff8dad9dfb __NSThread__main__ + 1318
16 libsystem_pthread.dylib             0x00007fff8b47e899 _pthread_body + 138
17 libsystem_pthread.dylib             0x00007fff8b47e72a _pthread_struct_init + 0
18 libsystem_pthread.dylib             0x00007fff8b482fc9 thread_start + 13
10/22/14 9:26:58.249 AM com.apple.launchd[1]: (com.apple.collabd.notifications[83832]) Exited with code: 1
10/22/14 9:26:58.249 AM com.apple.launchd[1]: (com.apple.collabd.notifications) Throttling respawn: Will start in 10 seconds
10/22/14 9:26:58.264 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres[83837]) Exited with code: 1
10/22/14 9:26:58.264 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres) Throttling respawn: Will start in 10 seconds
10/22/14 9:27:08.875 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres[83859]) Exited with code: 1
10/22/14 9:27:08.875 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres) Throttling respawn: Will start in 10 seconds
10/22/14 9:27:09.371 AM collabd[368]: [CSConnectionPool.m:196 1067f000 +11301ms] Could not open a connection to Postgres. Please make sure it is running and has the correct access.
10/22/14 9:27:09.390 AM collabd[368]: [CSServiceDispatcher.m:261 1067f000 +0ms] Caught exception "Connection to DB failed" [CSDatabaseError] executing [http]Request{AuthService.enterMagicalAuthRealm()}:
0   CoreFoundation                      0x00007fff84f2e25c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff85715e75 objc_exception_throw + 43
2   CSService                           0x000000010cecd76d -[CSConnectionPool openConnection] + 3309
3   CSService                           0x000000010cece13a -[CSConnectionPool currentConnection] + 98
4   CSService                           0x000000010cf4d839 -[CSAuthService unauthenticatedSession] + 82
5   CSService                           0x000000010cf4de13 -[CSAuthService currentOrNewSession] + 154
6   CSService                           0x000000010cf50c91 -[CSAuthService enterMagicalAuthRealm] + 51
7   CoreFoundation                      0x00007fff84e199ac __invoking___ + 140
8   CoreFoundation                      0x00007fff84e19814 -[NSInvocation invoke] + 308
9   CSService                           0x000000010cec9055 -[CSServiceDispatcher executeRequest:asPartOfBatch:usingServiceImpl:] + 4578
10 CSService                           0x000000010cec9548 -[CSServiceDispatcher executeRequest:] + 120
11 CSService                           0x000000010cf3e218 +[CSServiceDispatchHTTPRouter routeServiceRequest:response:] + 1135
12 CSService                           0x000000010cecfacf __21-[CSServiceBase init]_block_invoke_6 + 48
13 CSService                           0x000000010cf3b2aa __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
14 CSService                           0x000000010cf3e7b4 -[CSHTTPBackgroundResponse bounce:] + 286
15 Foundation                          0x00007fff8dad9dfb __NSThread__main__ + 1318
16 libsystem_pthread.dylib             0x00007fff8b47e899 _pthread_body + 138
17 libsystem_pthread.dylib             0x00007fff8b47e72a _pthread_struct_init + 0
18 libsystem_pthread.dylib             0x00007fff8b482fc9 thread_start + 13
10/22/14 9:27:09.611 AM com.apple.launchd[1]: (com.apple.collabd.notifications[83858]) Exited with code: 1
10/22/14 9:27:09.611 AM com.apple.launchd[1]: (com.apple.collabd.notifications) Throttling respawn: Will start in 9 seconds
10/22/14 9:27:13.180 AM xpcd[599]: restored permissions (100600 -> 100700) on /Users/administrator/Library/Containers/com.apple.TextEdit/Container.plist
10/22/14 9:27:20.459 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres[83881]) Exited with code: 1
10/22/14 9:27:20.459 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres) Throttling respawn: Will start in 9 seconds
10/22/14 9:27:22.698 AM collabd[368]: [CSConnectionPool.m:196 1067f000 +13265ms] Could not open a connection to Postgres. Please make sure it is running and has the correct access.
10/22/14 9:27:22.993 AM collabd[368]: [CSServiceDispatcher.m:261 1067f000 +0ms] Caught exception "Connection to DB failed" [CSDatabaseError] executing [http]Request{AuthService.enterMagicalAuthRealm()}:
0   CoreFoundation                      0x00007fff84f2e25c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff85715e75 objc_exception_throw + 43
2   CSService                           0x000000010cecd76d -[CSConnectionPool openConnection] + 3309
3   CSService                           0x000000010cece13a -[CSConnectionPool currentConnection] + 98
4   CSService                           0x000000010cf4d839 -[CSAuthService unauthenticatedSession] + 82
5   CSService                           0x000000010cf4de13 -[CSAuthService currentOrNewSession] + 154
6   CSService                           0x000000010cf50c91 -[CSAuthService enterMagicalAuthRealm] + 51
7   CoreFoundation                      0x00007fff84e199ac __invoking___ + 140
8   CoreFoundation                      0x00007fff84e19814 -[NSInvocation invoke] + 308
9   CSService                           0x000000010cec9055 -[CSServiceDispatcher executeRequest:asPartOfBatch:usingServiceImpl:] + 4578
10 CSService                           0x000000010cec9548 -[CSServiceDispatcher executeRequest:] + 120
11 CSService                           0x000000010cf3e218 +[CSServiceDispatchHTTPRouter routeServiceRequest:response:] + 1135
12 CSService                           0x000000010cecfacf __21-[CSServiceBase init]_block_invoke_6 + 48
13 CSService                           0x000000010cf3b2aa __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
14 CSService                           0x000000010cf3e7b4 -[CSHTTPBackgroundResponse bounce:] + 286
15 Foundation                          0x00007fff8dad9dfb __NSThread__main__ + 1318
16 libsystem_pthread.dylib             0x00007fff8b47e899 _pthread_body + 138
17 libsystem_pthread.dylib             0x00007fff8b47e72a _pthread_struct_init + 0
18 libsystem_pthread.dylib             0x00007fff8b482fc9 thread_start + 13
10/22/14 9:27:23.216 AM com.apple.launchd[1]: (com.apple.collabd.notifications[83880]) Exited with code: 1
10/22/14 9:27:23.217 AM com.apple.launchd[1]: (com.apple.collabd.notifications) Throttling respawn: Will start in 6 seconds
10/22/14 9:27:29.939 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres[83896]) Exited with code: 1
10/22/14 9:27:29.939 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres) Throttling respawn: Will start in 10 seconds
10/22/14 9:27:30.019 AM collabd[368]: [CSConnectionPool.m:196 1067f000 +6884ms] Could not open a connection to Postgres. Please make sure it is running and has the correct access.
10/22/14 9:27:30.125 AM collabd[368]: [CSServiceDispatcher.m:261 1067f000 +0ms] Caught exception "Connection to DB failed" [CSDatabaseError] executing [http]Request{AuthService.enterMagicalAuthRealm()}:
0   CoreFoundation                      0x00007fff84f2e25c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff85715e75 objc_exception_throw + 43
2   CSService                           0x000000010cecd76d -[CSConnectionPool openConnection] + 3309
3   CSService                           0x000000010cece13a -[CSConnectionPool currentConnection] + 98
4   CSService                           0x000000010cf4d839 -[CSAuthService unauthenticatedSession] + 82
5   CSService                           0x000000010cf4de13 -[CSAuthService currentOrNewSession] + 154
6   CSService                           0x000000010cf50c91 -[CSAuthService enterMagicalAuthRealm] + 51
7   CoreFoundation                      0x00007fff84e199ac __invoking___ + 140
8   CoreFoundation                      0x00007fff84e19814 -[NSInvocation invoke] + 308
9   CSService                           0x000000010cec9055 -[CSServiceDispatcher executeRequest:asPartOfBatch:usingServiceImpl:] + 4578
10 CSService                           0x000000010cec9548 -[CSServiceDispatcher executeRequest:] + 120
11 CSService                           0x000000010cf3e218 +[CSServiceDispatchHTTPRouter routeServiceRequest:response:] + 1135
12 CSService                           0x000000010cecfacf __21-[CSServiceBase init]_block_invoke_6 + 48
13 CSService                           0x000000010cf3b2aa __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
14 CSService                           0x000000010cf3e7b4 -[CSHTTPBackgroundResponse bounce:] + 286
15 Foundation                          0x00007fff8dad9dfb __NSThread__main__ + 1318
16 libsystem_pthread.dylib             0x00007fff8b47e899 _pthread_body + 138
17 libsystem_pthread.dylib             0x00007fff8b47e72a _pthread_struct_init + 0
18 libsystem_pthread.dylib             0x00007fff8b482fc9 thread_start + 13
10/22/14 9:27:30.358 AM com.apple.launchd[1]: (com.apple.collabd.notifications[83895]) Exited with code: 1
10/22/14 9:27:30.358 AM com.apple.launchd[1]: (com.apple.collabd.notifications) Throttling respawn: Will start in 9 seconds
10/22/14 9:27:32.166 AM com.apple.IconServicesAgent[640]: main Failed to composit image for binding VariantBinding [0x3b5] flags: 0x8 binding: FileInfoBinding [0x137] - extension: png, UTI: public.png, fileType: ????.
10/22/14 9:27:32.325 AM quicklookd[83883]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x203] flags: 0x8 binding: FileInfoBinding [0x103] - extension: png, UTI: public.png, fileType: ???? request size:16 scale: 1
10/22/14 9:27:34.728 AM com.apple.appkit.xpc.openAndSavePanelService[83868]: CGSGetWindowTransformAtPlacement
10/22/14 9:27:34.728 AM com.apple.appkit.xpc.openAndSavePanelService[83868]: CGSTranslatePointForWindow
10/22/14 9:27:34.728 AM com.apple.appkit.xpc.openAndSavePanelService[83868]: CGSGetWindowBounds
10/22/14 9:27:34.758 AM com.apple.appkit.xpc.openAndSavePanelService[83868]: Bogus event received by listener connection:
<error: 0x7fff73e14b50> { count = 1, contents =
"XPCErrorDescription" => <string: 0x7fff73e14e60> { length = 18, contents = "Connection invalid" }
10/22/14 9:27:40.275 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres[83915]) Exited with code: 1
10/22/14 9:27:40.275 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres) Throttling respawn: Will start in 10 seconds
10/22/14 9:27:40.312 AM collabd[368]: [CSConnectionPool.m:196 1067f000 +10055ms] Could not open a connection to Postgres. Please make sure it is running and has the correct access.
10/22/14 9:27:40.328 AM collabd[368]: [CSServiceDispatcher.m:261 1067f000 +0ms] Caught exception "Connection to DB failed" [CSDatabaseError] executing [http]Request{AuthService.enterMagicalAuthRealm()}:
0   CoreFoundation                      0x00007fff84f2e25c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff85715e75 objc_exception_throw + 43
2   CSService                           0x000000010cecd76d -[CSConnectionPool openConnection] + 3309
3   CSService                           0x000000010cece13a -[CSConnectionPool currentConnection] + 98
4   CSService                           0x000000010cf4d839 -[CSAuthService unauthenticatedSession] + 82
5   CSService                           0x000000010cf4de13 -[CSAuthService currentOrNewSession] + 154
6   CSService                           0x000000010cf50c91 -[CSAuthService enterMagicalAuthRealm] + 51
7   CoreFoundation                      0x00007fff84e199ac __invoking___ + 140
8   CoreFoundation                      0x00007fff84e19814 -[NSInvocation invoke] + 308
9   CSService                           0x000000010cec9055 -[CSServiceDispatcher executeRequest:asPartOfBatch:usingServiceImpl:] + 4578
10 CSService                           0x000000010cec9548 -[CSServiceDispatcher executeRequest:] + 120
11 CSService                           0x000000010cf3e218 +[CSServiceDispatchHTTPRouter routeServiceRequest:response:] + 1135
12 CSService                           0x000000010cecfacf __21-[CSServiceBase init]_block_invoke_6 + 48
13 CSService                           0x000000010cf3b2aa __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
14 CSService                           0x000000010cf3e7b4 -[CSHTTPBackgroundResponse bounce:] + 286
15 Foundation                          0x00007fff8dad9dfb __NSThread__main__ + 1318
16 libsystem_pthread.dylib             0x00007fff8b47e899 _pthread_body + 138
17 libsystem_pthread.dylib             0x00007fff8b47e72a _pthread_struct_init + 0
18 libsystem_pthread.dylib             0x00007fff8b482fc9 thread_start + 13
10/22/14 9:27:40.547 AM com.apple.launchd[1]: (com.apple.collabd.notifications[83913]) Exited with code: 1
10/22/14 9:27:40.547 AM com.apple.launchd[1]: (com.apple.collabd.notifications) Throttling respawn: Will start in 9 seconds
10/22/14 9:27:50.276 AM collabd[368]: [CSConnectionPool.m:196 1067f000 +9887ms] Could not open a connection to Postgres. Please make sure it is running and has the correct access.
10/22/14 9:27:50.298 AM collabd[368]: [CSServiceDispatcher.m:261 1067f000 +0ms] Caught exception "Connection to DB failed" [CSDatabaseError] executing [http]Request{AuthService.enterMagicalAuthRealm()}:
0   CoreFoundation                      0x00007fff84f2e25c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff85715e75 objc_exception_throw + 43
2   CSService                           0x000000010cecd76d -[CSConnectionPool openConnection] + 3309
3   CSService                           0x000000010cece13a -[CSConnectionPool currentConnection] + 98
4   CSService                           0x000000010cf4d839 -[CSAuthService unauthenticatedSession] + 82
5   CSService                           0x000000010cf4de13 -[CSAuthService currentOrNewSession] + 154
6   CSService                           0x000000010cf50c91 -[CSAuthService enterMagicalAuthRealm] + 51
7   CoreFoundation                      0x00007fff84e199ac __invoking___ + 140
8   CoreFoundation                      0x00007fff84e19814 -[NSInvocation invoke] + 308
9   CSService                           0x000000010cec9055 -[CSServiceDispatcher executeRequest:asPartOfBatch:usingServiceImpl:] + 4578
10 CSService                           0x000000010cec9548 -[CSServiceDispatcher executeRequest:] + 120
11 CSService                           0x000000010cf3e218 +[CSServiceDispatchHTTPRouter routeServiceRequest:response:] + 1135
12 CSService                           0x000000010cecfacf __21-[CSServiceBase init]_block_invoke_6 + 48
13 CSService                           0x000000010cf3b2aa __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
14 CSService                           0x000000010cf3e7b4 -[CSHTTPBackgroundResponse bounce:] + 286
15 Foundation                          0x00007fff8dad9dfb __NSThread__main__ + 1318
16 libsystem_pthread.dylib             0x00007fff8b47e899 _pthread_body + 138
17 libsystem_pthread.dylib             0x00007fff8b47e72a _pthread_struct_init + 0
18 libsystem_pthread.dylib             0x00007fff8b482fc9 thread_start + 13
10/22/14 9:27:50.507 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres[83934]) Exited with code: 1
10/22/14 9:27:50.507 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres) Throttling respawn: Will start in 10 seconds
10/22/14 9:27:50.528 AM com.apple.launchd[1]: (com.apple.collabd.notifications[83932]) Exited with code: 1
10/22/14 9:27:50.528 AM com.apple.launchd[1]: (com.apple.collabd.notifications) Throttling respawn: Will start in 10 seconds
10/22/14 9:28:01.077 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres[83949]) Exited with code: 1
10/22/14 9:28:01.077 AM com.apple.launchd[1]: (com.apple.DeviceManagement.postgres) Throttling respawn: Will start in 10 seconds
10/22/14 9:28:01.827 AM collabd[368]: [CSConnectionPool.m:196 1049d000 +11486ms] Could not open a connection to Postgres. Please make sure it is running and has the correct access.
10/22/14 9:28:01.969 AM collabd[368]: [CSServiceDispatcher.m:261 1049d000 +0ms] Caught exception "Connection to DB failed" [CSDatabaseError] executing [http]Request{AuthService.enterMagicalAuthRealm()}:
0   CoreFoundation                      0x00007fff84f2e25c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff85715e75 objc_exception_throw + 43
2   CSService                           0x000000010cecd76d -[CSConnectionPool openConnection] + 3309
3   CSService                           0x000000010cece13a -[CSConnectionPool currentConnection] + 98
4   CSService                           0x000000010cf4d839 -[CSAuthService unauthenticatedSession] + 82
5   CSService                           0x000000010cf4de13 -[CSAuthService currentOrNewSession] + 154
6   CSService                           0x000000010cf50c91 -[CSAuthService enterMagicalAuthRealm] + 51
7   CoreFoundation                      0x00007fff84e199ac __invoking___ + 140
8   CoreFoundation                      0x00007fff84e19814 -[NSInvocation invoke] + 308
9   CSService                           0x000000010cec9055 -[CSServiceDispatcher executeRequest:asPartOfBatch:usingServiceImpl:] + 4578
10 CSService                           0x000000010cec9548 -[CSServiceDispatcher executeRequest:] + 120
11 CSService                           0x000000010cf3e218 +[CSServiceDispatchHTTPRouter routeServiceRequest:response:] + 1135
12 CSService                           0x000000010cecfacf __21-[CSServiceBase init]_block_invoke_6 + 48
13 CSService                           0x000000010cf3b2aa __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
14 CSService                           0x000000010cf3e7b4 -[CSHTTPBackgroundResponse bounce:] + 286
15 Foundation                          0x00007fff8dad9dfb __NSThread__main__ + 1318
16 libsystem_pthread.dylib             0x00007fff8b47e899 _pthread_body + 138
17 libsystem_pthread.dylib             0x00007fff8b47e72a _pthread_struct_init + 0
18 libsystem_pthread.dylib             0x00007fff8b482fc9 thread_start + 13
10/22/14 9:28:02.194 AM com.apple.launchd[1]: (com.apple.collabd.notifications[83950]) Exited with code: 1
10/22/14 9:28:02.194 AM com.apple.launchd[1]: (com.apple.collabd.notifications) Throttling respawn: Will start in 9 seconds

Constantly preparing backup (every backup)

i had a few kernal panics... so i understood the first preparing backup after each -- and they took up to 48 hrs to finish that and then complete the back up. but after the last one -- it completed a HUGE back up (26 gb) because it seems to start from scratch every time... then a minute later backed up again - 1.1 gb... no idea why it did - but that one was normal. then i shut down for the night normally and no issues the next day at startup (no external drives, no mozy ..etc), today i told it to start backup -- and its back to preparing backup... why? i am on wireless so this constant preparing is basically hogging my bandwidth back to the server (since the backup is taking a good amount of bandwidth).. it did say last backup 4:55pm yesterday when i started.. so it KNOWs there is a good backup already...
excluded the time machine drive from anti virus (though i dont think it was scanning it in the first place), turned off hard drive sleep, and antivirus after that... there have been no significant changes on my mac -- at most it should be a 1 gb or less b/u.
(i cant find this console app mentioned in other threads to see the system log...)
any ideas ??
i am going to upgrade to SL - but i am awaiting all my apps to be SL updated... so for now i am stuck at 10.5.8
thanks
ml

thanks for your help
ok i did read that post but didn't want to install another widget...
in answer the the large backups - - now it has inexplicably reduced to 23.1 gb - which of course is still to large..
- vmware fusion is excluded from backups (checked still is)
- entourage hasn't been opened or changed in 2 weeks
- don't have parallels, thunderbird, or FileVault
- no recent OSX update
- no recent exclusion removals
- no major folder renames and only a few small file deleted (ie pdf's etc)
(i dont use my local drive for this stuff so there is little file change from a document perspective)
here are the results
I think its interesting that TimeMachine NO longer tells me when its removing an older backup -- nice... i see its in the log though... i have no idea what the last error message means..
as you can see - thanks to these repeated large backups i have only a few weeks of back ups left - because it keeps deleting the older to make room -- i used to have several months worth... the drive has a massive amount of space on it (i believe we earmarked 4 tb for total of our 2 laptops.) whats worse is it requested more than it needed in the end -- and deleted a backup that - now that it's shrunk it to 23.1 gb - it didn't need to delete...
Starting standard backup
Backup destination alias resolved to path: /Volumes/TIMEMACHINE-5
Disk image /Volumes/TIMEMACHINE-5/MyMac_00254bbb8f22.sparsebundle mounted at: /Volumes/MLTIME
Backing up to: /Volumes/MLTIME/Backups.backupdb
Starting pre-backup thinning: 28.66 GB requested (including padding), 23.51 GB available
No expired backups exist - deleting oldest backups to make room
Deleted backup /Volumes/MLTIME/Backups.backupdb/Macintosh/2009-09-24-002527: 70.39 GB now available
Pre-backup thinning completed successfully: 1 backups were deleted
Backup date range was shortened: oldest backup is now Sep 25, 2009
Bulk setting Spotlight attributes failed.
Bulk setting Spotlight attributes failed.
===================================================
I installed timetracker too
but that one loads up my husbands backups for its list of backups -- not mine... (very strange)
after that the time machine drive assoc to his macbook is mounted... (mine remained there as well)

Time Machine stuck on preparing backup with in turn breaks internet connectivity.

Hi all!
I recently started using Time Machine (on a 1TB USB 2.0 external hard drive) on my MBP (Early 2011, 13") and I've noticed that it constantly gets stuck on the "Preparing backup" stage, which can only be unstuck by pulling the drive or hard rebooting the computer (otherwise it gets stuck on the gray post-logout screen forever). What's more interesting is that while Time Machine is stuck I am unable to use any of my browsers because DNS resolution fails outright (although I can still visit IP addresses and perform manually DNS queries and start SSH sessions in Terminal.app). If I pull the drive or reboot the computer, my internet connectivity is restored. As a relatively new Mac user this behavior is quite puzzling; has anybody else encountered this type of problem?
Thanks!
Max

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of this exercise is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login. Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. The instructions provided by Apple are as follows:
Be sure your Mac is shut down.
Press the power button.
Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including your login items.
Launch the application(s) and test. Same problem(s)?
After testing, reboot as usual (i.e., not in safe mode.)

"Preparing Backup" mode

My Time Machine is constantly spinning on "Preparing Backup" mode and never completed a single back up at all couple of days ago?
I can, however still enter time machine to retrieve the old backups prior that day.
What's is going on?
Please help!
Thanks.

Welcome to the discussions!
Try resetting Time Machine as follows:
Open Hard Drive > Library > Preferences and delete the "com.apple.TimeMachine.plist" file and restart your computer.
Now open System Preferences and click on Time Machine to set it up again. Your backups should start again, but Time Machine may be in a "preparing" mode for some time since backups have not occurred for the past few days. Leave it alone and things should get back to normal.

Upgraded from 10.6 to 10.8 and time machine is stuck on 'preparing backup'

I am running a MBP, purchased in 2011. I upgraded on Sunday from 10.6 to 10.8 and everything seemed to be working fine. Thought I would do a backup but the drive has just been stuck on 'preparing backup' for ages. Does anybody have any ideas of what I can do?
Thanks.

I was going to suggest a restart - glad that I didn't. When upgrading OS's, there's usually a lot of data to back up, but I'm surprised that it took 'ages'!
Clinton

TimeMachine 'Preparing Backup' forever

Similar Messages

Maybe you are looking for