Airtunes hangs when time machine starts

Hi,
I have got one time capsule with one airport express. On snow leopard (10.6.2), I've configured time machine on time capsule. As soon as time machine starts (every 1 hour), airtunes hangs. I guess this is due to some QoS misconfiguration. But I haven't found anything about it. Does anyone has got any idea/fix to limit those hangs ?
Regards
Marc

I'm having a very similar problem and it is detrimental.
Here is the scenario: I have a 1TB Time Capsule as my primary router. I am able to perform backups on all but one of my machines. My iMac backs up via 1GB ethernet to the TC, my MacBookAir (60GB,SS) backs up via wireless N (270mb) and my other MacBookAir (80GB,IDE) also backs up via wireless N without any problems.
I used to use a 500mb external drive to backup my iMac but outgrew it, so I started backing up to the TC instead. No problems at all.
I also used to back up my Intel MacMini running Mac OS X Server 10.5.5 to a similar external hard-drive but haven't in a while.
I decided it finally made sense to backup ALL my Mac's to the same 1TB TimeCapsule but it's just not working out!
On the MacMini; I turn on TimeMachine, the TimeCapsule has been chosen as a backup location, it prepares backup for a moment, mounts the backup drive and then appears to begin backup up... No...! First I get a message the the TimeCapsule closed the connection, next I lose Internet connection across my entire network both wired and wireless and then the TimeCapsule light turns amber, flashes and essentially does a completel crash / reset and then comes back to life a few moments later. I can backup any other computer except the MacMini to the TimeCapsule without "crashing" it and it makes no sense! Every computer is completely up to date with all the latest patches and the TimeCapsule is running 7.3.2
I sure hope this gets resolved, seems like other people are pretty disgusted with the performance of the TimeCapsule with problems that have no resolution.

Similar Messages

Lose internet when time machine starts backup

Title says it all. I lose internet connectivity (wireless) when time machine starts. If I turn airport on and off from the taskbar, it works and the backup completes itself.

Me too!
It used to work just fine, but ever since I upgraded to snow leopard, I was having these intermittent internet outages, and it was driving me crazy. I finally realized it was happening every time Time Machine would start up. I turned Time Machine off, and now my internet works just fine. But this is obviously not an ideal solution. I'm glad to see I'm not alone.
Anyone else having this problem??

Losing internet when time machine starts backup

is anyone losing their wireless internet connection when time machine starts its automatic backup? if so, do you know a work around?

Problem here too...it's driving me nuts! There must be a solution - but I have a feeling it'll need an airport/OS X update of some sort?

HT201250 When Time Machine starts backingup, It popsup a small window that stays up the whole time it is backingup. How can I make it do its job in the background without the popup?

When Time Machine starts backingup, It popsup a small window that stays up the whole time it is backingup. How can I make it do its job in the background without the popup?

just let it do it for the first time. actually you might want to option click the little symbol next to the time representing timemachine then click verify bacups
Message was edited by: Carlo TD

What happens when Time Machine starts to fill up a drive?

Using Time Machine on a partitioned External HD has been an absolute snap! I love the app. My main disappointment with it is that it has no literature on HOW it works, and no real ways for me to set different controls for it other than on and off.
My question is that what happens when a drive starts to get full? I have about 30 gigs left on the partition, and I am wondering what Time Machine is going to do. Does it just delete the oldest material, or does it simply fill up and tell me to look at everything on there and decide to clear it all off. I hate that I don't know what will happen.
-Jon

From what I've read (I've not gotten a drive full so I can't speak from experience), when the TM drive gets full, it will notify you that it's going to start deleting the oldest backups to make space for the new ones. This general behavior is mentioned in the Mac Help for Time Machine, though it makes no mention about notifying you before it deletes the old backups, so I'm not sure about that part.

Finder crashes when Time Machine starts backup

