Why does Time Machine run continually?
I moved from Snow Leopard to Lion last week, and also converted my MobileMe account to iCloud. It has now been seven days and Time Machine appears to have never stopped backing up. To be more precise, it appears that as soon as it completes one back up, it immediately starts on a new one. My Time Machine drive is an external 750 GB connected by FW800. Time Machine estimates the size of a full backup at 132.66 GB. The Bootcamp partition on my 320 GB internal drive and the external Time Machine drive are excluded from the backups. Looking at the Star Wars screen in Time Machine shows that it has made two backups per day since the move, so I don't think it is still making the initial full back up due to the OS upgrade.
Is this normal? If not, what may be causing Time Machine to run continually? It did not behave in this way with Snow Leopard and previous versions of OS X.
Thanks for any advice.
Hi, and welcome to the forums.
It sounds like you may have either or both of the following:
Your backups are too large. Something is being backed-up often, or every time, that is taking a lot of time and disk space. See #D4 in the Time Machine - Troubleshooting *User Tip* at the top of this forum.
Your backups are running too slowly, for one or more reasons. See #D2 in the Troubleshooting Tip.
Similar Messages
-
Why does Time Machine disappear?
Why does Time Machine disappear each restart?
Suggest that you power cycle the entire network, as things are likely out of sequence
Power every device off on the network, order is not important
Wait a few moments, then start the modem first and let it run by itself for 2-3 minutes
Start the Time Capsule the same way
Start each network device one at a time about a minute apart
Check for proper operation -
Why does Time Machine Hang OSX when a USB drive does not respond?
I use USB drives to store photo data. When I back up the drives using Time Machine to a Time Capsule, If I have added a large amount of data to the USB drive, the backup will consistently fail with the drive hung. I can see the drive in finder, but I cannot see the directory structure. Often OSX hangs too and I cannot even get to finder, just the whirling colored wheel. Sometimes the system has entered sleep mode and it will not wake up. I if I am using the monitor, I can open the MAC Book Pro cover and the screen there shows alternately, a blue screen and the screen wallpaper, flipping back and forth but otherwise unresponsive. If I turn the USB drive off the OS recovers and Time Machine completes, usually indicating a backup failure (but not always). The drive is always very hot under these circumstances, indicating that the system is issuing repetitive operations to the drive. I should emphasize that I am not writing to the USB drives during backup, Time Machine is just reading the drive. So several questions:
1) How in the world can a non system drive hang the Operating System? This is a big no-no for a supposedly multi-tasking Operating System.
2) I use Aperture 2.1 to store data on the USB drives with no problems (at least so far). Why would Time Machine drive the USB drive so hard that it fails? I had the same problem using a USB drive with iTunes. It completely fried the drive by writing to it too intensively during one of the frequent software updates. Is there no throttle mechanism in OSX that limits the disc activity so that the throttle mechanism is not the failure of the drive itself?
3) Does Apple have a list of USB drives that it has validated to be able to work with it's system reliably?Are the USB drives powered from the computer or do they have their own power supplies.
There is a limit to how much power can be drawn from each USB port and also a total limit. If you exceed this, unexpected things can happen. -
Why does time machine go back less than a month?
clearly, i'm doing something wrong...
i'm in the process of cleaning up stuff from my external drives. sometime in the fall, i switched my time machine backup to a larger drive. i did my best to follow the instructions for transferring over a time machine backup, and it didn't work. i still have the old TM database, but time machine wouldn't recognize it. so i lived with it and got on with my life, starting a new TM backup.
today, i just realized that it goes back less than a month. what is THAT about? before you ask, it's NOT a disk space issue. on a 2 TB drive, i currently have 1.23 TB of available space. there's plenty of ROOM for further backups, but it's just not keeping them. please help... i love time machine, and it's saved my bacon on a number of different occasions. but on many of those occasions, i had to go back quite a bit further than 3 weeks to restore what i needed. if that's all i'm going to get from time machine, it's usefulness to me is slashed by about 80%.Time Machine automatically deletes older snapshots to make room for new ones. If your backup history is shorter than you expect, it may be because you're backing up one or more large files frequently.
Virtualization software such as VMware, Parallels, or VirtualBox creates a large virtual-disk container that is constantly changing, so it has to be backed up every time Time Machine runs. That will quickly fill up any backup destination.
You should exclude the virtual-disk file(s) from your Time Machine backups. To do that, click the Options button in the Time Machine preference pane. You may also be able to do it in the virtualization app's settings. Back up the files on the virtual disk from within the guest system, using a native backup application.
A compromise solution is to create a "snapshot" of the virtual machine in the virtualization software (not a Time Machine snapshot.) That will give you a single large file that never changes and only has to be backed up once. All the subsequent changes will be stored in a new file that's initially much smaller, but will grow over time. You should still exclude that file from TM backup. If you ever need to restore the VM from Time Machine, you'll have a working setup, which will make it easy for you to restore the rest of the data from within the guest system.
Another common cause of large TM snapshots is native OS X disk images. If you store a lot of data on one or more writable disk images, they should be in "sparsebundle" format, which will be backed up much more efficiently than any other format. A sparsebundle will not be backed up at all while the image is mounted. Make sure you unmount the image often so it can be backed up. Consider eliminating large read/write disk images from your workflow, if possible. -
Why does time machine not work?
First time machine was continually backing up, or not. Icon wouldn't respond. Started up on my Snow Leopard disk and it supposedly fixed the problem with disk utility. Now it will open time machine, but it doesn't work. I can't get a responce from the callender ot arrows. Then I have to command, option, esc to get out. Any help? It's 10.6.8.
http://pondini.org/TM/Troubleshooting.html
-
USB hard drive used with Time Machine runs continually
I have a USB SATA external hard drive that I am using for my Time Machine backups. The drive is configured to run on USB power. The drive begins running as soon as it is connected to the port, and runs continually, as long as it is connected. I expected the drive to sleep between TM backups, to save the moving parts. Is there any way to keep the drive sleeping until a TM backup is done, and then go back to sleep?
Kenneth Mclauchlan wrote:
I have a USB SATA external hard drive that I am using for my Time Machine backups. The drive is configured to run on USB power. The drive begins running as soon as it is connected to the port, and runs continually, as long as it is connected. I expected the drive to sleep between TM backups, to save the moving parts. Is there any way to keep the drive sleeping until a TM backup is done, and then go back to sleep?
I believe that is up to the drive manufacturer. In the Preferences Energy Saver see if you have checked "put drive to sleep when possible" and see if the external drive sleeps when you put the computer to sleep. If it does not then it's not a "sleeper." Even if it does, it may not have an internal clock or switch to sleep after so many minutes of inactivity.
Can you use the drive with external power? See if that does anything.
My LaCie d2 quadro sleeps between backups. I don't use USB, I use FW800. -
I'm running OS 10.6.8 on an imac from around 2011. I back up with Time Machine to an external hard drive that has about 500 GB. Until now, I've had no problemsm, or at least that's what I thought. But today I'm getting a message every hour saying "Time machine is unable to back up because the disk is full." It IS full, but Time Machine is supposed to delete the oldest backups when that happens, and keep deleting them in order.
Anyway, when I opened up my backup disk I discovered backups from February and most of March, nothing in April and nothing in May.
I'm a little freaked.
Does anybody know why that would happen and what to do about it?
Thanks in advance.Hello, I don't use TM, but...
Have you looked through Pondini's extensive TM help site?
http://Pondini.org/TM/FAQ.html
http://pondini.org/TM/Troubleshooting.html
Can't imagine something not being covered there. -
Why does time machine backup fail, error type -1
We have two Macbooks (2009 and 2010) running 10.6.8. My wife's computer came loaded with 10.5 and was upgraded to 10.6 while my mine came with 10.6 installed. Two months ago our time machine stopped doing backups of my wife's internal 120G(approx) hd while continuing to backup my 250G internal hd. My wife's hd was almost full so I thought that might be the problem. I replaced the hd with a much larger one but it still fails to make new backups. I was able to access the time machine to migrate information to the new hd. The time machine tries to backup but always fail to complete the backup due to a type -1 error. During the migration process I did not migrate applications in case the time mach app was corrupted. Both Macbooks are running time machine version 1.1.
The time machine tries to backup but always fail to complete the backup due to a type -1 error.
There are various things that can cause this error, so there are various solutions.
For some possible solutions, see #C17 in Time Machine guru Pondini's Time Machine -- Troubleshooting.
http://pondini.org/TM/Troubleshooting.html -
I'm attempting to recover a group of lost files from Time Machine. The files are backups from a mobile app within User/LibraryMobile Documents/.
I'm able to find the lost files, but Time Machine failed to restore them after I select 'Keep Both' and then enter my Admin Password. The screen returns to the desktop and the finder window for the file I'm trying to recover, but nothing else happens.
I hope someone can help.
Bil"Time Machine in Safe Mode couldn't access any history
Why not? What happened?
I have no Idea what happened. Here is the screenshot showing no history at all, and the Console:"
2/10/2014 6:08:25.166 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[401]) Exited with code: 1
2/10/2014 6:08:25.166 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:08:28.209 am WindowServer[95]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
2/10/2014 6:08:28.337 am WindowServer[95]: Display 0x4280480 captured by conn 0xcc03
2/10/2014 6:08:29.211 am WindowServer[95]: CGXOrderWindowList: Invalid window 85 (index 0/1)
2/10/2014 6:08:35.206 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[403]) Exited with code: 1
2/10/2014 6:08:35.206 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:08:40.577 am com.apple.IconServicesAgent[308]: main Failed to composit image for binding VariantBinding [0x6a9] flags: 0x8 binding: FileInfoBinding [0x1d1] - extension: png, UTI: public.png, fileType: ????.
2/10/2014 6:08:40.578 am quicklookd[408]: 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:64 scale: 1
2/10/2014 6:08:42.209 am WindowServer[95]: disable_update_likely_unbalanced: UI updates still disabled by application "Finder" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
2/10/2014 6:08:42.209 am Finder[279]: void CGSUpdateManager::log() const: conn 0xcc03 legacy 1
2/10/2014 6:08:42.211 am Finder[279]: Backtrace (at 1618.93):
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 0 CoreGraphics 0x000000010d02b379 CGSBacktraceCreate + 59
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 1 CoreGraphics 0x000000010d0da62c _ZN16CGSUpdateManager21disable_update_legacyEv + 78
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 2 CoreGraphics 0x000000010d0da5d7 CGSDisableUpdate + 35
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 3 Finder 0x0000000107b66aae Finder + 1608366
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 4 Finder 0x0000000107b66224 Finder + 1606180
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 5 CoreFoundation 0x000000010cbb7e0c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 6 CoreFoundation 0x000000010cb79f79 ____CFXNotificationPostToken_block_invoke + 137
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 7 CoreFoundation 0x000000010cb1a48c __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 8 CoreFoundation 0x000000010cb0bae5 __CFRunLoopDoBlocks + 341
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 9 CoreFoundation 0x000000010cb0b86e __CFRunLoopRun + 1982
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 10 CoreFoundation 0x000000010cb0ae75 CFRunLoopRunSpecific + 309
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 11 HIToolbox 0x000000010a829a0d RunCurrentEventLoopInMode + 226
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 12 HIToolbox 0x000000010a8297b7 ReceiveNextEventCommon + 479
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 13 HIToolbox 0x000000010a8295bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 14 AppKit 0x000000010b7c224e _DPSNextEvent + 1434
2/10/2014 6:08:42.211 am Finder[279]: void CGSUpdateManager::log() const: 15 AppKit 0x000000010b7c189b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
2/10/2014 6:08:42.212 am Finder[279]: void CGSUpdateManager::log() const: 16 AppKit 0x000000010b7b599c -[NSApplication run] + 553
2/10/2014 6:08:42.212 am Finder[279]: void CGSUpdateManager::log() const: 17 AppKit 0x000000010b7a0783 NSApplicationMain + 940
2/10/2014 6:08:42.212 am Finder[279]: void CGSUpdateManager::log() const: 18 Finder 0x00000001079e4730 Finder + 26416
2/10/2014 6:08:42.212 am Finder[279]: void CGSUpdateManager::log() const: 19 libdyld.dylib 0x000000010df545fd start + 1
2/10/2014 6:08:42.212 am Finder[279]: void CGSUpdateManager::log() const: 20 ??? 0x0000000000000001 0x0 + 1
2/10/2014 6:08:45.256 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[410]) Exited with code: 1
2/10/2014 6:08:45.256 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:08:55.346 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[411]) Exited with code: 1
2/10/2014 6:08:55.346 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:09:05.431 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[412]) Exited with code: 1
2/10/2014 6:09:05.431 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:09:15.480 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[413]) Exited with code: 1
2/10/2014 6:09:15.480 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:09:24.342 am WindowServer[95]: CGXOrderWindowList: Invalid window 85 (index 0/1)
2/10/2014 6:09:25.497 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[414]) Exited with code: 1
2/10/2014 6:09:25.497 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:09:26.008 am WindowServer[95]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 58.80 seconds (server forcibly re-enabled them after 1.00 seconds)
2/10/2014 6:09:26.338 am WindowServer[95]: Display 0x4280480 released by conn 0xcc03
2/10/2014 6:09:35.517 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[415]) Exited with code: 1
2/10/2014 6:09:35.517 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:09:45.541 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart[416]) Exited with code: 1
2/10/2014 6:09:45.541 am com.apple.launchd.peruser.501[246]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
"Have you tried restoring at the folder level? so that all files in the folder are restored. As it is an incremental backup - also wait until you hear the backup drive stop spinning - as it has to find the physical files - pointing to them."
Yes, I've tried both, and waiting until the drive stops spinning:
Here is the Console list:
2/10/2014 6:28:38.742 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[995]) Exited with code: 1
2/10/2014 6:28:38.742 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:28:46.603 am WindowServer[122]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
2/10/2014 6:28:46.778 am WindowServer[122]: Display 0x4280482 captured by conn 0xe80b
2/10/2014 6:28:48.761 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1000]) Exited with code: 1
2/10/2014 6:28:48.761 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:28:49.891 am WindowServer[122]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04280482 device: 0x7f9dc1422710 isBackBuffered: 1 numComp: 3 numDisp: 3
2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
2/10/2014 6:28:55.200 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
2/10/2014 6:28:58.780 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1003]) Exited with code: 1
2/10/2014 6:28:58.780 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:29:00.603 am WindowServer[122]: disable_update_likely_unbalanced: UI updates still disabled by application "Finder" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
2/10/2014 6:29:00.604 am Finder[206]: void CGSUpdateManager::log() const: conn 0xe80b legacy 1
2/10/2014 6:29:00.605 am Finder[206]: Backtrace (at 1000.37):
2/10/2014 6:29:00.605 am Finder[206]: void CGSUpdateManager::log() const: 0 CoreGraphics 0x0000000108c65379 CGSBacktraceCreate + 59
2/10/2014 6:29:00.606 am Finder[206]: void CGSUpdateManager::log() const: 1 CoreGraphics 0x0000000108d1462c _ZN16CGSUpdateManager21disable_update_legacyEv + 78
2/10/2014 6:29:00.606 am Finder[206]: void CGSUpdateManager::log() const: 2 CoreGraphics 0x0000000108d145d7 CGSDisableUpdate + 35
2/10/2014 6:29:00.606 am Finder[206]: void CGSUpdateManager::log() const: 3 Finder 0x000000010377faae Finder + 1608366
2/10/2014 6:29:00.606 am Finder[206]: void CGSUpdateManager::log() const: 4 Finder 0x000000010377f224 Finder + 1606180
2/10/2014 6:29:00.607 am Finder[206]: void CGSUpdateManager::log() const: 5 CoreFoundation 0x00000001087f7e0c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
2/10/2014 6:29:00.607 am Finder[206]: void CGSUpdateManager::log() const: 6 CoreFoundation 0x00000001087b9f79 ____CFXNotificationPostToken_block_invoke + 137
2/10/2014 6:29:00.607 am Finder[206]: void CGSUpdateManager::log() const: 7 CoreFoundation 0x000000010875a48c __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
2/10/2014 6:29:00.608 am Finder[206]: void CGSUpdateManager::log() const: 8 CoreFoundation 0x000000010874bae5 __CFRunLoopDoBlocks + 341
2/10/2014 6:29:00.608 am Finder[206]: void CGSUpdateManager::log() const: 9 CoreFoundation 0x000000010874b86e __CFRunLoopRun + 1982
2/10/2014 6:29:00.608 am Finder[206]: void CGSUpdateManager::log() const: 10 CoreFoundation 0x000000010874ae75 CFRunLoopRunSpecific + 309
2/10/2014 6:29:00.608 am Finder[206]: void CGSUpdateManager::log() const: 11 HIToolbox 0x000000010645ea0d RunCurrentEventLoopInMode + 226
2/10/2014 6:29:00.609 am Finder[206]: void CGSUpdateManager::log() const: 12 HIToolbox 0x000000010645e7b7 ReceiveNextEventCommon + 479
2/10/2014 6:29:00.609 am Finder[206]: void CGSUpdateManager::log() const: 13 HIToolbox 0x000000010645e5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
2/10/2014 6:29:00.609 am Finder[206]: void CGSUpdateManager::log() const: 14 AppKit 0x00000001073fd24e _DPSNextEvent + 1434
2/10/2014 6:29:00.609 am Finder[206]: void CGSUpdateManager::log() const: 15 AppKit 0x00000001073fc89b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
2/10/2014 6:29:00.609 am Finder[206]: void CGSUpdateManager::log() const: 16 AppKit 0x00000001073f099c -[NSApplication run] + 553
2/10/2014 6:29:00.610 am Finder[206]: void CGSUpdateManager::log() const: 17 AppKit 0x00000001073db783 NSApplicationMain + 940
2/10/2014 6:29:00.610 am Finder[206]: void CGSUpdateManager::log() const: 18 Finder 0x00000001035fd730 Finder + 26416
2/10/2014 6:29:00.610 am Finder[206]: void CGSUpdateManager::log() const: 19 libdyld.dylib 0x0000000109b875fd start + 1
2/10/2014 6:29:00.610 am Finder[206]: void CGSUpdateManager::log() const: 20 ??? 0x0000000000000001 0x0 + 1
2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
2/10/2014 6:29:05.235 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
2/10/2014 6:29:08.798 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1008]) Exited with code: 1
2/10/2014 6:29:08.798 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:29:18.817 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1012]) Exited with code: 1
2/10/2014 6:29:18.817 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:29:24.300 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
2/10/2014 6:29:24.300 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSGetWindowType: Invalid (NULL) window
2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSGetWindowResolution: Invalid window 0x0
2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSGetWindowDepth: Invalid window
2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSLockWindowRectBits: Invalid window 0x0
2/10/2014 6:29:24.301 am MouseLocatorAgent[327]: CGSUnlockWindowBits: Invalid window 0x0
2/10/2014 6:29:28.843 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1019]) Exited with code: 1
2/10/2014 6:29:28.843 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:29:29.894 am WindowServer[122]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 44.29 seconds (server forcibly re-enabled them after 1.00 seconds)
2/10/2014 6:29:30.261 am WindowServer[122]: Display 0x4280482 released by conn 0xe80b
2/10/2014 6:29:30.382 am WindowServer[122]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04280482 device: 0x7f9dc1422710 isBackBuffered: 1 numComp: 3 numDisp: 3
2/10/2014 6:29:38.861 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1024]) Exited with code: 1
2/10/2014 6:29:38.861 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:29:48.879 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1027]) Exited with code: 1
2/10/2014 6:29:48.879 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:29:52.483 am com.apple.backupd[907]: Copied 1776 items (176.1 MB) from volume Macintosh HD iMac 21.5-inch, Late 2013. Linked 13206.
2/10/2014 6:29:58.897 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1037]) Exited with code: 1
2/10/2014 6:29:58.897 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:30:06.184 am launchservicesd[98]: Application App:"Console" asn:0x0-6b06b pid:951 refs=6 @ 0x7ff443443bd0 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x6c06c pid=1034 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100004/0x186a4 queue
2/10/2014 6:30:06.185 am WindowServer[122]: [cps/setfront] Failed setting the front application to Console, psn 0x0-0x6b06b, securitySessionID=0x186a4, err=-13066
2/10/2014 6:30:06.646 am com.apple.backupd[907]: Will copy (4.3 MB) from Macintosh HD iMac 21.5-inch, Late 2013
2/10/2014 6:30:06.647 am com.apple.backupd[907]: Found 68 files (4.3 MB) needing backup
2/10/2014 6:30:06.647 am com.apple.backupd[907]: 7.89 GB required (including padding), 133.44 GB available
2/10/2014 6:30:08.233 am iSnap[331]: Can't Retrieve Window Zoom
2/10/2014 6:30:08.579 am iSnap[331]: time out
2/10/2014 6:30:08.917 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1041]) Exited with code: 1
2/10/2014 6:30:08.917 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:30:18.448 am com.apple.appkit.xpc.openAndSavePanelService[1047]: assertion failed: 13F34: liblaunch.dylib + 25164 [A40A0C7B-3216-39B4-8AE0-B5D3BAF1DA8A]: 0x25
2/10/2014 6:30:18.934 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1049]) Exited with code: 1
2/10/2014 6:30:18.934 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
2/10/2014 6:30:18.980 am com.apple.appkit.xpc.openAndSavePanelService[1047]: Bogus event received by listener connection:
<error: 0x111766b50> { count = 1, contents =
"XPCErrorDescription" => <string: 0x111766e60> { length = 18, contents = "Connection invalid" }
2/10/2014 6:30:18.981 am librariand[219]: client process 349 does not have a valid com.apple.developer.ubiquity-container-identifiers entitlement
2/10/2014 6:30:18.982 am librariand[219]: error in handle_container_path_request: LibrarianErrorDomain/9/The client process does not have a valid com.apple.developer.ubiquity-container-identifiers entitlement
2/10/2014 6:30:20.551 am com.apple.backupd[907]: Copied 204 items (4.3 MB) from volume Macintosh HD iMac 21.5-inch, Late 2013. Linked 1778.
2/10/2014 6:30:21.935 am com.apple.backupd[907]: Created new backup: 2014-10-02-063021
2/10/2014 6:30:22.625 am launchservicesd[98]: Application App:"Monosnap" asn:0x0-28028 pid:349 refs=5 @ 0x7ff443632f50 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x6c06c pid=1034 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100004/0x186a4 queue
2/10/2014 6:30:22.625 am WindowServer[122]: [cps/setfront] Failed setting the front application to Monosnap, psn 0x0-0x28028, securitySessionID=0x186a4, err=-13066
2/10/2014 6:30:22.874 am WindowServer[122]: CGXSetWindowLevel: Operation on a window 0x236 requiring rights kCGSWindowRightPresenter by caller com.apple.appkit.xpc.openAndSav
2/10/2014 6:30:22.874 am com.apple.appkit.xpc.openAndSavePanelService[1047]: CGSSetWindowLevel
2/10/2014 6:30:22.874 am com.apple.appkit.xpc.openAndSavePanelService[1047]: PSsetwindowlevel, error setting window level (1001)
2/10/2014 6:30:24.868 am com.apple.backupd[907]: Starting post-backup thinning
2/10/2014 6:30:24.868 am com.apple.backupd[907]: No post-backup thinning needed: no expired backups exist
2/10/2014 6:30:24.898 am com.apple.backupd[907]: Backup completed successfully.
2/10/2014 6:30:25.501 am launchservicesd[98]: Application App:"Finder" asn:0x0-b00b pid:206 refs=7 @ 0x7ff443429180 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x6c06c pid=1034 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100004/0x186a4 queue
2/10/2014 6:30:25.502 am WindowServer[122]: [cps/setfront] Failed setting the front application to Finder, psn 0x0-0xb00b, securitySessionID=0x186a4, err=-13066
2/10/2014 6:30:28.952 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart[1056]) Exited with code: 1
2/10/2014 6:30:28.952 am com.apple.launchd.peruser.501[187]: (com.qbix.CalendarStart) Throttling respawn: Will start in 10 seconds
Still restores only the first 7 files of 955.
I appreciate your efforts to help. That's a lot of files that are lost! -
I'm pretty sure that upto a few months ago I had a hard disk connected via USB to my Airport Extreme and I was able to backup all the computers on my home network. However, somehow over the last few months this had stopped happening. I am not able to select my network disks for time machine backup.
There is a very unhelpful sentence on Apple's website which simply says it does not allow backup to hard disks connected to Airport Extreme via USB. Does anyone know why this is? Is there a way around this? Can I connect a drive to my desktop computer and have other computers backup through the network to that?This was never an approved configuration: OS X Mountain Lion: Disks you can use with Time Machine
Can I connect a drive to my desktop computer and have other computers backup through the network to that?
The above KB article indicates you can, though I have not personally tried it. -
Why does time machine make a second/different backup after new installing a hard drive?
Hi all,
Long time reader, first time poster...
after having to install a new hard drive on my MacBook Pro, the new Time Machine backups are not recognising the original/older backups on the external hard drive connected via network router and has created a new/second backup caller 'xxx Mac Book Pro 1' instead of updating/reading the orginal 'xxx Mac Book Pro backup'?
Does anyone know why it did this? and more importantly how do i make it recgonise the original and stop making the secondary copy?
Thanks!Hi gb69,
If you are having issues with Time Machine backups after a recent hardware change, you may find the following article helpful:
Time Machine: Troubleshooting backup issues
http://support.apple.com/kb/ht3275
Regards,
- Brenden -
Why does time machine back up change root directory of software?
about a year ago i did a time machine back up of my old macbook pro, then when i came to use a piece of software (native instruments-traktor) it said the root directory had been changed and it couldnt find the file. i had to remove the whole program from my mac and redownload it. then since then had no problems.
now ive just purchased a new macbook today and wanted all my old files and software on it so i did a migration expert with time machine. it seems to have bought most things over.....a few files are missing from logic but again when i went open traktor, again it said root directory changed,,,im not to good with these root directorys so havent got a clue what to do so again ive had to remove the program and redownload it which is a bit of a pain.
any ideas why time machine changes it??I'm also puzzled because it continually wants to back up some 15MB or more when I've changed nothing
Suggest that you download and install BackupLoupe to find out exactly what is being backed up on each pass.
soma-zone: BackupLoupe
If you want to change the backup frequency of Time Machine, an application like Time Machine Editor will allow you schedule backups whenever you like. But, you may not need to do this if you can figure out what might be causing the first issue.
TimeMachineEditor
If you ever decide to delete Time Machine Editor, be sure to change the backup frequency back to hourly before you delete the application. -
Why does Time Machine forget "everything" after Mountain Lion update?
After updating to Mountain Lion (from Snow Leopard), I fired up my trusty external hard drive which contains my Time Machine backups (and nothing else) - of course I had run a backup right before upgrading to be sure. Two things are deeply disturbing: 1) The drive keeps on "rattling" as if a process is constantly reading or writing to it - even with Time Machine "OFF". Why? I (tried to) explicitly disable(d) Spotlight searching that drive, and nothing else should be accessing it! (I wish there was a way to simply turn Spotlight OFF for a while - I suspect it of a lot of crashes I experience).
Anyway, even more disturbing: Opening the System Preference Panel and sliding Time Machine to "On", it claims there is NO backup at all! Oldest backup: "NONE". Latest backup: "NONE". This is B.S.! BTW, opening the "Time Machine" app proper shows all the recent backups, so they are still there. So why doesn't the Time Machine Preference Panel not recognize them? Under these circumstances, is it safe to enable backups??? I am very afraid that if I let Time Machine proceed, it will try to create a full new backup, perhaps overriding all the snapshots from the past that are still stored on that disk. For one, even at 1 TB, my disk is not big enough to take another full backup on top of what's already stored on there. Any advice (other than "buy another hard disk just to be safe")?
O.k., I admit, so far I'm more upset with Mountain Lion than impressed.Dear Pondini,
I am grateful for your advice and encouraging words, but I am (and remain) at my wit's ends as far as Time Machine is concerned. While I'm sure 99.99% of Mac users have no problem, there must be SOMETHING idiosyncratic about my own setup that has consistently crashed TM in the past, and now (after upgrading to Mountain Lion), it simply refuses to work EVER. Mind you, I'm NOT a "hacker" who installs non-standard software or likes to poke around in the Kernel.
Below is a shortened version of the Console output during my latest attempt - after 3 tries (after running disk utility to repair my permissions and check the hard drive), it never makes it beyond about 4 Gb before crashing. (And, what's worse, if I don't immediately react, TM very often crashes the whole computer to the point where NOTHING works anymore - requiring a restart. Even with Mountain Lion).
Thanks for any offer of help from anyone... SK
THIS WAS RIGHT BEFORE I TRIED TO START THE BACKUP
7/30/12 12:42:46.697 PM WindowServer[73]: [cps/setfront] Failed setting the front application to Finder, psn 0x0-0xc00c, securitySessionID=0x186a4, err=-13066 _
7/30/12 12:46:53.815 PM UserEventAgent[180]: com.apple.TMLaunchAgent disabled
NONE OF THE ABOVE WAS IN RESPONSE TO ANYTHING I DID! BUT MAYBE A CLUE?
ANYWAY, HERE GOES (with many repetitive lines removed - indicated by gaps):
7/30/12 12:48:52.885 PM com.apple.backupd[320]: Starting manual backup
7/30/12 12:48:53.475 PM com.apple.backupd[320]: Backing up to: /Volumes/TimeShare/Backups.backupdb
7/30/12 12:48:55.101 PM com.apple.backupd[320]: Event store UUIDs don't match for volume: Macintosh HD
7/30/12 12:48:55.799 PM com.apple.backupd[320]: Deep event scan at path:/ reason:must scan subdirs|new event db|
7/30/12 12:49:20.607 PM com.apple.launchd.peruser.501[156]: (com.apple.KerberosHelper.LKDCHelper[212]) Exited with code: 1
7/30/12 12:54:19.579 PM com.apple.backupd[320]: Finished scan
7/30/12 12:59:57.836 PM com.apple.backupd[320]: Found 470214 files (18.15 GB) needing backup
7/30/12 12:59:58.422 PM com.apple.backupd[320]: 24.03 GB required (including padding), 312.52 GB available
7/30/12 1:05:28.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:28.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:28.000 PM kernel[0]: jnl: disk1s2: do_jnl_io: strategy err 0x5
7/30/12 1:05:28.000 PM kernel[0]: jnl: disk1s2: write_journal_header: error writing the journal header!
7/30/12 1:05:28.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:28.693 PM com.apple.backupd[320]: Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 "The file “Credits.rtf” couldn’t be opened." UserInfo=0x7f8b749355c0 {NSURL=file://localhost/Volumes/TimeShare/Backups.backupdb/kuhn%E2%80%99s%20Mac Book%20Pro/2012-07-26-114729/Macintosh%20HD/Applications/Preview.app/Contents/Re sources/zh_TW.lproj/Credits.rtf, NSFilePath=/Volumes/TimeShare/Backups.backupdb/kuhn’s MacBook Pro/2012-07-26-114729/Macintosh HD/Applications/Preview.app/Contents/Resources/zh_TW.lproj/Credits.rtf, NSUnderlyingError=0x7f8b7493fff0 "The operation couldn’t be completed. Input/output error"}
7/30/12 1:05:28.694 PM com.apple.backupd[320]: Error: (-50) SrcErr:NO Copying /Applications/Preview.app/Contents/Resources/zh_TW.lproj/Credits.rtf to /Volumes/TimeShare/Backups.backupdb/kuhn’s MacBook Pro/2012-07-30-124855.inProgress/A9556B25-47FE-4D1F-A2C9-BF18EEF78898/Macintosh HD/Applications/Preview.app/Contents/Resources/zh_TW.lproj
7/30/12 1:05:28.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:30.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:30.341 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.341 PM com.apple.backupd[320]: Error: (-50) SrcErr:NO Copying /Applications/Preview.app/Contents/version.plist to /Volumes/TimeShare/Backups.backupdb/kuhn’s MacBook Pro/2012-07-30-124855.inProgress/A9556B25-47FE-4D1F-A2C9-BF18EEF78898/Macintosh HD/Applications/Preview.app/Contents
7/30/12 1:05:30.341 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.341 PM com.apple.backupd[320]: Error: (-50) SrcErr:NO Copying /Applications/Preview.app/Contents/XPCServices to /Volumes/TimeShare/Backups.backupdb/kuhn’s MacBook Pro/2012-07-30-124855.inProgress/A9556B25-47FE-4D1F-A2C9-BF18EEF78898/Macintosh HD/Applications/Preview.app/Contents
7/30/12 1:05:30.381 PM com.apple.backupd[320]: Stopping backup.
7/30/12 1:05:30.381 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.381 PM com.apple.backupd[320]: Error: (-8062) SrcErr:NO Copying /Applications/Preview.app/Contents/XPCServices/com.apple.Preview.TrustedBookmar ksService.xpc/Contents/_CodeSignature/CodeResources to (null)
7/30/12 1:05:30.385 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.386 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.386 PM com.apple.backupd[320]: Copied 96604 files (2.26 GB) from volume Macintosh HD.
7/30/12 1:05:30.386 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.387 PM com.apple.backupd[320]: Copy stage failed with error:11
7/30/12 1:05:30.389 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:30.464 PM com.apple.backupd[320]: Error: (5) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/TimeShare/Backups.backupdb/kuhn’s MacBook Pro/2011-06-14-140802
7/30/12 1:05:30.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:31.178 PM com.apple.backupd[320]: Error: (5) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/TimeShare/Backups.backupdb/kuhn’s MacBook Pro/2012-07-26-114729
7/30/12 1:05:31.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:31.248 PM com.apple.backupd[320]: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TimeShare/Backups.backupdb/kuhn’s MacBook Pro size:37
7/30/12 1:05:41.526 PM com.apple.backupd[320]: Backup failed with error: 11
7/30/12 1:09:42.396 PM mtmfs[37]: filesystem unmount attempted from stopFS
7/30/12 1:09:42.557 PM mtmfs[37]: unmount failed for /Volumes/MobileBackups
NOTE THE FAILURE TO UNMOUNT
7/30/12 1:10:02.499 PM fseventsd[48]: disk logger: failed to open output file /Volumes/TimeShare/.fseventsd/636573369d318daf (Invalid argument). mount point /Volumes/TimeShare/.fseventsd
7/30/12 1:10:04.000 PM kernel[0]: disk1s2: I/O error.
HERE I USED "FORCE EJECT"
7/30/12 1:10:04.799 PM fseventsd[48]: disk logger: failed to open output file /Volumes/TimeShare/.fseventsd/636573369d318daf (Invalid argument). mount point /Volumes/TimeShare/.fseventsd
7/30/12 1:10:05.000 PM kernel[0]: jnl: disk1s2: close: journal 0xffffff8042d1bcc0, is invalid. aborting outstanding transactions -
Why does Time Machine not work over wifi but only via ethernet cable ?
Hi everyone,
It's been some time I have this problem now.
The first time I backed up my mac within Time Capsule with time machine, I chose to use the ethernet cable because the gigabit connection is much faster than the wifi for the first back up, but now, any time I want to update this back up, I need to connect the cable, cause "Time Machine can not connect to the Drive I picked" over wifi.
This is so annoying. Does anyone have a similar issue ?
Any solution ?
When I got this "error" I can use Utility Airport and get full access to the drive, even in finder. The only thing that doesn't work is TimeMachine connecting to the drive, even if it is detected by TimeMachine itself.
Thanks.
RiccardoTypical Yosemite.
I suggest a full reconfigure of the TC.
Follow this list..
No files are deleted on the TC doing this although you might have to repoint your laptop to the backup.
Note.. even if TM does connect it will say it is going to do a new backup.. it is only when it starts that it discovers the backup exists and increments it.
Start from a factory reset. No files are lost on the hard disk doing this.
Factory reset universal
Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
Setup the TC again.
Then redo the setup from the computer with Yosemite.
1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
eg TCgen5 for basestation and and TCwifi wireless name.
If the issue is wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round. ie plan on a first and second round of changes to fix this.. hopefully.. I will point out other steps that can be round2.
2. Use all passwords that also comply with 1. but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
3. If the TC is main router you can skip this point. This is only an issue when the TC is bridged.
Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking.
4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
5. Mount the TC disk in the computer manually.
In Finder, Go, Connect to server from the top menu,
Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only. Do the same for ethernet if you use it.
There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
You might need to do some more work on the computer itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
Tell us how you go.
Someone posted a solution.. See this thread.
Macbook can't find Time Capsule anymore
Start from the bottom and work up.. I have a list of good network practice changes but I have avoided Yosemites bug heaven.
Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/ -
Why does Time Machine take forever?
Just using Time Machine for the first time today. It's been running for nearly four and half hours, only displaying "Indexing backup..." with no progress indication at all. Does it really take this monumentally long the first time you use it?
Sorry if this question is redundant... I find the new Apple discussions board absolutely horrible to use... use to be super easy to search thru previous posts but it seems like the new search function can't find anything. (Another case of a company fixing something that wasn't broken and ruining it in the process.)peteratomic wrote:
Just using Time Machine for the first time today. It's been running for nearly four and half hours, only displaying "Indexing backup..." with no progress indication at all. Does it really take this monumentally long the first time you use it?
Yes. It must copy the entire contents of your hard drive to the backup. Are you backing up to a networked drive like a Time Capsule? If so, it will take even longer. Don't bother trying it without connecting via ethernet cable first. Event then it will take overnight. Subsequent backups are very small and will work fine over WiFi, even faster with a directly connected disk.
Sorry if this question is redundant... I find the new Apple discussions board absolutely horrible to use... use to be super easy to search thru previous posts but it seems like the new search function can't find anything. (Another case of a company fixing something that wasn't broken and ruining it in the process.)
Apple doesn't bother trying to be everything to everyone. They make the best products they can in what they think is the best way. If you think that is horrible and broken, you are free to go elsewhere. Searching for this topic is definitely something I would consider super easty. I was quite familiar with the old system and the old search engine. It was profoundly broken and useless.
Maybe you are looking for
-
I can't delete an item in my shopping cart.
I have tried to click on the x beside the buy symbol and also highlighted the item and push the delete key and neither one will delete it. I added a song today and then deleted it and it worked just fine but this one will not go away. Can someone hel
-
Hi all, this is my scenario: I've created a query with input variable for characteristic Year/Month (0CALMONTH), in columns i added a key figure and in rows i added the characteristic 0CALDAY. The result looks someting like this: Varibale entry: 09.2
-
I'm trying to set up video conferencing with my parents and in-laws so they can see their new grandchild. Both sets of parents are PC'ers. I can't get the video to connect. Audio and chatting works. Does iChat work with a DSL line? PLease help, the g
-
Why is a boolean sometimes a variant?
All; I have a latch-when-released boolean control on my front panel, when I create a property mode and select either the "value" or "value (signaling)" property, it shows up as the purple variant type -- not the green boolean type I'm so familiar wit
-
Why does the light go dark at the bottom of my screen
Why is the bottom of my screen suddenly darker than the main part of the screen?