What I did to fix Time Machine in 10.5.3
Thought I'd document this because I just spent about an hour resolving it on two separate machines.
Machines:
New iMac 24" (1 TB HD)
MacBook Pro 15" 2nd generation (120 GB HD)
Time Capsule (1 TB)
*If Time Machine is stuck on Preparing...* Let it go. For whatever reason, the first backup after migrating to 10.5.3 can take an excruciatingly long time (this did not occur with 10.5.1 or 10.5.2). You may see the following messages in your system.log:
May 28 22:02:37 new-host /System/Library/CoreServices/backupd[151]: Event store UUIDs don't match for volume: Macintosh HD
May 28 22:02:37 new-host /System/Library/CoreServices/backupd[151]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
*If you followed others' "advice" and deselected/reselected the backup volume in preferences, and now Time Machine no longer wants to mount the volume automatically; and/or if you see the following in your log*:
May 28 21:58:39 new-host /System/Library/CoreServices/backupd[333]: Network mountpoint /Volumes/Time Capsule not owned by backupd... remounting
May 28 21:58:39 new-host /System/Library/CoreServices/backupd[333]: Failed to remount network volume.
May 28 21:58:44 new-host /System/Library/CoreServices/backupd[333]: Backup failed with error: 19
Try the following:
1.) Go into Time Machine preferences and choose None for disk. This will turn Time Machine off.
2.) Restart the computer. Time Machine should still be off.
3.) Rechoose the proper volume. You should get the excruciatingly long "Preparing Backup" message and see the above "deep transversal" message in your log.
For some reason, there seems to be an issue with the backupd process in 10.5.3. Restarting the computer with Time Machine off then turning it back on seems to fix the issue.
Hi. I'm having similar problems (Time Machine seems to be forever stuck on "Preparing backup" after an update to Mac OS X 10.5.3), but I'm having slightly different symptoms. My setup looks like this:
* Mac OS X -Sever- 10.5.3 Leopard running on a Mac Pro tower
* 1TB LaCie BigDisk plugged directly into the server via FireWire 800, serving as Time Machine volume
Everything was smooth while using Mac OS X Server 10.5.2, but I have updated to Mac OS X 10.5.3 and swapped in a new 1TB drive (to take the old one off-site). I set up Time Machine as before and let it run overnight, but it is still in the "Preparing backup" phase.
Checking the system.log file I can see a huge amount of "Waiting for index to be ready (906 > 0)" messages.
Here are some interesting portions, abbreviated for brevity, of the log. Note the dates
May 30 00:00:14 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 00:00:44 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 00:01:14 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 00:01:44 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 00:02:14 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 00:02:44 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:15:17 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:15:47 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:16:17 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:16:47 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:17:17 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:17:47 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:18:17 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:18:47 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:19:17 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:19:47 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:20:17 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
May 30 09:20:47 kringmerk /System/Library/CoreServices/backupd[2363]: Waiting for index to be ready (906 > 0)
Eventually I just canceled the backup. Then I requested a new backup after turning off Time Machine and turning it back on:
May 30 13:32:50 kringmerk /System/Library/CoreServices/backupd[7620]: Backup requested by user
May 30 13:32:50 kringmerk /System/Library/CoreServices/backupd[7620]: Starting standard backup
May 30 13:32:50 kringmerk /System/Library/CoreServices/backupd[7620]: Backing up to: /Volumes/Eskimo Server Time Machine 2/Backups.backupdb
May 30 13:32:50 kringmerk /System/Library/CoreServices/backupd[7620]: Journaling is disabled on the backup destination volume. Enabling.
May 30 13:32:52 kringmerk /System/Library/CoreServices/backupd[7620]: Event store UUIDs don't match for volume: Macintosh HD
May 30 13:32:52 kringmerk /System/Library/CoreServices/backupd[7620]: Backup content size: 231.0 GB excluded items size: 495.9 MB for volume Macintosh HD
May 30 13:32:52 kringmerk /System/Library/CoreServices/backupd[7620]: No pre-backup thinning needed: 276.57 GB requested (including padding), 931.16 GB available
May 30 13:32:52 kringmerk /System/Library/CoreServices/backupd[7620]: Waiting for index to be ready (909 > 0)
May 30 13:32:57 kringmerk /System/Library/CoreServices/backupd[7620]: Waiting for index to be ready (906 > 0)
May 30 13:33:42 kringmerk /System/Library/CoreServices/backupd[7620]: Waiting for index to be ready (906 > 0)
May 30 13:34:37 kringmerk /System/Library/CoreServices/backupd[7620]: Waiting for index to be ready (906 > 0)
May 30 13:35:07 kringmerk /System/Library/CoreServices/backupd[7620]: Waiting for index to be ready (906 > 0)
May 30 14:02:07 kringmerk /System/Library/CoreServices/backupd[7620]: Waiting for index to be ready (906 > 0)
May 30 14:02:37 kringmerk /System/Library/CoreServices/backupd[7620]: Waiting for index to be ready (906 > 0)
May 30 14:03:07 kringmerk /System/Library/CoreServices/backupd[7620]: Waiting for index to be ready (906 > 0)
May 30 14:03:37 kringmerk /System/Library/CoreServices/backupd[7620]: Waiting for index to be ready (906 > 0)
and it's still going like that, "Waiting for index to be ready." As you can see, every thirty seconds it reports that it's still waiting for the index to be ready. Obviously, I'm prepared for this to take a long time as I've got over 200 GB of data to backup with Time Machine, but should it really take almost 16 hours just to "Prepare"?
Also note the absence of a "Node requires deep traversal" message. I'm not really sure what to try next except perhaps a full restart after shutting down Time Machine, then turning it back on after it starts up.
If that doesn't work, however, do you have any other suggestions I could try?
Thanks,
-Meitar Moscovitz
Similar Messages
-
Fixing Time Machine/External Hard Drive
My Time Machine stopped working in April, and I couldn't get it working again. I thought I was going to have to buy another External Hard Drive, but I've been putting that off. Anyway, I finally decided that I had to either fix it today or buy another External Hard Drive. I called Apple. TOGETHER (It took both of us), we stumbled across the solution: REPLUG THE EXTERNAL HARD DRIVE CABLE INTO ANOTHER USB PORT. That did it, and Time Machine is working again. Not only that, I then did the same thing with my on-strike printer and it is now back on duty. So, I now have a list of three things that should be tried before panicking: (1) Turn the computer OFF and then ON again. (2) Replug the cable into another USB port. (3) Try another browser [Sometimes website incompatibility is the problem].
I finally bought another external hard drive. No more problems now.
-
What is the status of time machine not working with yosemite?
I upgraded mu mac pro to yosemite and since have found time machine does not work.
Also, my old backup via a clikfree wireless backup does not work any longer.
Is anyone working on this issue?
Is there anyway I can backup my information today and until time machine &
yosemite get fixed?These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the word "Starting" (without the quotes.) You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard."
Each message in the log begins with the date and time when it was entered. Note the timestamp of the last "Starting" message that corresponds to the beginning of an an abnormal backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ If all you see are messages that contain the word "Starting," you didn't clear the text field.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. Don't post more than is requested.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting. -
I was having problems with Time Machine, just like many people in here. Slow transfers, error in the middle of the process.
Here's how I fixed it:
1. In System Preferences>Time Machine, turn off backups (the On/Off switch).
2. In Disk Utility, select the external hard drive, then go to the Erase section (not First Aid or Partition).
3. Choose Volume Format: +Mac OS X Extended (Journaled)+
3.5. You can name it whatever (I left it at Untitled, then just changed it later).
4.Click Erase.
5. Let the disk remount itself. Should show up as a simple external drive (Firewire for me, I don't know what yours is).
6. If asked, make this the Time Machine backup disk. If you are not asked (I wasn't), go to Time Machine preferences and manually set it as the disk.
7. Either wait for Time Machine to back up itself, or right-click (CTRL+click) Time Machine in the Dock, then click Back Up Now.
This worked for me and my Western Digital My Book 750GB drive! It didn't entirely solve the slow transfer problem, but it helped for sure. Took about 2 hours to transfer about 80GB.
I hope this helps!Ok. Well I was desparate as trying time machine I haven't had one successful backup and had x3 kernel panics whilst TM was working in the background
I looked at my Iomega Desktop HD- Time Machine initially set it up as HFS Extended, Journaled, Case Sensitive.
So in Disk Utility, I wiped the drive and set to HFS Extended, Journaled
And despite the fact that I was highly sceptical, five minutes on I am at 1.06 Gb of 35 Gb and I can actually see the progress bar moving, which is a first.
I'll leave it to run overnight and report back -
Can't set up my time capsule on Airport Extreme (updated). Apple instructions are to use manual set up. Click on Advanced tab. Click on Mobileme and enter Mobileme ID and password. I did this. But Time Machine window is blank. Tryed to click on update window after entering Mobileme ID but Airport does not respond (turn of then on)
mickair wrote:
I have been experiencing some networking problems
Welcome to Apple's discussion groups.
I have the latest Time Capsule ("TC"), an old Airport Extreme Base Station ("AEBS") bought in 2007 and 2 Airport Expresses, one bought in 3 months ago ("AE-Alpha") and the other bought back in 2007 ("AE-Beta"). All of them have been updated with the latest firmware.
Based on those dates, the AirPort Extreme is probably flat (as opposed to dome-shaped), making it 802.11n-capable. The Newer AirPort Express is probably an 802.11n-capable model A1264, while the older one is probably a model A1084 or A1088.
I use {the TC's} DHCP function ... to avoid unauthorized use.
This a discussion for another thread, but that's not what DHCP is for.
The wireless setting for it is to participate as WDS Main, but after reading various posts, it seems WDS is a bad idea
With that older AirPort Express you're stuck with WDS unless you decide to replace it with a newer model.
The AEBS is currently setup as being a WDS Relay at the moment
Why a relay? That's only needed if there's another base station "beyond" it that is configured to depend on it.
Since the AEBS is connected to the TC via Ethernet, you should probably configure it as a "roaming network":
http://discussions.apple.com/thread.jspa?threadID=2273124
{The AE-Alpha} connects fine as WDS remote at the moment
I don't have any experience with mixed WDS and non-WDS networks, but since it's 802.11n-capable, you may be able to configure it to "extend" the network of the TC rather than as WDS. Look for a setting on the TC to "Allow this network to be extended".
Physical location:
AEBS in one end, TC and AE-Alpha in the middle while AE-Beta on the other end.
A device such as "AE-Beta" that's supposed to extend a network shouldn't be "at the end" but should be half way between the central base station and the clients that need an extended network. -
What size ext. hd for time machine
I'll be upgrading to Leopard in the next two weeks, and I was wondering what size external hd i should be looking at. I'm looking at the Western Digital My Book Premium Edition, which I found the 500gb version for $150 and the 750Gb version for $230. Is it worth the extra $80 for 250GB more hd space? How much space do I need to back up my 250GB drive (with 140GB used)??? Does Time Machine compress files at all??? Thanks for your response.
I have a similar situation. I have a 500gb iMac with 350gb used. I have a 500gb ext. hd with 465gb available. Time Machine (horrible so far in my opinion) claims I don't have enough room to run it. The math I learned still proves that 465 is greater than 350.
Not only that but installing Leopard was excruciating. If you have yet to install it, make sure you run the installer as archive then install and not upgrade. Upgrade will give you blue screen of death. Why did Apple, my favorite computer company, release an os with features that create so many windows like issues. So far I am nothing even close to excited, nor even satisfied with this $140 upgrade. -
I am trying to back up my imac using an external storage: My passport Studio 1TB. Each time it trys to back up Time machine says: Unable to complete back up. An error occurred while creating the backup folder. Does anyone know how I can fix this problem? Thanks
Plowie,
Do a search in Discussions, "An error occurred while creating the backup folder."
Many of us are having this problem and no fix has been offered, that I could find.
Unless you call "eject the external HDD; turn off; turn back on" a fix. That's what I have to do every 2 or 3 days; I even have to "force eject", with the concomitant warning message that you could lose data, etc. -
ITunes 9.2 update on windows 7 x64 failed What I did to fix it
Seems like everybody else had the same problems. In my case the upgrade originally failed with a 2324 error. It suggested trying again and if it continued that I should select tools download only. That is what I did. It will save the files to: C:\Users\YourUserName\AppData\Local\Apple\Apple Software Update .
The five files are:
AppleApplicationSupport
AppleMobileDeviceSupport64
Bonjour64
iTunes64
SetupAdmin
1. I started by running SetupAdmin.
2. Then I tried to install Bonjour64. Opps there is my 2324 error. So I clocked Start->Run->Services.msc In the list of services rightclick on Bonjour and select Stop Service. Then Click Start->Control Panel->Programs and Features Right Click on Bonjour and select uninstall. While here I decided to uninstall all of the other Apple programs (Don't forget Quicktime.)
Install Bonjour64
3. Install AppleApplicationSupport
4. Install AppleMobileDeviceSupport64
5. Install iTunes64
Opps there is the second error. Quicktime didn't install properly. Downloaded quicktime and installed it (don't do this). Ran qt and checked for upgrade. I have the latest available. Ran iTunes64 opps Quicktime didn't install properly.
***! Why is it even trying to reinstall qt if I have the latest?
6. Uninstall qt. Download iTunes 9.2+QT for x64
7. Install the download with no problems.
I then Disabled Bonjour since it causes problems on my system.
What I discovered. Bonjour is stealthed in. It should be an OPTION like safari. The Bonjour was not able to stop and uninstall the existing disabled Bonjour. Evidently the Quicktime player was also no able to be uninstalled by the upgrade. When manually uninstalled the upgrade could still not install qt.
The upgrade is not properly checking for installed versions. It forces an unneeded reinstall of qt.
The upgrade program is seriously broken and needs to be fixed.Seems like everybody else had the same problems. In my case the upgrade originally failed with a 2324 error. It suggested trying again and if it continued that I should select tools download only. That is what I did. It will save the files to: C:\Users\YourUserName\AppData\Local\Apple\Apple Software Update .
The five files are:
AppleApplicationSupport
AppleMobileDeviceSupport64
Bonjour64
iTunes64
SetupAdmin
1. I started by running SetupAdmin.
2. Then I tried to install Bonjour64. Opps there is my 2324 error. So I clocked Start->Run->Services.msc In the list of services rightclick on Bonjour and select Stop Service. Then Click Start->Control Panel->Programs and Features Right Click on Bonjour and select uninstall. While here I decided to uninstall all of the other Apple programs (Don't forget Quicktime.)
Install Bonjour64
3. Install AppleApplicationSupport
4. Install AppleMobileDeviceSupport64
5. Install iTunes64
Opps there is the second error. Quicktime didn't install properly. Downloaded quicktime and installed it (don't do this). Ran qt and checked for upgrade. I have the latest available. Ran iTunes64 opps Quicktime didn't install properly.
***! Why is it even trying to reinstall qt if I have the latest?
6. Uninstall qt. Download iTunes 9.2+QT for x64
7. Install the download with no problems.
I then Disabled Bonjour since it causes problems on my system.
What I discovered. Bonjour is stealthed in. It should be an OPTION like safari. The Bonjour was not able to stop and uninstall the existing disabled Bonjour. Evidently the Quicktime player was also no able to be uninstalled by the upgrade. When manually uninstalled the upgrade could still not install qt.
The upgrade is not properly checking for installed versions. It forces an unneeded reinstall of qt.
The upgrade program is seriously broken and needs to be fixed. -
What is the equation for Time Machine required space?
Once again Time Machine says it has run out of room to do my backup. I guess I just don't understand the equation for figuring this out.
These are my specs:
Disks being backed up - 2 drives
Internal Drive - 640gb, 482gb in use
External Drive - 500gb, 105gb in use
587gb total data in use
Time Machine disk - 1TB, 715gb in use, 284gb available, asking for 303gb
TM wants space that is more than half of my total data in use. I have one (old) 2gb file, all others are 99mb and smaller, mostly much smaller.
Why isn't TM removing older backup files to make room for the latest? Why does it think it needs a block of 303gb when the new files it needs to back up are all in the sub 10mb range?
On the surface it seems like TM is using disk sizes to do it's caluclations instead of file size.
What is the equation it uses to figure this out? I am puzzled...jlmcvay wrote:
Starting pre-backup thinning: 286.19 GB requested (including padding), 265.05 GB available
That's your main problem; wanting to back up about 238 GB (plus 20%). Curiously, that's a bit less than the previous messages.
See what's shown for Estimated size of full backup under the exclusions box in Time Machine Preferences > Options. According to the figures in your first post, it should be about 587 GB. If it's considerably larger, then there are two possibilities:
Something else is connected, and Time Machine is trying to back it up.
There's a directory problem on one of the disks being backed-up, so Time Machine thinks it's much larger. If so, try verifying your internal HD, and repairing the external, per #A4 in Time Machine - Troubleshooting.
But if the estimate is reasonably close, then something very large has changed. See #D4 in Time Machine - Troubleshooting for some of the common culprits. Unfortunately, there's no way to tell in advance what it is; you can only see that after a backup completes.
If nothing there helps, try excluding the external HD and trying again (per #10 in Time Machine - Frequently Asked Questions) -- that should tell us whether the problem is on the internal or the external. Then we can try to narrow it down.
Seems like there is a problem with the Event store UUIDs for my internal drive.
Not a major one. That message means that Time Machine isn't sure that the previous backup was completed normally (which it obviously didn't). When that happens, Time Machine can't use the Event store, but has to do a "deep traversal" to compare everything on the drive to the backups to figure out what's changed and needs to be backed-up. That takes a while, of course, and means your backup will take considerably longer than usual.
I commonly have iPhoto open all the time. If TM cannot back up iPhoto while it open that would explain why it needs to backup a lot of data.
That's a possible explanation, but 238 GB is a lot of photos. How large is your entire iPhoto Library?
Time Machine can sometimes back the iPhoto Library up when iPhoto is open -- it seems to depend on just what you've been doing. So it's fairly unusual for it to be missed for very long. (It ought to send a message after a certain time, but it doesn't.)
If excluding the external HD doesn't turn up a clue, try excluding your Pictures folder. -
What is better choice than Time Machine
I have a Seagaye GoFlex for Mac ( 2TB) external HD. I have fought with this drive and Time machine for over a year. I have partitioned the drive (2) to use for other purposes. 500 GB is for backup. Often it won't Backup. Sometimes it indicates it's read only. I end up erasing the disk, etc.. It's terrible as a Backup situation. I'm wondering if I would be better off with another application for my backup process? Something different than Time Machine.
Or is there someting I can do to correct my existing problem.
One of my situations is if i Shut Down my computer. When I start up, the Backup Partition does not mount. Is the volume just too large? I'm really confused, and upset with this ongoing problem.Different backup software won't help if the external drive chipset is the source of the flaky mounting behaviour and other issues.
I use CCC and maintain an at home and off site clone, but neither CCC nor SuperDuper really replace TM as a file backup system. TM is ideally suited for finding and restoring specific files, or really, specific versions or time points of specific files. CCC/SuperDuper are single time point clones of your entire system - not really the same thing or useful in the same ways as TM.
Relying on a drive that you know has problems or issues that are likely or known to be tied to the actual hardware&firmware of the drive itself is a disaster waiting to happen. I would never trust any backup solution to such a device, and would bite the bullet and buy a drive that was, in fact, a reliable hardware device instead.
I've been using a 1TB WD My Book USB2 drive for TM for several years (so OS X 7,8 and up) without any errors or problems with mounting on reboot or after ejection (my clones are on portable firewire bus-powered drives). Had it ever shown any such issues, I would have stopped using it and gone to something that did not cause such problems - an unreliable backup volume or drive is an unreliable backup, period.
It is also generally considered a "best practice" to use your backup drives for nothing but that - backups. A dedicated backup drive is far preferable than a backup volume on a drive that sees all sorts of alternate uses as well - using a drive for both backup and general file use just increases the chance of some logical or physical error leading to the loss of the entire drive's contents. -
What Should I See Entering Time Machine?
I am using a Lacie 500 gig external drive to retain Time Machine backups. Everything appears to work properly. On entering Time Machine, I see only the contents of my 'Desktop' (except the Mac HD and Lacie HD) and nothing else.
Is this as it should be, or should I be able to access files/data not on my desktop?
In Time Machine settings, I have excluded backup of the Lacie drive itself, otherwise I have confirmed everything is actually backed up by examining the Lacie HD backup itself.
What if anything am I missing here?With no open Finder windows and all other apps hidden, what I see when I click the TM icon in the dock is a column-view Finder window with Desktop selected in the sidebar, and receding windows backward in time. Is that what you see?
The if I click another sidebar item, such as my home (user) folder, or Documents, I see the contents of those directories, also with receding windows.
If you click the backward arrow in the Time Machine view TM will take you back to the last time there was a change in the selected directory, one change at a time, per click. -
What is encrypting on my time machine backup
i just bought a 1T lacie external hard drive
i chose to encrypt the the back up
not sure why..it just seemed to be the prudent thing to choose
it is still encrypting the data after 7 hrs
what's going on
can i change this
should i change this
why & what is it doing?
also can i change the schedule of backups the time machine does
i really do NOT need hourly ones!!!The original backupnwith TimeMachine can be quite long and the encryption may have added more time to it. Once TimeMachine gets its initial backup it is much faster as it only addresses things that have changed. Hourly backups turn into daily backups and use less space than you might think. Let it run it's fine.
Best TimeMachine primer ever:
Pondini's Time Machine FAQ -
How do I fix Time Machine from crashing in mountain lion
Hi,
I recently had to wipe my SSD on my rMBP as I couldn't partition the drive in order to install Bootcamp. I managed to eventually erase the drive and setup a new partition for Windows. I then reinstalled Mountain Lion via the internet and hooked the computer up to my Time Capsual to do the restore. Restore did not restore to my latest backup and when I go to time machine to do a restore I am getting 2 things happen:
1) Dates of retre points are all listed in Purple.
2) Unable to select any of these dates as the software appears to freeze.
Anyone know why this is happening?
ThanksAnother option to check your backups is through the Finder window.
Connect the external HD to Mac - or connect to the IP address where the HD is connected to (GO-Connect to Server).
-In the HD you will find the backups.backups folder - folder of your Mac - folders of each back up. -
Where can I find what the error messages of Time Machine means?
Checking my System Log Queries I found the following:
Could not back up OS X Recovery to /Volumes/Backup2/Backups.backupdb: Error Domain=NSOSStatusErrorDomain Code=-10 "Could not create com.apple.Boot.plist for recovery set" (kCFURLUnknownError / dsMacsBugInstalled: ) UserInfo=0x7fed8b312100 {NSLocalizedDescription=Could not create com.apple.Boot.plist for recovery set}
Can anyone explain what this means, and is it "fatal" in such a way that the backup made is useless for restoring? Where can I find documentation for such messages?
HansI reinstalled OS X just as you recommended. It seems that the error message concerning the Recovery set changed:
25/04/15 16:17:52,246 storedownloadd[491]: DownloadServiceDelegate: Accepting new connection <NSXPCConnection: 0x7ff598500fa0> connection from pid 487 with interface <DownloadServiceInterface: 0x7ff598506b50> (PID 487)
25/04/15 16:17:59,751 com.apple.backupd[403]: Starting automatic backup
25/04/15 16:17:59,995 com.apple.backupd[403]: Backing up to /dev/disk2s2: /Volumes/Backup2/Backups.backupdb
25/04/15 16:18:00,806 com.apple.backupd[403]: Event store UUIDs don't match for volume: SSD Boot
25/04/15 16:18:01,454 com.apple.backupd[403]: Deep event scan at path:/ reason:must scan subdirs|new event db|
25/04/15 16:18:01,455 com.apple.backupd[403]: Running event scan
25/04/15 16:18:30,853 mdworker[532]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"
25/04/15 16:18:30,983 mdworker[532]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"
25/04/15 16:18:32,812 com.apple.xpc.launchd[1]: (com.apple.imdmessageservices.IMDMessageServicesAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
25/04/15 16:18:32,812 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
25/04/15 16:18:50,000 kernel[0]: process MacsFanControl[451] caught causing excessive wakeups. Observed wakeups rate (per sec): 641; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45544
25/04/15 16:18:50,539 com.apple.xpc.launchd[1]: (com.apple.ReportCrash[559]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
25/04/15 16:18:50,540 ReportCrash[559]: Invoking spindump for pid=451 wakeups_rate=641 duration=71 because of excessive wakeups
25/04/15 16:18:53,089 spindump[560]: Saved wakeups_resource.diag report for MacsFanControl version 1.2.1.0 (???) to /Library/Logs/DiagnosticReports/MacsFanControl_2015-04-25-161853_iMac-van-Hans. wakeups_resource.diag
25/04/15 16:19:18,278 com.apple.backupd[403]: Finished scan
25/04/15 16:19:18,770 com.apple.backupd[403]: Saved event cache at /Volumes/Backup2/Backups.backupdb/iMac van Hans/2015-04-25-161800.inProgress/C8A10FE4-5356-4E21-81A5-6E3F9C14FF93/.F999C86 6-1B71-3466-8990-9540C593C08A.eventdb
25/04/15 16:19:18,868 com.apple.backupd[403]: Not using file event preflight for SSD Boot
25/04/15 16:20:22,939 com.apple.backupd[403]: Will copy (769 bytes) from USERS1
25/04/15 16:20:22,950 com.apple.backupd[403]: Found 423386 files (11,49 GB) needing backup
25/04/15 16:20:23,207 com.apple.backupd[403]: 19,66 GB required (including padding), 1,41 TB available
25/04/15 16:20:50,187 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
25/04/15 16:20:51,554 cloudphotosd[663]: Unable to register with launch services, result = -10819
25/04/15 16:20:51,588 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
25/04/15 16:20:54,027 cloudphotosd[663]: +[CSLogger preferencesChanged:] reconfiguring logging
25/04/15 16:20:54,244 cloudphotosd[663]: Determine service transition start: service=com.apple.photo.icloud.myphotostream personId=1353114644 lastKnownPersonId=(null) targetState=-1
25/04/15 16:20:54,244 cloudphotosd[663]: Determine service transition end: 2, currentState: 3, shouldEnableService: 0
25/04/15 16:20:54,566 cloudphotosd[663]: Determine service transition start: service=com.apple.photo.icloud.sharedstreams personId=1353114644 lastKnownPersonId=(null) targetState=-1
25/04/15 16:20:54,566 cloudphotosd[663]: Determine service transition end: 2, currentState: 3, shouldEnableService: 0
25/04/15 16:20:55,464 cloudphotosd[663]: Determine service transition start: service=com.apple.photo.icloud.cloudphoto personId=1353114644 lastKnownPersonId=(null) targetState=0
25/04/15 16:20:55,464 cloudphotosd[663]: Determine service transition end: 2, currentState: 3, shouldEnableService: 0
25/04/15 16:20:56,548 cloudphotosd[663]: New connection request from 666
25/04/15 16:20:57,767 com.apple.photomoments[672]: Photomoments process awakened.
25/04/15 16:20:57,956 com.apple.photomoments[672]: Connection error while checking Apple Internalness. Error: Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper application." (The connection to service named com.apple.CrashReporterSupportHelper was invalidated.) UserInfo=0x7f92a143c050 {NSDebugDescription=The connection to service named com.apple.CrashReporterSupportHelper was invalidated.}
25/04/15 16:20:58,164 sandboxd[323]: ([672]) com.apple.photom(672) deny mach-lookup com.apple.CrashReporterSupportHelper
25/04/15 16:20:58,000 kernel[0]: process backupd[403] thread 9125 caught burning CPU! It used more than 50% CPU (Actual recent usage: 50%) over 180 seconds. thread lifetime cpu usage 90.873877 seconds, (42.019109 user, 48.854768 system) ledger info: balance: 90016080142 credit: 90016080142 debit: 0 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 179260947065
25/04/15 16:20:58,968 com.apple.xpc.launchd[1]: (com.apple.ReportCrash.Root[677]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash.DirectoryService
25/04/15 16:20:59,150 com.apple.geod[675]: Connection error while checking Apple Internalness. Error: Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper application." (The connection to service named com.apple.CrashReporterSupportHelper was invalidated.) UserInfo=0x7f90e9700130 {NSDebugDescription=The connection to service named com.apple.CrashReporterSupportHelper was invalidated.}
25/04/15 16:20:59,160 sandboxd[323]: ([675]) com.apple.geod(675) deny mach-lookup com.apple.CrashReporterSupportHelper
25/04/15 16:20:59,367 spindump[560]: Saved cpu_resource.diag report for backupd version ??? (???) to /Library/Logs/DiagnosticReports/backupd_2015-04-25-162059_iMac-van-Hans.cpu_res ource.diag
25/04/15 16:21:56,492 mdworker[738]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"
25/04/15 16:21:56,620 mdworker[738]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"
25/04/15 16:23:29,049 com.apple.backupd-helper[68]: Not starting scheduled Time Machine backup: Backup already running
25/04/15 16:23:39,154 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
25/04/15 16:23:39,795 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
25/04/15 16:29:15,765 com.apple.xpc.launchd[1]: (com.apple.DataDetectorsDynamicData) The JoinExistingSession key is only available to Application services.
25/04/15 16:29:15,766 com.apple.xpc.launchd[1]: (com.apple.appkit.xpc.sandboxedServiceRunner) The JoinExistingSession key is only available to Application services.
25/04/15 16:29:31,510 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
25/04/15 16:29:35,483 mdworker[293]: SCNetworkReachability server not available
25/04/15 16:29:35,484 mdworker[293]: SCNetworkReachability server not available
25/04/15 16:29:35,487 mdworker[293]: bootstrap_look_up2 failed with 0x44c
25/04/15 16:29:35,487 mdworker[293]: IOPMConnectionCreate failed, 0xe00002c9
25/04/15 16:29:35,719 sandboxd[323]: ([293]) mdworker(293) deny mach-lookup com.apple.SystemConfiguration.SCNetworkReachability (import fstype:hfs fsflag:480D000 flags:5E diag:0 isXCode:0 uti:public.html plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 2310261)
25/04/15 16:29:35,754 sandboxd[323]: ([293]) mdworker(293) deny mach-lookup com.apple.PowerManagement.control (import fstype:hfs fsflag:480D000 flags:5E diag:0 isXCode:0 uti:public.html plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 2310261)
25/04/15 16:31:03,369 com.apple.backupd[403]: Copied 223515 items (1,65 GB) from volume SSD Boot. Linked 210906.
25/04/15 16:31:32,355 com.apple.backupd[403]: Copied 14 items (861 bytes) from volume USERS1. Linked 119.
25/04/15 16:31:35,323 com.apple.backupd[403]: Created new backup: 2015-04-25-163135
25/04/15 16:31:35,517 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
25/04/15 16:31:35,000 kernel[0]: hfs: mounted Recovery HD on device disk0s3
25/04/15 16:31:35,871 mds[57]: (Volume.Normal:2464) volume:0x7fb9c213e000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Recovery HD
25/04/15 16:31:35,918 fseventsd[44]: Logging disabled completely for device:1: /Volumes/Recovery HD
25/04/15 16:31:35,932 com.apple.backupd[403]: Copying OS X Recovery set
25/04/15 16:31:59,320 mdworker[290]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,320 mdworker[292]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,322 mdworker[293]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,328 mdworker[291]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,330 mdworker[885]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,334 mdworker[294]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,334 mdworker[295]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,335 mdworker[296]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,337 mdworker[297]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,337 mdworker[530]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,339 mdworker[788]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,339 mdworker[327]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,340 mdworker32[1077]: (ImportBailout.Error:1325) Asked to exit for Diskarb
25/04/15 16:31:59,000 kernel[0]: hfs: unmount initiated on Recovery HD on device disk0s3
25/04/15 16:32:00,119 com.apple.backupd[403]: Starting post-backup thinning
25/04/15 16:32:00,120 com.apple.backupd[403]: No post-backup thinning needed: no expired backups exist
25/04/15 16:32:00,133 com.apple.backupd[403]: Backup completed successfully.
25/04/15 16:32:44,591 WindowServer[181]: CGXGetConnectionProperty: Invalid connection 54279
Am I wrong or is the recovery set still " under fire"? -
What's the point of Time Machine
After clearing up this 10.5.6 bug on Time Machine it got me wondering what the benefit of TM really is. I am a photographer dealing with large files but I never work on a single photo for more then one hour. My method of backing up is simple... download raw images from the CF card to the OS disk that I'll be working from as well as to two internal HD backup disks. As I work I put finished photos in a "finals" folder that is copied onto the backups as I go along. Indeed if the OS disk goes down while I'm working I have the raw files on two backups plus the finals folder as I may have backed up in that time frame. I understand TM will provide me with a fall back to previous edits of a single image but even so, this seems like a waste of a hard drive and perhaps more trouble than it's worth for the small effort to drag and drop occasionally. Perhaps TM is better for video work or am I missing something elemental here?
Carl,
CarlKramer wrote:
Excellent info, thanks. Two questions about the post.
How do I "flush" data of a backup HD to de-frag it?
Easy. Copy all the data to a second drive or volume, delete it from the first, then copy it back (or not). The most logical scenario is one where "live" data (that which is being edited or otherwise managed) is kept on one drive temporarily. When it reaches a state where the files will remain "static" in the future, those files are copied to the second drive/volume and deleted from the first. Since files will be written to the second "archival" drive sequentially, then never modified or moved again, fragmentation will always remain at essentially zero for that drive.
Fragmentation on the first drive will be eliminated when all data is removed from it. Alternatively, the volume can just be formatted (erased), but this isn't necessary.
Lets say I get a disk error and my boot system goes down. If I have been backing up the boot drive to an external with TM, what are the steps I would take to get total recovery?
A "Full Restore" is a function of the Leopard installer. Boot to the installation disk, then open the installer's "Utilities" menu. "Restore from a Time Machine Backup" is at the bottom of the menu. You are asked to connect the backup drive. When it is mounted, it is scanned for valid backups. A list appears, and you choose which backup you would like to restore (presumably the most recent, but you can choose any that exist). You then choose a destination for the installation. When it has been restored, the machine reboots to the restored installation ad you're back up & running.
Unlike a "normal" installation of OS X, restoring a backup is dependent only on the direct transfer speed from the backup drive. Where a bare installation of Leopard might take as long as 2 hours, a restoration of Leopard plus all applications and user data takes only minutes (in my case, 45).
You would normally be using this feature after having used Disk Utility (in the same menu) to erase the faulty startup drive. However, it can also be used, and quite handily, to move an installation from one drive or machine to another.
Scott
P.S. If fragmentation on a startup disk becomes and issue (rare with OS X, but it can happen with the types of file mentioned earlier), restoring from a Time Machine backup after an erasure can be an excellent solution! -s
Maybe you are looking for
-
Since Upgrading the software on my Iphone 3GS to the iOS5, I have not been able to back up my on my laptop, it starts syncing then kicks me out. I have uninstalled my internet security and that is not the problem (so re-installed) I have updated the
-
How can I get Web Sharing to work?
I am having trouble getting web sharing to work - the name for the folder is a NetBIOS name which I can't change - and that is the first part of the problem. Is this a known issue because I have tried it on several computers and it does not work like
-
Signal recovery 7225 lock-in - Dumping curve buffer issue
Hi there I am programming an experiment that requires me to take data fast using the curve buffer of my lock-in amplifier (Signal Recovery 7225). I have been using the supplied vi files in labview, but seem to be having a problem with the read buffe
-
Error when release account plan via CRM_ACC_PL
Hi expert, Getting error 'Overlapping validity periods for two condition records' when release account plan via CRM_ACC_PL. Any idea what caused this error? Cheers.
-
I'm not the type to complain and it's not directed at Verizon but, the Verizon store I typically shop at. I've always had good customer service at Verizon on line or, over the phone but, the store, it's a whole different story. We have three phones o