Hello,
My finder/computer crashes at least once or twice a day when the Time Machine backups start (there are other times where the backup will go fine). I am using a MacBook Pro, 2011 2.2 GHz i7 with 8GB of Ram. I have a 64 GB Samsung SSD drive I use for startup and applications, and a 700 GB SSD/7500 hybrid drive mounted in the Superdrive bay for docs/music/etc.
I have a 1TB WD HDD connected via USB I use for Time Machine.
Looks like there might be something amis when I am using Chrome and Time Machine in the superdrive bay SSD/HDD setup? Also some software update errors were being thrown just before the crash too.
Thanks for any help you can provide!
Peace,
Ed
Here is the console Log just before the crash through the reboot:
5/27/12 12:45:10.207 PM com.apple.SecurityServer: Failed to authorize right 'system.install.app-store-software' by client '/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/in stalld' [8335] for authorization created by '/usr/sbin/softwareupdate' [8334]
5/27/12 12:46:10.291 PM authorizationhost: SFBuiltinEntitled: softwareupdate is not entitled for system.install.app-store-software
5/27/12 12:46:10.314 PM authorizationhost: SFBuiltinEntitled: softwareupdate is not entitled for system.install.app-store-software
5/27/12 12:46:10.314 PM com.apple.SecurityServer: Failed to authorize right 'system.install.app-store-software' by client '/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/in stalld' [8345] for authorization created by '/usr/sbin/softwareupdate' [8344]
5/27/12 12:46:28.012 PM com.apple.backupd: Starting standard backup
5/27/12 12:46:28.681 PM com.apple.backupd: Backing up to: /Volumes/Big Mac Backup/Backups.backupdb
5/27/12 12:46:28.000 PM kernel: nspace-handler-set-snapshot-time: 1338147990
5/27/12 12:46:28.959 PM com.apple.mtmd: stat on /Users/edwardhilton/Library/Application Support/Google/Chrome/Default/History Index 2012-05-journal: No such file or directory
5/27/12 12:46:28.961 PM com.apple.mtmd: stat on /Users/edwardhilton/Library/Application Support/Google/Chrome/Default/History Index 2012-05-journal: No such file or directory
5/27/12 12:46:28.963 PM com.apple.mtmd: stat on /Users/edwardhilton/Library/Application Support/Google/Chrome/Default/History Index 2012-05-journal: No such file or directory
5/27/12 12:46:28.964 PM com.apple.mtmd: stat on /Users/edwardhilton/Library/Application Support/Google/Chrome/Default/History Index 2012-05-journal: No such file or directory
5/27/12 12:46:28.966 PM com.apple.mtmd: stat on /Users/edwardhilton/Library/Application Support/Google/Chrome/Default/History Index 2012-05-journal: No such file or directory
5/27/12 12:46:28.967 PM com.apple.mtmd: stat on /Users/edwardhilton/Library/Application Support/Google/Chrome/Default/History Index 2012-05-journal: No such file or directory
5/27/12 12:46:28.969 PM com.apple.mtmd: stat on /Users/edwardhilton/Library/Application Support/Google/Chrome/Default/History Index 2012-05-journal: No such file or directory
5/27/12 12:46:28.970 PM com.apple.mtmd: stat on /Users/edwardhilton/Library/Application Support/Google/Chrome/Default/History Index 2012-05-journal: No such file or directory
5/27/12 12:46:28.971 PM com.apple.mtmd: stat on /Users/edwardhilton/Library/Application Support/Google/Chrome/Default/History Index 2012-05-journal: No such file or directory
5/27/12 12:46:28.972 PM com.apple.mtmd: stat on /Users/edwardhilton/Library/Application Support/Google/Chrome/Default/History Index 2012-05-journal: No such file or directory
5/27/12 12:46:29.281 PM mds: (Error) Backup: doBackupIndexFile could not stat backup location /.MobileBackups/Computer/2012-05-27-124630/Volume/Users/edwardhilton/Library/Ap plication Support/Google/Chrome/Default/History Index 2012-05-journal /.MobileBackups/Computer/2012-05-27-124630/Volume/Users/edwardhilton/Library/Ap plication Support/Google/Chrome/Default/History Index 2012-05-journal. Error 2 with uid 0
5/27/12 12:46:30.133 PM com.apple.backupd: 3.07 GB required (including padding), 1.19 TB available
5/27/12 12:49:00.000 PM bootlog: BOOT_TIME 1338148140 0
5/27/12 12:49:02.000 PM kernel: PMAP: PCID enabled

