Time Machine Preparing ad nauseum

Folks,
As of the 10.7.1 update my Time Machine enters the Preparing mode and never exits same. I allowed it to "prepare" for 12 hours yesterday with no change.
I then stopped the backup & entered Time Machine.
The time line indicated several backups (about every two hours) for the past day? It also showed all backups for the last month. However, the backups for the last day were labeled in white, but the previous backups were in purple (except for 2?).
Does that indicate a difficulty in reading the data?
Should I wipe the backup drive & start over?
Regards,
Jack

Are Lacie really that bad? I thought that the main reason they are mentioned in these forums is that Lacie are one of the only brands of external storage that apple actively promote through their own web stores so there a good chance that quite a few Mac users will buy one. Anyway I can't afford to buy another Hard Drive at the moment and the lacie works perfectly apart from Time Machine.
The problem seems to be with Mac OS the more I delve into these forums and more importantly the 10.5.2. update which is where Time Machine appears to be providing users with a lot of troubles.
The Apple support self service on the website is far from comprehensive as I guess they want you to purchase Apple Care for ongoing support after the 90 days initial period but come on apple give us a break and sort it out or provide a support email address for specific problems!

Similar Messages

  • Time Machine - Preparing backup - It's endless

    My C2D Mac Mini is hanging on Time Machine - Preparing Backup for the second time since "Upgrading" to 10.5.2
    I had to re-format my backup disk last time and start all the backups again.
    Here is an extract from the console log:
    29/04/2008 23:50:13 /System/Library/CoreServices/backupd[1094] Starting standard backup
    29/04/2008 23:50:13 /System/Library/CoreServices/backupd[1094] Backing up to: /Volumes/LaCie Disk/Backups.backupdb
    29/04/2008 23:50:15 /System/Library/CoreServices/backupd[1094] Event store UUIDs don't match for volume: Macintosh HD
    29/04/2008 23:50:15 /System/Library/CoreServices/backupd[1094] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
    Does anyone recognise this? I'm a Mac novice so I don't understand what it all means. I hope I don't have to reformat and start again as I was converted to Mac from PC on the advice that "A Mac Works!"
    My backup drive is a 500GB Lacie Mini if that is of any relevance. Spotlight is told not to index the drive and also the Lacie drive is told not to back itself up.
    Can anyone help as it's driving me nuts!

    Are Lacie really that bad? I thought that the main reason they are mentioned in these forums is that Lacie are one of the only brands of external storage that apple actively promote through their own web stores so there a good chance that quite a few Mac users will buy one. Anyway I can't afford to buy another Hard Drive at the moment and the lacie works perfectly apart from Time Machine.
    The problem seems to be with Mac OS the more I delve into these forums and more importantly the 10.5.2. update which is where Time Machine appears to be providing users with a lot of troubles.
    The Apple support self service on the website is far from comprehensive as I guess they want you to purchase Apple Care for ongoing support after the 90 days initial period but come on apple give us a break and sort it out or provide a support email address for specific problems!

  • Time Machine preparing WAY too many items

    I just noticed that my Time Machine backups are taking an unusually long time. So when the last one finished, I immediately ran a second backup with Time Machine preferences open so I could watch the progress bar. It said it was “Preparing (about) 3,200 Items...” for a total of 660 KB. The backup took about 6 or 7 minutes. This now happens every time TM does a backup.
    Obviously this is very wrong given that only a few seconds had passed between backups and nothing had changed. There should have been a handful of items to prepare, and the backup should have taken a few seconds. I installed TimeTracker, and it showed a few dozen items had been backed up. I made sure to open every folder/subfolder but found nothing that would account for 3,200 items.
    Anyone have any idea what might be going on?

    MacVal wrote:
    When I reinstalled my software I didn't drag any of the old preference files back over either, just in case something was corrupted. And everything I installed software-wise has been running on 10.6.8 forever with no issues. The only exceptions were Apple Remote Desktop, which I did not reinstall this time, and a new generation of Plex media server I've been trying out, which I recently upgraded to from an older version.
    In theory, a incompatible or faulty kernel extension could cause this, but it's highly doubtful.
    I assume there is no way that any my documents could cause strange system behaviour?
    Never say never, but highly unlikely.
    At times both before and after this rebuild when I've been playing around with TM preferences (selecting the drive, setting which folders to exclude) my CPU will run very high (can't recall the % exactly) and my fans will kick into high gear. Obviously this is not normal, especially with nothing else running at the time. Something is clearly messing with TM.
    Ah, yes, very suspicious.  I don't recall seeing this before.
    Perhaps the preference file (where all that is kept) is damaged. Try a "full reset" of Time Machine, per #A5 in Time Machine - Troubleshooting. 
    If that doesn't help:
    Are you running any 3rd-party disk/directory monitoring apps, such as the Directory Protection feature of Tech Tools?
    Does that happen with other pages in System Preferences?
    Does it happen in a different user account (if you don't have one, create one via System Prefs > Accounts).  You'll have to unlock the panel to make changes from a non-Admin account.
    If none of that provides any light, a clue may be lurking in your logs.  See the tan box in OSX Log Files to locate your system.log, then the blue box to decipher it.  Use the technique in the Monitoring the log ... section to see if any messages appear while you're using the TM Prefs window.  If they do, copy and post them (or, if there are a lot of them, a reasonable portion) here.
    Message was edited by: Pondini

  • Time machine preparing forever and spotlight estimating indexing time

    hey guys,
    Im having two problems that seem to be related. time machine gets stuck on preparing with the following error in console:
    Jul 18 17:03:19 Macintosh-5 /System/Library/CoreServices/backupd[6926]: Waiting for index to be ready (905 > 0)
    Spotlight is also acting up and freezes indefinitely whilst estimating indexing time with the following console error:
    Jul 18 17:03:44 Macintosh-5 mds[94]: (Error) Server: mdsync launch failed: (ipc/send) invalid destination port
    I have not been able to find much on this last error on support forums. Any ideas? I have erased all spotlight indices, reset PRAM, this problems occurs when indexing both the internal and external hard drives. (The drive i am using for time machine has worked in the past.) I have also repaired disk permission etc. Any solutions without reinstalling leopard as the reason why i am trying to back up is so I can do a reinstall then!
    Thanks!

    I had this exact problem yesterday (Waiting for index to be ready (905 > 0)). I rebooted with the shift key held down, rebooted again, and rebuilt my Spotlight index. Now there seems to be a conflict between Spotlight and Time Machine:
    Aug 26 05:03:08 Musa /System/Library/CoreServices/backupd[702]: Waiting for Spotlight to finish indexing /Volumes/Backup of Musa/Backups.backupdb
    I thought of adding the backup drive to Spotlight's exclusion list, but doesn't the backup drive need to be indexed by Spotlight for it to work with Time Machine?

  • 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

  • MY POSSIBLE FIX for Time Machine preparing for ages every hour

    Like many others, i have had problems with Time Machines backups - ever since upgrading to 10.5.2. Every hour it would say 'preparing' for ages, and then, when it did finally backup, the data transfer was incredibly slow. Not to mention the amount of cpu usage it was using during the preparing status!
    I have no idea if this is a FIX, or if i was just lucky, but Time Machine now works as it should, i.e. it backs-up seamlessly.
    Anyway, this is what i did: booted from my Tiger disc (yes, even though i have Leopard) and went into its 'disc utility', from there i selected 'repair permissions'. Once the Tiger disc had completed repairing the permissions, i quit out of it and restarted my MacBook normally, i.e. not from the Tiger disc. When it had finished restarting, i went to disc utility and selected 'repair permissions'.
    Ever since, TM has been just perfect. Coincidence? - i honestly do not know.
    By the way, i don't know if repairing the permissions from within Leopard did anything or not, but this is the sequence i used. Plus also, it might be good to note that i had repaired permissions many a time, but with no success in fixing TM, but once doing it from the Tiger disc it fixed TM.
    I hope it helps someone, because i know just how annoying it was when TM was not working correctly!

    I upgraded from Tiger to Leopard, which is why i believe i have had trouble.
    What is 'A&I or E&I'?

  • Time Machine "Preparing"

    I've read the other threads on TM slowness, etc. but need some interpretation of what this Console entry means (see below.) As you can see, TM was doing fine and has been for several months until today. Then it suddenly stopped doing the hourly backups. It seemed to be locked in the Preparing mode and I tried to restart my iMac (running 10.5.2 with 2gb memory)but could not conventionally. I powered it off then back on. I do not know what deep traversal means but after reading other posts assume it means that TM is reviewing every file on my computer before commencing a fresh backup. If so, it has been at it for over three hours without going on and finishing the backup. (I have about 25gb on the iMac HD.) I'd appreciate any analysis as to what the problem is and what I should do. If just letting TM run for a day is the answer, I'm fine with that; I don't necessarily have to take radical steps to be satisfied. Thanks in advance for all help.
    2/21/08 6:32:42 AM /System/Library/CoreServices/backupd[429] Backing up to: /Volumes/Iomega HDD/Backups.backupdb
    2/21/08 6:32:44 AM /System/Library/CoreServices/backupd[429] No pre-backup thinning needed: 5.70 GB requested (including padding), 324.57 GB available
    2/21/08 6:36:35 AM /System/Library/CoreServices/backupd[429] Copied 1722 files (4.7 GB) from volume Macintosh HD.
    2/21/08 6:36:36 AM /System/Library/CoreServices/backupd[429] No pre-backup thinning needed: 111.2 MB requested (including padding), 319.91 GB available
    2/21/08 6:36:40 AM /System/Library/CoreServices/backupd[429] Copied 389 files (129 KB) from volume Macintosh HD.
    2/21/08 6:36:41 AM /System/Library/CoreServices/backupd[429] Starting post-backup thinning
    2/21/08 6:36:55 AM /System/Library/CoreServices/backupd[429] Deleted backup /Volumes/Iomega HDD/Backups.backupdb/Rick Davenport’s iMac/2008-01-22-082757: 323.88 GB now available
    2/21/08 6:36:55 AM /System/Library/CoreServices/backupd[429] Post-back up thinning complete: 1 expired backups removed
    2/21/08 6:36:55 AM /System/Library/CoreServices/backupd[429] Backup completed successfully.
    2/21/08 6:57:56 AM /System/Library/CoreServices/backupd[588] Starting standard backup
    2/21/08 6:57:56 AM /System/Library/CoreServices/backupd[588] Backing up to: /Volumes/Iomega HDD/Backups.backupdb
    2/21/08 6:57:57 AM /System/Library/CoreServices/backupd[588] No pre-backup thinning needed: 1.14 GB requested (including padding), 323.88 GB available
    2/21/08 6:58:43 AM /System/Library/CoreServices/backupd[588] Copied 1328 files (879.1 MB) from volume Macintosh HD.
    2/21/08 6:58:43 AM /System/Library/CoreServices/backupd[588] No pre-backup thinning needed: 111.1 MB requested (including padding), 323.02 GB available
    2/21/08 6:58:45 AM /System/Library/CoreServices/backupd[588] Copied 186 files (5 KB) from volume Macintosh HD.
    2/21/08 6:58:46 AM /System/Library/CoreServices/backupd[588] Starting post-backup thinning
    2/21/08 6:58:46 AM /System/Library/CoreServices/backupd[588] No post-back up thinning needed: no expired backups exist
    2/21/08 6:58:46 AM /System/Library/CoreServices/backupd[588] Backup completed successfully.
    2/21/08 7:57:56 AM /System/Library/CoreServices/backupd[666] Starting standard backup
    2/21/08 7:58:06 AM /System/Library/CoreServices/backupd[666] Backing up to: /Volumes/Iomega HDD/Backups.backupdb
    2/21/08 7:58:06 AM /System/Library/CoreServices/backupd[666] No pre-backup thinning needed: 123.0 MB requested (including padding), 323.02 GB available
    2/21/08 7:58:12 AM /System/Library/CoreServices/backupd[666] Copied 385 files (10.0 MB) from volume Macintosh HD.
    2/21/08 7:58:12 AM /System/Library/CoreServices/backupd[666] Starting post-backup thinning
    2/21/08 7:58:14 AM /System/Library/CoreServices/backupd[666] Deleted backup /Volumes/Iomega HDD/Backups.backupdb/Rick Davenport’s iMac/2008-02-20-073821: 323.02 GB now available
    2/21/08 7:58:14 AM /System/Library/CoreServices/backupd[666] Post-back up thinning complete: 1 expired backups removed
    2/21/08 7:58:15 AM /System/Library/CoreServices/backupd[666] Backup completed successfully.
    2/21/08 8:57:56 AM /System/Library/CoreServices/backupd[751] Starting standard backup
    2/21/08 8:58:06 AM /System/Library/CoreServices/backupd[751] Backing up to: /Volumes/Iomega HDD/Backups.backupdb
    2/21/08 11:02:06 AM /System/Library/CoreServices/backupd[251] Starting standard backup
    2/21/08 11:02:16 AM /System/Library/CoreServices/backupd[251] Backing up to: /Volumes/Iomega HDD/Backups.backupdb
    2/21/08 11:02:16 AM /System/Library/CoreServices/backupd[251] Event store UUIDs don't match for volume: Macintosh HD
    2/21/08 11:02:16 AM /System/Library/CoreServices/backupd[251] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
    2/21/08 2:21:37 PM /System/Library/CoreServices/backupd[240] Starting standard backup
    2/21/08 2:21:47 PM /System/Library/CoreServices/backupd[240] Backing up to: /Volumes/Iomega HDD/Backups.backupdb
    2/21/08 2:21:48 PM /System/Library/CoreServices/backupd[240] Event store UUIDs don't match for volume: Macintosh HD
    2/21/08 2:21:48 PM /System/Library/CoreServices/backupd[240] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
    2/21/08 3:53:21 PM /System/Library/CoreServices/backupd[186] Backup requested by user
    2/21/08 3:53:21 PM /System/Library/CoreServices/backupd[186] Starting standard backup
    2/21/08 3:53:21 PM /System/Library/CoreServices/backupd[186] Backing up to: /Volumes/Iomega HDD/Backups.backupdb
    2/21/08 3:53:22 PM /System/Library/CoreServices/backupd[186] Event store UUIDs don't match for volume: Macintosh HD
    2/21/08 3:53:22 PM /System/Library/CoreServices/backupd[186] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|

    I am having the same problem on our server (or at least the mac we use as a server - it doesnt have any special server software as far as I know. Says 'Preparing" forever. It wont ever actually start the backup. It worked fine at first, but now it just sits and spins.
    The main problem is that when it tries its backup and starts it's "sit and spin" mode, I loose connection to the server and everything im working on. The only way to get back access is to hold down the power key to restart (it wont let me restart through the apple). It also causes any programs I am working with on the local machines to crash.
    I have just turned Time Machine completely off so that I can access all the files I need to work on from the server.
    My time machine works perfectly at home - but its a major mess here at work.
    This needs to be addressed ASAP. Hundreds of large files (brochures, annual reports, etc) are currently NOT being backed-up.

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

  • No sound while time machine prepares for backup

    something strange happen to my OS. yesterday i updated to 10.5.2, and now, while time-machine started to prepare it's backup, i tried to listen to a mp3 song.
    no sound came. in the system preferences, suddenly i don't have any sound input or output devices.
    i have a powerbook g4, 1.87 ghz, 1.5 RAM.
    what is going on here???.

    something strange happen to my OS. yesterday i updated to 10.5.2, and now, while time-machine started to prepare it's backup, i tried to listen to a mp3 song.
    no sound came. in the system preferences, suddenly i don't have any sound input or output devices.
    i have a powerbook g4, 1.87 ghz, 1.5 RAM.
    what is going on here???.

  • Time Machine "Preparing Backup"

    Am I understanding correctly (from reading some other discussions here) that there are issues with Time Machine back ups and Yosemite, and that it's not just me having these problems? Since I upgrade I am having major issues with wifi connection being dropped and my Time Machine hasn't performed a back up in 19 days. It looks as though it will but stalls at "preparing back up". When it finally stops I get an error message saying it can't find the disc. I've restored the Time Machine to factory settings and started over more than once but still get the same message. Am I doing something wrong or is this an Apple issue?

    Just to be clear you are using a Time Capsule for your Time Machine backups. A Time Capsule looks like this
    or this
    In that case follow these instructions and reply with your results:
    AirPort Time Capsule: Time Machine backups may not mount; "Backup volume cannot be found" may appear - Apple Support

  • Time Machine preparing for over 19 hours ??

    Is this exceptionally long? There has not been a backup of the laptop (to the Time Capsule) for about 3 months. I have installed the monitoring widget for time machine and this shows that it is doing the full scan - but come on surely nearly a day preparing is too much. I have the laptop connected directly to the time capsule via ethernet.
    Piers

    pierslofi wrote:
    Is this exceptionally long?
    Yes. It's clearly stuck.
    There has not been a backup of the laptop (to the Time Capsule) for about 3 months.
    After that long, TM will almost certainly do a full backup. So if your TC isn't considerably more than twice the size of the data it's backing-up, your best bet will be to erase it and let TM start fresh.
    Also, try all the things in item #D2 of the Time Machine - Troubleshooting *User Tip* at the top of this forum.

  • Time Machine preparing lasts forever

    When I start Time Machine to back up, it takes hours (last night it has been on), ad is still preparing, how long can I expact it to last before preparations are finished.
    It's been a while since my last back up (because of this problem).
    I back Up to a LaCie 1 terra disk Firewire.
    Actually I want t erase the disk, and start it all over, but it is not possible to deactivate this disk, how can I erase the disk.
    Thanx

    AppleChat wrote:
    Used Backup for years and tried time machine for first time yesterday.
    Iy has been running or 12 hours and done 14 of 100 gb. Is that normal for an initial backup?
    Thank you.
    See my answer in the other thread you posted this in: http://discussions.apple.com/message.jspa?messageID=10141710#10141710
    Please don't double-post the same question.

  • Time Machine Preparing for ages

    I know this has come up a lot, but there seem to be so many possibilities, I thought I'd post some data from Time Machine Buddy.
    Basically it had all been working great, but seems to have gone AWOL recently. Its still saying preparing just now in my latest attempt. (To be fair, hasn't been that long), but I'd been getting some error messages about not being able to mount etc.
    And that appears in the TMB report so far :
    Starting standard backup
    Mounted network destination using URL: afp://Iain%[email protected]/Time%20Capsule
    Backup destination mounted at path: /Volumes/Time Capsule
    Failed to mount disk image /Volumes/Time Capsule/Iain MacDonald’s MacBook Pro_002332b100e6.sparsebundle (DIHLDiskImageAttach returned: 60)
    Waiting 60 seconds and trying again.
    Failed to eject volume /Volumes/Time Capsule (FSVolumeRefNum: -101; status: -47; dissenting pid: 0)
    Backup destination alias resolved to path: /Volumes/Time Capsule
    Any clues as to what my next steps should be would be much appreciated.
    Many thanks.
    Message was edited by: Iain MacDonald1

    I upgraded from Tiger to Leopard, which is why i believe i have had trouble.
    What is 'A&I or E&I'?

  • Time Machine-"preparing for EVER/backup"

    i read an earlier post, saying that after mac crashes, its likely TM wants to do an initial backup again, and something in Console..
    I hadnt crashed, only change was hadnt backed up in 2 weeks while traveling...so after coming home, my Time Capsule and Time Machine went to back up, and 4 hours of "preparing back up", it never backed up..And i guess my question is, why is the response from TM to want to do its initial backup as opposed to just backing up to whatever is new or had changed. Does this mean, after a day or two of not connecting with TimeCapsule or whatever External Drive I choose, that this will happen? As for now, how long would you say is a normal time, for the "preparing" to...prepare, and start to backup? And if its doing its initial, isnt it wanting to do everything, so there will be duplicates?
    thank you for any help!!!

    JGcalifornia wrote:
    i read an earlier post, saying that after mac crashes, its likely TM wants to do an initial backup again, and something in Console..
    If that's what it said, it was wrong. After a crash, TM can't be sure where everything was when "the lights went out", so it will likely do a "deep traversal", examining every file and folder on your system to see what needs to be backed-up. It will send explanatory messages to your logs. This process takes quite a while, of course, and much more with a Time Capsule, but TM won't do a full backup just because of a crash.
    I hadnt crashed, only change was hadnt backed up in 2 weeks while traveling...so after coming home, my Time Capsule and Time Machine went to back up, and 4 hours of "preparing back up", it never backed up..And i guess my question is, why is the response from TM to want to do its initial backup as opposed to just backing up to whatever is new or had changed. Does this mean, after a day or two of not connecting with TimeCapsule or whatever External Drive I choose, that this will happen? As for now, how long would you say is a normal time, for the "preparing" to...prepare, and start to backup? And if its doing its initial, isnt it wanting to do everything, so there will be duplicates?
    You have about three questions there.
    First, TM will do a full, complete backup after certain hardware repairs, a full restore, or going several days without a backup. Just how many days is unclear, but it seems to be a combination of days and the volume of changes: 10 days seems safe, 2 weeks may not be.
    And yes, this is another full backup of everything on your system. So it will take a very long time and a lot of disk space. Depending on how much space is available, you may want to erase the disk and let TM start over.
    You say TM "never backed up" after the lengthy "preparing" phase. Did the backup fail, or did you cancel it?
    If it failed, we need to look at the messages in your logs. Download the +Time Machine Buddy+ widget from: http://www.apple.com/downloads/dashboard/status/timemachinebuddy.html. It shows the messages from your logs for one TM backup run at a time, in a small window. Navigate to the failed backup, then copy and post the messages here (be sure to get them all, as sometimes they overflow the small window).

  • Leopard applications all hang while Time Machine prepares for backup

    I'm sure others have posted about this but I can't find a usable solution. I have the most recent version of Leopard, a 1TB external FireWire drive dedicated to Time Machine storage and about 400GB of backups on it. Every day at some point, Time Machine starts a backup, pauses while preparing, and the entire Mac grinds to a halt. New processes won't launch, open applications hang, Finder becomes unresponsive, menus and dock freeze in whatever position they were in at the point of launch, and I can't cancel the backup process.
    The only solution is to turn off the backup drive while its running and wait for the Mac to wake up again (which it does in under a minute). I have no virus protection running. I have erased the drive and started fresh at least once to no avail.
    Since I am effectively breaking a live connection every time I turn the drive off without unmounting it first (an obvious no-no), the data has great potential to be getting more and more screwed up. What can I do?

    Message logs:
    October 12, 2009, 1:43:25 AM
    Volume at path /Volumes/Racer BU does not appear to be the correct backup volume for this computer. (Cookies do not match)
    Backup failed with error: 18
    October 12, 2009, 11:32:32 AM
    Starting standard backup
    Backing up to: /Volumes/Racer BU/Backups.backupdb
    Event store UUIDs don't match for volume: Racer X
    Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
    No pre-backup thinning needed: 984.2 MB requested (including padding), 443.72 GB available
    Copied 21948 files (368.1 MB) from volume Racer X.
    No pre-backup thinning needed: 548.2 MB requested (including padding), 443.35 GB available
    Copied 961 files (965 KB) from volume Racer X.
    Starting post-backup thinning
    Deleted backup /Volumes/Racer BU/Backups.backupdb/Eric’s Mac Pro/2009-10-10-215828: 443.35 GB now available
    Deleted backup /Volumes/Racer BU/Backups.backupdb/Eric’s Mac Pro/2009-10-10-205855: 443.36 GB now available
    Deleted backup /Volumes/Racer BU/Backups.backupdb/Eric’s Mac Pro/2009-10-10-195856: 443.40 GB now available
    Deleted backup /Volumes/Racer BU/Backups.backupdb/Eric’s Mac Pro/2009-10-10-185908: 443.46 GB now available
    Deleted backup /Volumes/Racer BU/Backups.backupdb/Eric’s Mac Pro/2009-10-10-175907: 443.51 GB now available
    Post-back up thinning complete: 5 expired backups removed
    Backup completed successfully.
    October 12, 2009, 12:18:32 PM
    Starting standard backup
    Backing up to: /Volumes/Racer BU/Backups.backupdb
    No pre-backup thinning needed: 954.4 MB requested (including padding), 443.51 GB available
    Unable to rebuild path cache for source item. Partial source path:
    Copied 16717 files (339.6 MB) from volume Racer X.
    No pre-backup thinning needed: 569.5 MB requested (including padding), 443.17 GB available
    Copied 634 files (18.7 MB) from volume Racer X.
    Starting post-backup thinning
    Deleted backup /Volumes/Racer BU/Backups.backupdb/Eric’s Mac Pro/2009-10-10-225832: 443.24 GB now available
    Deleted backup /Volumes/Racer BU/Backups.backupdb/Eric’s Mac Pro/2009-10-10-165828: 443.25 GB now available
    Deleted backup /Volumes/Racer BU/Backups.backupdb/Eric’s Mac Pro/2009-10-10-155855: 443.30 GB now available
    Deleted backup /Volumes/Racer BU/Backups.backupdb/Eric’s Mac Pro/2009-10-10-145857: 443.36 GB now available
    Deleted backup /Volumes/Racer BU/Backups.backupdb/Eric’s Mac Pro/2009-10-10-135852: 443.38 GB now available
    Post-back up thinning complete: 5 expired backups removed
    Backup completed successfully.
    October 12, 2009, 4:46:51 PM
    Starting standard backup
    Volume at path /Volumes/Racer BU does not appear to be the correct backup volume for this computer. (Cookies do not match)
    Backup failed with error: 18
    etc...
    The long periods between backups are when it is "preparing for backup" and nothing is happening. Sometimes this is while I'm not using it and the machine is asleep.

Maybe you are looking for

  • When I click on Pages, I get a message that says it cannot open due to an error

    I have iWork V9.0.03 and cannot get Pages to open.  I need to update some things on a document and cannot get it to open or get Pages to open.  I reinstalled iWork and even did the most recent update.  Still have issues. I really need Pages to get wo

  • Is there any way to block accessing Exchange server

    Hello, We are using iPhone as a business phone to access Exchange server using ActiveSync. Is there any way to block non-company, in other words private iPhone, iPhone to access Exchange Server? Some users have 2 iPhones (1 provided by our company, 1

  • Impact of SRM 7.0 Upgrade on XI 3.0

    Hi, Soon we are going to upgrade our SRM 4.0 system to SRM 7.0 and MDM Catalog 3.0. So is there any impact on XI 3.0, do we need to upgrade XI 3.0 to PI 7.0 or PI 7.1 to be able to do this. Do you have any idea? I have looked in the PAM at SAP but I

  • How to Transfer Upgrade and not go through Verizon

    I can get the Iphone 4s though Apple for $99 but it doesn't look like I can transfer an upgrade through their order process.  Is that possible or am I stuck going through Verizon and paying $50 more for the same phone?

  • Formula from the 15th to the end of the previous month.

    Hi, I am trying to create a formula in the selection expert to run a report on the 1st day of the month for an end time from the 15 of the previous month to the end of the previous month. Thanks.