Hi Pondini,
Thank you so much for the tips. Ive verified and repaired the HD per your guide and have turned local snapshots off. I also deleted the Chrome folder in the Library and the next time I opened the app it was rebuilt. So far so good and no crashes.
Do you have any idea what is throwing this error message? Should I be worried about multiple errors in the Console? This one is by far the most prevalent error.
Thanks!
5/28/12 3:47:27.121 PM authorizationhost: SFBuiltinEntitled: softwareupdate is not entitled for system.install.app-store-software
5/28/12 3:47:27.143 PM authorizationhost: SFBuiltinEntitled: softwareupdate is not entitled for system.install.app-store-software
5/28/12 3:47:27.143 PM com.apple.SecurityServer: Failed to authorize right 'system.install.app-store-software' by client '/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/in stalld' [6253] for authorization created by '/usr/sbin/softwareupdate' [7548]
5/28/12 3:48:27.202 PM authorizationhost: SFBuiltinEntitled: softwareupdate is not entitled for system.install.app-store-software
5/28/12 3:48:27.223 PM authorizationhost: SFBuiltinEntitled: softwareupdate is not entitled for system.install.app-store-software
5/28/12 3:48:27.223 PM com.apple.SecurityServer: Failed to authorize right 'system.install.app-store-software' by client '/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/in stalld' [6253] for authorization created by '/usr/sbin/softwareupdate' [7552]
5/28/12 3:49:27.276 PM authorizationhost: SFBuiltinEntitled: softwareupdate is not entitled for system.install.app-store-software
5/28/12 3:49:27.297 PM authorizationhost: SFBuiltinEntitled: softwareupdate is not entitled for system.install.app-store-software
5/28/12 3:49:27.298 PM com.apple.SecurityServer: Failed to authorize right 'system.install.app-store-software' by client '/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/in stalld' [6253] for authorization created by '/usr/sbin/softwareupdate' [7556]

BUG: Degraded performance, unresponsive system, syslog flooded with IOUserClient.cpp kernel errors when Time Machine starts (10.8.5 Server)

Every couple of months, my 2009 Mac Mini becomes suddenly unresponsive to Screen Sharing, Remote Desktop, AFP/SMB connections, VPN connections, and even SSH logins. It was still pingable, and the router showed many active network connections from an application that I knew was still running on it.
It is a headless machine, so the only way I can gain control is to manually reboot.
The Time Machine volume is an iSCSI target on a Synology DS412+ connected from the Mac by GlobalSAN's iSCSI Initiator v5.2.0.429. I am using iSCSI because of poor performance using Time Machine directly over AFP.
I looked at the logs this time and found a direct link between the starting of the backupd service and the appearance of these log entries. It has happened once every hour for the last 7 days.
3/11/14 2:53:37.915 AM com.apple.backupd[49366]: Starting automatic backup
3/11/14 2:53:38.067 AM com.apple.backupd[49366]: Backing up to: /Volumes/timemachine/Backups.backupdb
3/11/14 2:53:39.600 AM sudo[49393]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:43.960 AM sudo[49415]:     root : TTY=unknown ; PWD=/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:45.154 AM serveradmin[49437]: servermgr_swupdate[WRN]: Missing or invalid language for product items request. Using default "en".
3/11/14 2:53:46.663 AM sudo[49460]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:48.476 AM sudo[49483]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:50.759 AM sudo[49559]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:54.993 AM sudo[49581]:     root : TTY=unknown ; PWD=/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:57.799 AM serveradmin[49618]: servermgr_swupdate[WRN]: Missing or invalid language for product items request. Using default "en".
3/11/14 2:53:59.487 AM sudo[49643]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:54:01.371 AM sudo[49666]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:03.150 AM com.apple.backupd[49366]: Using file event preflight for Tardis SSD
3/11/14 2:54:03.251 AM com.apple.backupd[49366]: Will copy (128.5 MB) from Tardis SSD
3/11/14 2:54:03.259 AM com.apple.backupd[49366]: Found 216 files (128.5 MB) needing backup
3/11/14 2:54:03.283 AM com.apple.backupd[49366]: 913.2 MB required (including padding), 275.36 GB available
3/11/14 2:54:11.008 AM com.apple.backupd[49366]: Copied 2215 files (129.6 MB) from volume Tardis SSD.
3/11/14 2:54:11.037 AM com.apple.backupd[49366]: Using file event preflight for Tardis SSD
3/11/14 2:54:11.044 AM com.apple.backupd[49366]: Will copy (119 KB) from Tardis SSD
3/11/14 2:54:11.045 AM com.apple.backupd[49366]: Found 23 files (119 KB) needing backup
3/11/14 2:54:11.046 AM com.apple.backupd[49366]: 759.2 MB required (including padding), 275.23 GB available
3/11/14 2:54:13.402 AM com.apple.backupd[49366]: Copied 567 files (119 KB) from volume Tardis SSD.
3/11/14 2:54:13.589 AM com.apple.backupd[49366]: Created new backup: 2014-03-11-025413
3/11/14 2:54:14.679 AM com.apple.backupd[49366]: Starting post-backup thinning
3/11/14 2:54:18.200 AM com.apple.backupd[49366]: Deleted /Volumes/timemachine/Backups.backupdb/tardis/2014-03-10-015424 (128.9 MB)
3/11/14 2:54:18.200 AM com.apple.backupd[49366]: Post-back up thinning complete: 1 expired backups removed
3/11/14 2:54:18.582 AM com.apple.backupd[49366]: Backup completed successfully.

JoBidun wrote:
Thanks a lot for this really quick reply.
When you say: "I would though go back to 7.5.2 firmware." Do you mean a reset to factory default ?
Greetz
NO, your time capsule is running 7.6.1 but it is built with AFP following increased security for LION.. that is not required or available in Leopard.. so there is no point.. it is also not as stable on the older hardware.. at least in my experience.. I have repaired about 200 of the suckers so I do see a few.
When you select firmware update in the airport utility.. hold the option key.. all valid firmware versions for your TC then show up.. not only upgrades.. select 7.5.2 and upgrade to that.
Do a factory reset when you do it is a good idea though.. start off again.
And do reset of TM.. A4 in pondini.
See if it helps.
Oh, the TC will continually complain about needing a firmware update.. turn off automatic checking of updates.. it will still annoy you for fun every few weeks but that is better than daily.

Mac Pro freezes when Time Machine starts backup

MacPro1,1, Lion 10.7.5 (this machine won't run Mountain Lion).
Processor Name: Dual-Core Intel Xeon
Processor Speed: 3 GHz
Number of Processors: 2
Total Number of Cores: 4
L2 Cache (per Processor): 4 MB
Memory: 12 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005D.B00
SMC Version (system): 1.7f10
I'm backing up to a newer 3Tb Time Capsule. When TM backup starts other applications freeze, Force Quit is unaccessible, I have to hold down the power button to shut down. This started about a month after starting to use the Time Capsule, now 2 months old. Here's some log data from when TM starts to the shut down:
9/7/13 9:54:44.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:44.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:44.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:44.560 AM com.apple.backupd: Waiting for Spotlight to finish indexing /Volumes/Time Machine Backups/Backups.backupdb
9/7/13 9:54:45.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:45.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:45.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:45.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:46.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:46.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:46.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:46.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:47.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:47.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:47.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:47.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:48.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:48.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:48.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:48.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:49.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:49.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:49.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:49.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:50.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:50.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:50.734 AM configd: network configuration changed.
9/7/13 9:54:51.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:51.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:51.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 65.
9/7/13 9:54:51.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
9/7/13 9:54:52.031 AM configd: network configuration changed.
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:54.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: Logging in with uam 13 /Volumes/Data
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data
9/7/13 9:54:54.000 AM kernel: ASP_TCP ReplayPendingReqs: replaying slot 0 with reqID 2981 afpCmd 0xB on so 0x1e43ce68
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: get the reconnect token
9/7/13 9:54:54.443 AM SLRuntimeLoader: clip: empty path.
9/7/13 9:54:54.444 AM [0x0-0x17d17d].com.canon.SLRuntimeLoader: Sep 7 09:54:54 My-Mac-Pro-6.local SLRuntimeLoader[3031] <Error>: clip: empty path.
9/7/13 9:54:58.738 AM Address Book: Subscription request completed
9/7/13 9:55:10.581 AM [0x0-0x181181].com.apple.iTunes: 2013-09-07 09:55:10.581 The plugin 'Quartz Composer Visualizer' failed to load because it has the wrong CPU architecture for this version of iTunes. (3585)
9/7/13 9:55:22.038 AM com.apple.backupd: Starting standard backup
9/7/13 9:55:22.066 AM com.apple.backupd: Network destination already mounted at: /Volumes/Data
9/7/13 9:55:33.811 AM com.apple.backupd: Disk image already attached: /Volumes/Data/My Mac Pro (6).sparsebundle, DIHLDiskImageAttach returned: 35
9/7/13 9:55:35.601 AM com.apple.backupd: Disk image already attached: /Volumes/Data/My Mac Pro (6).sparsebundle, DIHLDiskImageAttach returned: 35
9/7/13 9:55:36.791 AM com.apple.backupd: Disk image /Volumes/Data/My Mac Pro (6).sparsebundle mounted at: /Volumes/Time Machine Backups
9/7/13 9:55:36.988 AM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
9/7/13 9:55:55.532 AM com.apple.backupd: 1.77 GB required (including padding), 1.09 TB available
9/7/13 9:57:24.944 AM com.apple.backupd: Copied 3262 files (21.5 MB) from volume Internal 1 3TB.
9/7/13 9:57:31.941 AM com.apple.backupd: 1.92 GB required (including padding), 1.09 TB available
9/7/13 9:58:02.477 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.480 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.482 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.483 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.484 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.485 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:26.993 AM com.apple.backupd: Copied 1720 files (304.1 MB) from volume Internal 1 3TB.
9/7/13 10:01:45.000 AM bootlog: BOOT_TIME 1378566105 0
9/7/13 10:01:58.767 AM fseventsd: event logs in /.fseventsd out of sync with volume. destroying old logs. (307606 12 307803)
9/7/13 10:01:59.000 AM kernel: npvhash=4095
9/7/13 10:01:59.000 AM kernel: PAE enabled

Thanks, Linc. Based on earlier posts around the same problem I assumed it was something to do with the computer. TC is up to date and restarting it seems to have corrected the problem, at least during the one TM backup that's gone since.
BTW, I have two internal 3 TB HDs, one with all content, the second which mirrors the first and is updated every night. I'm using the TC/TM as the backup to my backup. I also take a new full copy offsite weekly. Curious though, what do you think of backing up to cloud storage?

Time Capsule crashes when Time Machine starts a backup

I've not searched through the postings here to see if other people have seen a similar problem. I've not attempted to repeat the problem I've seen here so I'm not very clear about the cause.
I'm using a MacBook Pro with OS 10.5.4 connected via a network cabled directly to a Time Capsule which is connected to a DSL/Cable modem. The Time Capsule is updated with v 7.3.2 of the firmware. I've got Time Machine enabled but I'm also using the Time Capsule disk (1TB) to store photos that I've previously archived to CD. I'm in the process of copying all the data from CD to the Time Capsule.
Having copied some photo data to the Time Capsule I was trying out some photo cataloguing SW to see if it was any good (iPhoto is no good to me as I don't want to store photos on the local drive of my machine) - Kodak EasyShare v6.1. Having loaded some images into EasyShare I tried to use finder to search for the file names of some of the images to check that EasyShare was not copying images to my local drive. While I was doing this I think Time Machine tried to kick in and start doing a backup. I believe that Time Capsule crashed at this point. Finder froze and after I restarted it (via Force Quit not a re-boot) I discovered that I had no network connection and Mac OS couldn't see the Time Capsule under FInder or via AirPort Utility (the Time Machine backup also timed out and failed). Time Capsule just sat there with the disk spinning and a green light on the front as if all was OK. Actually - the disk just kept spinning (Time Capsule normally shuts down the drive after it is idle for a while). Because of this I'm pretty sure that Time Capsule had crashed.
I experimented with re-booting my Mac but still no network etc so I tried power cycling the Time Capsule and everything came back to life.
I'm guessing that my doing a search (or some other drive activity on Time Capsule) at the same time as Time Machine kicking in with a backup caused Time Capsule to crash.
Perhaps this is not a very interesting point if this problem is not repeatable but - well, I'd be interested to know if others have seen similar behavior...

I'm having a very similar problem and it is detrimental.
Here is the scenario: I have a 1TB Time Capsule as my primary router. I am able to perform backups on all but one of my machines. My iMac backs up via 1GB ethernet to the TC, my MacBookAir (60GB,SS) backs up via wireless N (270mb) and my other MacBookAir (80GB,IDE) also backs up via wireless N without any problems.
I used to use a 500mb external drive to backup my iMac but outgrew it, so I started backing up to the TC instead. No problems at all.
I also used to back up my Intel MacMini running Mac OS X Server 10.5.5 to a similar external hard-drive but haven't in a while.
I decided it finally made sense to backup ALL my Mac's to the same 1TB TimeCapsule but it's just not working out!
On the MacMini; I turn on TimeMachine, the TimeCapsule has been chosen as a backup location, it prepares backup for a moment, mounts the backup drive and then appears to begin backup up... No...! First I get a message the the TimeCapsule closed the connection, next I lose Internet connection across my entire network both wired and wireless and then the TimeCapsule light turns amber, flashes and essentially does a completel crash / reset and then comes back to life a few moments later. I can backup any other computer except the MacMini to the TimeCapsule without "crashing" it and it makes no sense! Every computer is completely up to date with all the latest patches and the TimeCapsule is running 7.3.2
I sure hope this gets resolved, seems like other people are pretty disgusted with the performance of the TimeCapsule with problems that have no resolution.

Extreme 802.11n 100BaseT - drops out when Time Machine starts -no USB disk

I've got a strrange problem I'm troubleshooting at present - symptom being that once hourly the Airport Express drops off - yellow flashing light, all DHCP connections stop etc, and then recovers after a 30 second or so period. Log shows the following:
Dec 28 07:56:47 Severity:5 Connection accepted from ::ffff:10.0.1.12/54766.
Dec 28 07:56:48 Severity:5 unloading current configuration.
Dec 28 07:57:10 Severity:5 Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
Dec 28 07:57:10 Severity:5 Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
Dec 28 07:57:10 Severity:5 Rotated TKIP group key.
Dec 28 07:57:19 Severity:5 Internet Configuration leased -- host <202.27.xxx.xxx/255.255.255.0> gateway <202.27.xxx.xxx> dns <202.27.xxx.xxx> wins lease <300> domain <home>
Dec 28 07:57:21 Severity:5 Clock synchronized to network time server time.asia.apple.com (adjusted +0 seconds).
Dec 28 07:57:25 Severity:5 (WAN) link state is Up.
The machine 10.0.1.12 is my Leopard server, which is backing up using time machine hourly (xx.56ish) to a firewire connected disk. Steps I've taken to troubleshoot include:
Removing the USB connected disk on the Airport Extreme - no change
Switiching the Airport Extreme to a different power supply board - no change
Rebooting the Airport Extreme, setting up an additional profile - no change
Note that the server is connceted to the base station by ethernet, not wifi. 6 or so other machines are connected by wifi, and a printer is also connected by ethernet.
Is anyone seeing anything similar? Most disruptive behaviour!

Gullah Betty wrote:
The young man had me to click on the internet tab of my time capsule (the one next to the airport tab). He then had me click on the TCP/IP tab and change the DNS Server.
That makes sense, although it could have been hoped that your ISP's DHCP server would have supplied the Time Capsule with the correct DNS value(s).
My local area connection is a direct connection from my modem to my Sony.
I imagine you don't normally have your broadband modem (that "UBEE D3.0"?) connected to the Vaio, right? Unless your modem has a second Ethernet port, I imagine that it's normally only connected to your Time Capsule.
I only keep it available because whenever I have to call Comcast, the first thing that they ask me to do is to make a direct connection from my Sony to the modem. And they also refer to it as the host computer. I do not keep this connection active at all times.
I understand. That's a routine troubleshooting technique, in that it removes as much equipment as possible from the connection chain. However, for the purposes of this discussion, calling that "the host computer" is irrelevant and potentially confusing.
I have Windows XP Professional 5.1.2600, SP3.
That's the latest version. It should be capable of connecting. If you have your Vaio connected via WiFi and via an Ethernet cable, I wonder if that's confusing Windows. In that case I'd disconnect the Ethernet cable to see if things work better that way.
One other technique that you may already be using: When you switch what device is connected to your broadband modem, for a lot of modems it's necessary to power the modem down for several minutes to convince it to connect to a new device.

Why when time machine does the back up on the time capsule atbthe end of the back up it starts again on a reverse mode?

i mean that i does the back up and time machine says for example 45 of 220 gb but when the count down is to 0 time machine start doing the opposito count for example 2gb of 2gb and few minutes later 3 gb of 3gb and so on. it seems it never stop

i mean that i does the back up and time machine says for example 45 of 220 gb but when the count down is to 0 time machine start doing the opposito count for example 2gb of 2gb and few minutes later 3 gb of 3gb and so on. it seems it never stop

System crashing when Time Machine backup starts

My MacBook Pro has crashed 4 times today. The first 2 times I wasn't around to see the crash, I just saw the message that the system had crashed and that I needed to hold down the power button and restart.
The 3rd time it happened I noticed that the Time Machine backup process had just started before the crash. I restarted the computer, manually started a Time Machine backup, and it crashed again.
It seems that the crashes are happening when Time Machine tries to backup to my Time Capsule.
Anyone have any ideas for me to try to get it working correctly, or any ideas on what exactly might be causing it? Maybe a problem with my Time Capsule? I noticed on my wife's MacBook that her Time Machine backup had failed today too. Her MacBook has not had any system crashes though.

Hi Garner,
Yes, you'll erase it with Disk Utility (make sure that you don't have any other information on the drive that you don't want to lose!).
So when you try backing up the other machine manually, does it work? If your other backup is actually working, you might want to try just erasing the old backups for the one machine that won't work and see if that helps (to avoid backing up both all over again). Just because my experience was that we had to format the drive doesn't mean that you'll necessarily have to.
And yes, if you don't ever mount the drive outside of Time Machine, that should be OK.
Hope that helps! Enjoy the long, boring backup process (sorry about that...).
—Hazy

When I open a PDF from an email Time Machine starts

Everytime I open a PDF from an email Time Machine starts & freezes my 4k iMac for about 30 seconds, it's annoying.

Although the problem is not the same, please follow the instructions in this support article to reset the Launch Services database. If you don't already have a current backup, back up all data before proceeding. You may have to log out or restart to see a change.

Leopard applications all hang while Time Machine prepares for backup

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

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

What to do when time machine seems stuck on "Preparing Backup"

This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos. This means that the only backup will be for the system, profiles, and the app. I have been running this for a few months andhas been doing OK until up to now.
My problem is that my time machine seems to get stuck on "Preparing Backup". The latest backup was done last Nov 8, 2011, whcih is about 11 days from now. I am also aware that the time machine drive has only about 200 mb space left, but I am not worried at all because I've always TM to delete the oldest backup to free up space. My oldest backup was still Sept 8, and I'm ok if that will be deleted.
So I'd like to find out why it still stuck on "Preparing backup" ,and I am wondering if deleting a backup can solve it. Can it? what do I do to solve this?
Also, I use my computer alot , so it is basically running for about 18 hours a day, but still time machine didn't quite work well. I have tried reparing the disk using disk utility, but that didn't help.

Comments inline below.
Pondini wrote:
joshua raphael wrote:
This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos.
You may want to revisit that strategy:
A backup on the same drive isn't very secure -- when (not if) the HD fails, you risk losing everything.
In most cases, if there's a problem with OSX the best way to fix it is to just install a fresh version. But you can't do that from that backup.
Indeed!
Backing-up apps that way will also be useless in some cases. 3rd-party apps that came with their own installers put other files in other places (and sometimes "helper" apps as well). Unless you know what and where they all are, and restore them, too, the restored app won't work properly, if at all.
I think you're confusing each other with terminology. iTunes music and iPhoto pictures are NOT "Libraries", which has a specific meaning when it comes to OS X. "Libraries", in OS X normally refers to /Libraries and ~/Libraries folders. This is not where iTunes music and iPhoto pictures are stored. iTunes music and iPhoto pictures are stored within ~/Music and ~/Pictures, respectively.
I have tried reparing the disk using disk utility, but that didn't help.
Disk Utility changed a bit in Lion. When you select an entire disk, it only repairs the partition map, not all the volumes. You must repair each one separately.
Wow, good to know. (What a stupid change to make, for backwards compatibility, if for no other reason!)
See #D1 in Time Machine - Troubleshooting to figure out why the backups are hanging.
Whew. This editor makes it so hard to make comments inline. The key thing when time machine seems stuck is patience. Sometimes it needs to be left to run overnight. Unfortunately, it doesn't log or report it's progress very well.
Opening Time Machine settings in Preferences plus a command like this left running in Terminal.app is how I monitor progress. And even so, there is very little logging indicating progress.
sudo tail -f /Volumes/Time Machine/Backups.backupdb/My\ Computer/2012-07-11-133352.inProgress/.Backup.363731632.496216.log
The parts in italics will need to be adjusted. Tab completion makes this easy, e.g type
sudo tail -f /Volumes/
and hit tab, type the first few letters of the relevant volume name, hit tab...
Also, I have a hypothesis which needs testing.
I know that Time Machine gets confused if one deletes large files from a backup - specifically, Time Machine doesn't recognize that the size of the backup has changed.
I know because this made restoring a thinned out time machine backup ("thinned out" by deleting files from within the GUI while inside the Time Machine) to a small SSD harder than it should have been. I had to restore to a big disk and then clone that volume to the SSD - even though the SSD had enough space, Time Machine didn't think so; it didn't "understand" that it had been thinned.
My hypothesis is that Time Machine also gets confused if the Time Machine partition is resized. I shrunk a Time Machine partition (no it wasn't on my main disk!) and about that time, Time Machine stopped working. After thinning the volume, it started working again.

Airtunes hangs when time machine starts

Similar Messages

Maybe you are looking for