Time Machine backup problems with firewire 800 since Mavericks

Since I installed Mavericks about a week ago, I have had problems with TM not working with my LaCie external drive. At best, it would not back up when the mac was awakened from sleep mode and in use. When I would open time machine preferences, I would see the "preparing for back up" prompt that would last forever. Not only was it doing that, I have found that it would freeze my mac. I figured this out when I was not able to get my mac to respond from the login screen. It was basically frozen and couldn't log on. I noticed the back up drive light flickering but nothing would happen even with waiting a long time. I finally figured out that shutting off the TM EHD would unfreeze the mac and it would start functioning normal again. This was happening with my external HD daisy chained to another external drive that contains my iPhoto, iMovie and Itunes files. That drive was also connected to the mac using firewire 800. I tried many different configurations, switched the order the drives were daisy chained, tried different cables and even directly connected the TM drive with firewire 800 to the mac, but the problems still persisted. The strange thing is that when I connect the TM drive through USB, it works flawlesly and no hanging up of the computer. Thats what Ive been forced to do. I have my other EHD connected directly through firewire 800 and it works fine. I only have one firewire 800 port, and since it works fine with my other LaCie drive, it makes me think its not the port or macs hardware? I can only guess this is a Time Machine issue or something wrong with my TM drive? I have been in contact with LaCie and given them all these details but I have not heard back yet on what they feel the problem is. I thought I would post this to see if anyone else had some experience with this problem.

Forgot to mention I did that. Completely erased and reformatted HD and then reconnected to TM. Didn't help. I did have the mac hang up while installing Mavericks and had to eventually shut off the external drive. It did that to me the firs time I tried to install Mavericks and I lost all my data because it did a clean install after that. I had another back up on CCC so I just restored from there. This time the update to Mavericks transferred my data. I have had TM hang up my mac in the past on occasion, but I was always able to shut down the drive and then the mac would return to normal. Perhaps I should try to erase and reformat again?

Similar Messages

Time Machine Backup Problem with OS X 10.9.4

I am having a problem with the Time Machine backup on a MacBook Pro 2.6 running OS X 10.9.4. What is happening is it starts the backup and then gets to a certain point and just freezes indefinitely at that point. (Indefinitely meaning overnight >12 hrs) I deleted the sparsebundle file and restarted the backup and it essentially freezes at the same point. It's like there's a particular file it has an issue with. Is there a way to tell what file it's backing up when it freezes so I can exclude it from the backup. I initially thought it was a Time Capsule and backing up over the network issue. I acquired a USB 3 Seagate drive and tried using it with the same result. So, the issue has nothing to do with the Maverick network "qwerks" I've seen referenced.
My initial backup size is about 250 GB. I've pared that back by excluding the Parallels Virtual Machines on the hard drive and my IPhoto Library. That scales the back up size to about 55 GB.   Before I did the file exclusion it was hanging up at 1.83 GB out of ~250GB. Now it's hanging up at 1.82 GB out of ~55 GB. So it's as if it is reaching some file it has an issue with and stopping.
Any thoughts?

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
The title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the word "Starting" (without the quotes.) You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard."
Each message in the log begins with the date and time when it was entered. Note the timestamp of the last "Starting" message that corresponds to the beginning of an an abnormal backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ If all you see are messages that contain the word "Starting," you didn't clear the text field.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. Don't post more than is requested.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

Time machine backup problem with company backup.

I have serious problems with making backups of our company computers by Time Machine.
We have Synology NAS with Time Machine Support. When I made setting for Time Machine backups (users, shares, quotas, etc. ) ewerything worked fine. All Time machines uses one directory, that appears on the network like a Time capsule. Machines have their own accounts with quotas etc. After a few days started many problems. Some Time Machines has missed their target sparsebundles and unsuccessfully tried write into some others. After Time Machine restart and new manual setting problem persisting. Only successfull solution is complete remove all affected sparsebundles (miss all older backups) and make new ones. This problems appears on many different computers with various OSX version 10.6 - 10.8.
Can you help me with this problem?

I have used OS X Server on an Xserve and gained the impression that it did little that OS X would not do. Earlier versions had a fairly easy to use GUI but as it developed it became more tedious and unreliable than using OS X on the same hardware. It was far from cheap for unlimited users even with educational discounts.
At one time OS X Server was more advanced than the same version number OS X - about half a version ahead.
I am not saying that it may not be faster to set up if you have had previous OS X Server experience but it is a steep learning curve after only OS X experience. The average user would get there faster with one of the many tutorials on the web about using OS X as a server.
At one time OS X Server had a security bug in that it confused FTP root with machine root under some conditions leaving the whole disk open to the public.

Time machine backup problem with new MacPro

On my new MacPro (6 core, 32gb, 1TB ssd) I am trying to do my initial Time Machine backup. The MacPro has 350 GB of files on it. When I start Time Machine it shows that it is backing up 355 GB of data onto the 4 TB LaCie drive and the time to complete is about 20 minutes. (The extrnal HD is excluded from the backup list). When it nears the end of the 355 gb backup all of a sudden it just starts increasing both the number of gbs copying and number of gbs left to copy (both numbers just start going up incrementally together) way beyond the initial 355 gbs - I've stopped it at 910 GBs several times. Tried different external hard drives, restarts etc.
Any ideas what is going on?
Thanks

3/2/14 3:58:22.176 PM com.apple.backupd[703]: Starting manual backup
3/2/14 3:58:22.464 PM com.apple.backupd[703]: Backing up to /dev/disk3: /Volumes/LaCie 1 4tb/Backups.backupdb
3/2/14 3:58:22.466 PM com.apple.backupd[703]: Ownership is disabled on the backup destination volume. Enabling.
3/2/14 3:58:27.071 PM com.apple.backupd[703]: Forcing deep traversal on source: "Macintosh HD" (device: /dev/disk0s2 mount: '/' fsUUID: 7D2102FE-BABF-3603-9A2A-42EBAB91196E eventDBUUID: 2C010EB1-3A50-41CC-95BF-7590BA087C20)
3/2/14 3:58:27.863 PM com.apple.backupd[703]: Total content size: 328.18 GB excluded items size: 4.92 GB for volume Macintosh HD
3/2/14 3:58:27.864 PM com.apple.backupd[703]: Found 668710 files (323.26 GB) needing backup
3/2/14 3:58:27.864 PM com.apple.backupd[703]: 344.73 GB required (including padding), 2.79 TB available
3/2/14 3:58:27.890 PM com.apple.backupd[703]: Waiting for index to be ready (100)
3/2/14 3:59:20.778 PM WindowServer[106]: window e2 is already attached to window e0
3/2/14 3:59:29.180 PM WindowServer[106]: _CGXGetWindowOrderingGroup: Operation on a window 0xe2 requiring rights 0x5 by caller System Preferences
3/2/14 3:59:30.854 PM WindowServer[106]: window e6 is already attached to window e0
3/2/14 3:59:39.881 PM WindowServer[106]: _CGXGetWindowOrderingGroup: Operation on a window 0xe6 requiring rights 0x5 by caller System Preferences
3/2/14 3:59:42.791 PM sandboxd[125]: ([715]) mdworker(715) deny file-read-data /Applications/GarageBand.localized/.localized ()
3/2/14 3:59:42.795 PM sandboxd[125]: ([715]) mdworker(715) deny file-read-data /Applications/GarageBand.localized/.localized ()
3/2/14 3:59:42.798 PM sandboxd[125]: ([715]) mdworker(715) deny file-read-data /Applications/GarageBand.localized/.localized ()
3/2/14 3:59:42.801 PM sandboxd[125]: ([715]) mdworker(715) deny file-read-data /Applications/GarageBand.localized/.localized ()
3/2/14 4:02:09.515 PM mdworker[744]: (Error) Import: Could not create instance for plugIn 'file:///Applications/GarageBand.app/Contents/Library/Spotlight/GarageBandSpotlig htImporter.mdimporter/'
3/2/14 4:02:09.515 PM mdworker[744]: (Error) Import: BAD IMPORTER ~~~~~~~~~~~~~~~~~~file:///Applications/GarageBand.app/Contents/Library/Spotlight/GarageBandSpotlig htImporter.mdimporter/
3/2/14 4:02:36.844 PM sandboxd[125]: ([738]) mdworker(738) deny file-read-data /Library/Documentation/User Information.localized/.localized (pre-plugin fstype:hfs fsflag:480D000 flags:200000044 diag:0 isXCode:0 uti:com.adobe.pdf plugin:/Library/Spotlight/PDF.mdimporter - find suspect file using: sudo mdutil -t 591093)
3/2/14 4:02:36.865 PM sandboxd[125]: ([738]) mdworker(738) deny file-read-data /Library/Documentation/User Information.localized/.localized (pre-plugin fstype:hfs fsflag:480D000 flags:200000044 diag:0 isXCode:0 uti:com.adobe.pdf plugin:/Library/Spotlight/PDF.mdimporter - find suspect file using: sudo mdutil -t 591093)
3/2/14 4:02:36.890 PM sandboxd[125]: ([738]) mdworker(738) deny file-read-data /Library/Documentation/User Information.localized/.localized (pre-plugin fstype:hfs fsflag:480D000 flags:200000044 diag:0 isXCode:0 uti:com.adobe.pdf plugin:/Library/Spotlight/PDF.mdimporter - find suspect file using: sudo mdutil -t 591093)
3/2/14 4:02:36.916 PM sandboxd[125]: ([715]) mdworker(715) deny file-read-data /Library/Documentation/User Information.localized/.localized (pre-plugin fstype:hfs fsflag:480D000 flags:200000044 diag:0 isXCode:0 uti:public.rtf plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 401141)
3/2/14 4:02:36.942 PM sandboxd[125]: ([738]) mdworker(738) deny file-read-data /Library/Documentation/User Information.localized/.localized (pre-plugin fstype:hfs fsflag:480D000 flags:200000044 diag:0 isXCode:0 uti:com.adobe.pdf plugin:/Library/Spotlight/PDF.mdimporter - find suspect file using: sudo mdutil -t 591093)
3/2/14 4:02:36.945 PM sandboxd[125]: ([715]) mdworker(715) deny file-read-data /Library/Documentation/User Information.localized/.localized (pre-plugin fstype:hfs fsflag:480D000 flags:200000044 diag:0 isXCode:0 uti:public.rtf plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 401141)
3/2/14 4:02:36.948 PM sandboxd[125]: ([715]) mdworker(715) deny file-read-data /Library/Documentation/User Information.localized/.localized (pre-plugin fstype:hfs fsflag:480D000 flags:200000044 diag:0 isXCode:0 uti:public.rtf plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 401141)
3/2/14 4:02:36.952 PM sandboxd[125]: ([715]) mdworker(715) deny file-read-data /Library/Documentation/User Information.localized/.localized (pre-plugin fstype:hfs fsflag:480D000 flags:200000044 diag:0 isXCode:0 uti:public.rtf plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 401141)
3/2/14 4:02:37.000 PM kernel[0]: Sandbox: mdworker(748) deny file-read-data /Library/Documentation/User Information.localized/.localized
3/2/14 4:02:37.000 PM kernel[0]: Sandbox: mdworker(748) deny file-read-data /Library/Documentation/User Information.localized/.localized
3/2/14 4:02:37.000 PM kernel[0]: Sandbox: mdworker(748) deny file-read-data /Library/Documentation/User Information.localized/.localized
3/2/14 4:02:37.000 PM kernel[0]: Sandbox: mdworker(748) deny file-read-data /Library/Documentation/User Information.localized/.localized
3/2/14 4:02:40.850 PM com.apple.SecurityServer[15]: Killing auth hosts
3/2/14 4:02:40.850 PM com.apple.SecurityServer[15]: Session 100022 destroyed
3/2/14 4:05:10.623 PM com.apple.SecurityServer[15]: Killing auth hosts
3/2/14 4:05:10.623 PM com.apple.SecurityServer[15]: Session 100013 destroyed
3/2/14 4:06:09.539 PM com.apple.SecurityServer[15]: Killing auth hosts
3/2/14 4:06:09.539 PM com.apple.SecurityServer[15]: Session 100016 destroyed
3/2/14 4:06:19.569 PM mdworker[740]: Messages Importer couldn't importfile:///System/Library/PrivateFrameworks/SetupAssistantSupport.framework/Version s/A/Resources/AppleConnect.chat
3/2/14 4:06:19.569 PM mdworker[741]: Messages Importer couldn't importfile:///System/Library/PrivateFrameworks/SetupAssistantSupport.framework/Version s/A/Resources/AppleDebug.chat
3/2/14 4:06:45.310 PM xpcproxy[778]: assertion failed: 13C64: xpcproxy + 3438 [D559FC96-E6B1-363A-B850-C7AC9734F210]: 0x2
3/2/14 4:10:35.429 PM WindowServer[106]: _CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
3/2/14 4:10:35.429 PM loginwindow[81]: find_shared_window: WID -1
3/2/14 4:10:35.430 PM loginwindow[81]: CGSGetWindowTags: Invalid window 0xffffffff
3/2/14 4:10:35.430 PM loginwindow[81]: find_shared_window: WID -1
3/2/14 4:10:35.430 PM loginwindow[81]: CGSSetWindowTags: Invalid window 0xffffffff
3/2/14 4:10:35.512 PM WindowServer[106]: device_generate_desktop_screenshot: authw 0x7f934075da30(2000), shield 0x7f9341e1e850(2001)
3/2/14 4:10:35.541 PM WindowServer[106]: device_generate_lock_screen_screenshot: authw 0x7f934075da30(2000), shield 0x7f9341e1e850(2001)
3/2/14 4:10:45.401 PM loginwindow[81]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
3/2/14 4:25:08.511 PM WindowServer[106]: CGXDisplayDidWakeNotification [6348810374829]: posting kCGSDisplayDidWake
3/2/14 4:25:08.512 PM WindowServer[106]: handle_will_sleep_auth_and_shield_windows: Deferring.
3/2/14 4:25:27.685 PM loginwindow[81]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
3/2/14 4:25:41.888 PM System Preferences[696]: view service marshal for <NSRemoteView: 0x7f882382ed40> failed to forget accessibility connection due to Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper application." (The connection was invalidated from this process.) UserInfo=0x600000477840 {NSDebugDescription=The connection was invalidated from this process.}
timestamp: 16:25:41.888 Sunday 02 March 2014
process/thread/queue: System Preferences (696) / 0x10d105000 / com.apple.NSXPCConnection.user.endpoint
code: line 2972 of /SourceCache/ViewBridge/ViewBridge-46.2/NSRemoteView.m in __57-[NSRemoteView viewServiceMarshalProxy:withErrorHandler:]_block_invoke
domain: communications-failure
3/2/14 4:25:45.589 PM System Preferences[696]: Attempted search for modules of unknown type (4)
3/2/14 4:29:53.871 PM WindowServer[106]: window e6 is already attached to window e0
3/2/14 4:30:00.197 PM WindowServer[106]: _CGXGetWindowOrderingGroup: Operation on a window 0xe6 requiring rights 0x5 by caller System Preferences
3/2/14 4:37:33.198 PM com.apple.IconServicesAgent[244]: main Failed to composit image for binding VariantBinding [0x3df] flags: 0x8 binding: FileInfoBinding [0x22d] - extension: mov, UTI: com.apple.quicktime-movie, fileType: ????.
3/2/14 4:37:33.199 PM quicklookd[816]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x203] flags: 0x8 binding: FileInfoBinding [0x103] - extension: mov, UTI: com.apple.quicktime-movie, fileType: ???? request size:32 scale: 1
3/2/14 4:37:43.260 PM xpcd[205]: restored permissions (100600 -> 100700) on /Users/stephenbarrie/Library/Containers/com.apple.quicklook.ui.helper/Container .plist
3/2/14 4:39:15.805 PM CalendarAgent[230]: [com.apple.calendar.store.log.notifications.totals] [Warning: Alarm for recurring event Bring wifi to GG has large relative trigger of 2147483647. Ignoring.]
3/2/14 4:39:15.808 PM CalendarAgent[230]: [com.apple.calendar.store.log.notifications.totals] [Warning: Alarm for recurring event Ear meds has large relative trigger of 2147483647. Ignoring.]
3/2/14 4:40:27.529 PM com.apple.IconServicesAgent[244]: main Failed to composit image for binding VariantBinding [0x239] flags: 0x8 binding: FileInfoBinding [0x3eb] - extension: jpg, UTI: public.jpeg, fileType: ????.
3/2/14 4:40:27.530 PM quicklookd[816]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x403] flags: 0x8 binding: FileInfoBinding [0x303] - extension: jpg, UTI: public.jpeg, fileType: ???? request size:128 scale: 1
3/2/14 4:40:27.541 PM com.apple.IconServicesAgent[244]: main Failed to composit image for binding VariantBinding [0x23b] flags: 0x8 binding: FileInfoBinding [0x153] - extension: pages-tef, UTI: com.apple.iwork.pages.pages-tef, fileType: ????.
3/2/14 4:40:27.542 PM quicklookd[816]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x603] flags: 0x8 binding: FileInfoBinding [0x503] - extension: pages-tef, UTI: com.apple.iwork.pages.pages-tef, fileType: ???? request size:128 scale: 1
3/2/14 4:40:27.568 PM com.apple.IconServicesAgent[244]: main Failed to composit image for binding VariantBinding [0x23d] flags: 0x8 binding: FileInfoBinding [0x3ed] - extension: pages, UTI: com.apple.iwork.pages.pages, fileType: ????.
3/2/14 4:40:27.569 PM quicklookd[816]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x803] flags: 0x8 binding: FileInfoBinding [0x703] - extension: pages, UTI: com.apple.iwork.pages.pages, fileType: ???? request size:128 scale: 1
3/2/14 4:40:27.585 PM com.apple.IconServicesAgent[244]: main Failed to composit image for binding VariantBinding [0x23f] flags: 0x8 binding: FileInfoBinding [0x155] - extension: lpdf, UTI: com.apple.localized-pdf-bundle, fileType: ????.
3/2/14 4:40:27.586 PM quicklookd[816]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0xa03] flags: 0x8 binding: FileInfoBinding [0x903] - extension: lpdf, UTI: com.apple.localized-pdf-bundle, fileType: ???? request size:128 scale: 1
3/2/14 4:40:27.589 PM com.apple.IconServicesAgent[244]: main Failed to composit image for binding VariantBinding [0x241] flags: 0x8 binding: FileInfoBinding [0x3ef] - extension: pdf, UTI: com.adobe.pdf, fileType: ????.
3/2/14 4:40:27.590 PM quicklookd[816]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0xc03] flags: 0x8 binding: FileInfoBinding [0xb03] - extension: pdf, UTI: com.adobe.pdf, fileType: ???? request size:128 scale: 1
3/2/14 4:41:04.896 PM com.apple.backupd[703]: Copied 626650 items (513.4 GB) from volume Macintosh HD. Linked 0.
3/2/14 4:41:04.921 PM com.apple.backupd[703]: Backup canceled.
3/2/14 3:58:22.176 PM com.apple.backupd[703]: Starting manual backup
3/2/14 4:45:12.000 PM kernel[0]: AppleKeyStore starting (BUILT: Oct 17 2013 20:40:01)
3/2/14 4:45:14.731 PM awacsd[91]: Starting awacsd connectivity_executables-97 (Sep 12 2013 20:24:33)
3/2/14 4:45:14.750 PM mDNSResponder[70]: mDNSResponder mDNSResponder-522.90.2 (Nov 3 2013 18:51:09) starting OSXVers 13
3/2/14 4:45:14.757 PM WindowServer[104]: Server is starting up
3/2/14 4:45:32.301 PM sharingd[217]: Starting Up...
3/2/14 4:54:52.017 PM com.apple.backupd[360]: Starting manual backup
3/2/14 5:00:55.918 PM com.apple.backupd-helper[359]: Not starting scheduled Time Machine backup: Backup already running
3/2/14 5:46:51.000 PM kernel[0]: AppleRAID::restartSet - restarting set "LaCie" (5BC18B93-2DBE-4254-8A5A-E979B94196EA).
3/2/14 6:38:13.000 PM kernel[0]: AppleKeyStore starting (BUILT: Oct 17 2013 20:40:01)
3/2/14 6:38:17.157 PM mDNSResponder[65]: mDNSResponder mDNSResponder-522.90.2 (Nov 3 2013 18:51:09) starting OSXVers 13
3/2/14 6:38:17.162 PM awacsd[84]: Starting awacsd connectivity_executables-97 (Sep 12 2013 20:24:33)
3/2/14 6:38:17.173 PM WindowServer[94]: Server is starting up
3/2/14 6:38:31.449 PM sharingd[199]: Starting Up...
3/2/14 6:48:42.000 PM kernel[0]: AppleKeyStore starting (BUILT: Oct 17 2013 20:40:01)
3/2/14 6:48:44.465 PM awacsd[86]: Starting awacsd connectivity_executables-97 (Sep 12 2013 20:24:33)
3/2/14 6:48:44.474 PM mDNSResponder[68]: mDNSResponder mDNSResponder-522.90.2 (Nov 3 2013 18:51:09) starting OSXVers 13
3/2/14 6:48:44.508 PM WindowServer[97]: Server is starting up
3/2/14 6:48:58.168 PM sharingd[204]: Starting Up...
3/2/14 6:49:21.116 PM com.apple.backupd[240]: Starting manual backup
3/2/14 6:55:57.141 PM com.apple.backupd-helper[299]: Not starting scheduled Time Machine backup: Backup already running
3/2/14 7:59:41.107 PM com.apple.backupd[485]: Starting automatic backup

Time machine backup problem with upgrade to Lion - Choose Backup Disk button non-existant

Hi, I just upgraded my mac mini to Lion and have encountered a problem with by Time Machine. It no longer sees my networked drive for back up. So, I followed the instructions on this site http://code.stephenmorley.org/articles/time-machine-on-a-network-drive/ and get to item 6b. and have a problem I have not been able to sort out. Instead of the button "Choose Backup Disk" on the Time Machine window, I have a button "Select Disk" with a button "Options" under it. When I click "Select Disk" I get a window promtping me to "Set Up Other Time Capsule" and clicking that takes me to a window for AirPort Utility. (screen shot )
Anyone know why I don't have the right button for starters and why I can't access any drives on my machine at all? I followed the web instructions on the site I mention above because initially I had an error about AFP, so suspected the drive set up here (it is my work) is incompatible.
(The only IT guy we have is on vacation for 2 weeks and then I am on vacation for 2 weeks and can't wait a month in order to back up! Thought I would try here to see if I can get answers before I am away.)
Thanks in advance!

i had a similar problem when I first installed Lion last year. It seems that some network NAS products need a firmware update to work with Lion. I contacted the manufacturer and they helped me out. I am using a Synology NAS system. Problem solved after firmware update.

My Time machine backup fails with an error message

Time machine used to work just fine when I first upgraded to Leopard but now every time it tries to backup I get an Error message "Unable to complete backup. An error occurred while copying files to the backup volume." This occurs while Time Machine is "Preparing". Next hour it starts all over again and does the same thing. I have reformatted the backup drive but still get the error. I'm backing up to a 300g Firewire drive and have used about 207G for the backups.backupdb folder.
An ideas how to resolve this issue?

Here is a list of some TM articles that may help. You can look for more by searching Mac Help from the Finder's Help menu or searching the Knowledge Base from Apple's Support Page.
Time Machine Troubleshooting
Here are several articles to help troubleshoot Time Machine Problems as well as assist in properly setting up Time Machine.
Mac 101- Using Time Machine in Mac OS X 10.5 Leopard
Is Time Machine all you need?
Some advice for those using Time Machine
TidBITS Macs & Mac OS X- Time Machine- The Good, the Bad, and the Missing Features
Mac OS X 10.5- Time Machine backups are not visible
OS X 10.5- Time Machine stops backing up to external disk
10.5- Disable the 'use this disk?' Time Machine dialog
Time Machine tips and troubleshooting
Mac OS X 10.5 Help- Restoring files backed up with Time Machine
OS X 10.5- Using Time Machine and troubleshooting Time Machine issues

Time Machine backups fail with no error message

My Time Machine hasn't successfully completed a backup since 3/19. It starts the backup on schedule, indexes over 2 million objects, goes through the phase of preparing objects, and then just stops. I know that there have been many changes since that time, but it isn't backing them up. Please tell me how to fix this.

I have the same problem - Time Machine fails to backup with no error message - after a brief foray into Mavericks. Each time it tries to backup, TM creates a new folder in the "in progress" directory but fails to complete. Otherwise TM looks normal with no obvious errors. I have several HDDs. I installed Mavericks on an external drive, migrated my data over to it. Booted from it and after a day or two decided I just didn’t' like it and booted from my Snow Leopard partition. All was fine but apparently, I had forgotten to turn OFF Time Machine while booted into Mavericks. Thereafter, Time Machine failed to backup. Here's what I've done and the error logs:
Deleted the NEW directory that Mavericks created on TM
Done a full reset of TM (deleted: /Library/Preferences/com.apple.TimeMachine.plist
Re-entered the exclusions
Rebuilt the directory structure on the boot disc using DiskWarrior
Repaired the TM disc using Disc Utility
Resynced the Spotlight cache on the boot disk
TM also seems not to do a deep traversal since it just stops after checking files to backup.
Here are the error logs from the TM Buddy widget:
Starting standard backup
Error loading /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/Vir tualPCDiskImagePlugin: dlopen(/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/Ma cOS/VirtualPCDiskImagePlugin, 262): no suitable image found. Did find:\n /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/Vir tualPCDiskImagePlugin: mach-o, but wrong architecture
Cannot find function pointer MacDiskImagePluginFactory for factory 7F1FD83E-6684-11D8-968F-000A957703C0 in CFBundle/CFPlugIn 0x102f00930 </Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle> (bundle, not loaded)
Backing up to: /Volumes/Time Machine/Backups.backupdb
Event store UUIDs don't match for volume: Mac Pro Data
Forcing deep traversal on source: "Mac Pro Data" (mount: '/Volumes/Mac Pro Data' fsUUID: B4BEA50F-15B1-34BB-92F1-B7605139B852 eventDBUUID: BA019CB5-8123-4C99-9806-C9593D4EFA34), {1, 1, 1, 0}
Event store UUIDs don't match for volume: Music HDD
Forcing deep traversal on source: "Music HDD" (mount: '/Volumes/Music HDD' fsUUID: FF1EF8F5-30D0-34C0-BC02-ACDB5AD18B3A eventDBUUID: 92A95F63-5F4A-4987-90DB-5444ADF33D40), {1, 1, 1, 0}
Node requires deep traversal:/ reason:must scan subdirs|
Error: Flushing index to disk returned an error: 0
Backup canceled.
I don't know what to do next. Any ideas?
Thanks,
John

Time Machine backup problem OS X server 10.5.8

Greetings,
I am having a horrible time getting an OS X 10.5.8 server to run Time Machine. I've followed all of the advice, started with a fresh drive, et...etc...etc... and no love.
When starting Time Machine, I get the following in the logfile. Can anyone help?
1/23/12 12:42:23 PM /System/Library/CoreServices/backupd[315] Backup requested by user
1/23/12 12:42:23 PM /System/Library/CoreServices/backupd[315] Starting standard backup
1/23/12 12:42:23 PM /System/Library/CoreServices/backupd[315] Backing up to: /Volumes/TimeMachine/Backups.backupdb
1/23/12 12:42:23 PM /System/Library/CoreServices/backupd[315] Backing up to: /Volumes/TimeMachine/Backups.backupdb
1/23/12 12:42:28 PM hdiejectd[374] running
1/23/12 12:42:28 PM hdiejectd[374] running
1/23/12 12:42:30 PM KernelEventAgent[60] tid 00000000 received unknown event (256)
1/23/12 12:42:30 PM KernelEventAgent[60] tid 00000000 received unknown event (256)
1/23/12 12:42:47 PM diskarbitrationd[71] servermgrd [54]:30783 not responding.
1/23/12 12:42:47 PM diskarbitrationd[71] servermgrd [54]:30783 not responding.
1/23/12 12:42:49 PM DirectoryService[26] GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Server not found in Kerberos database)
1/23/12 12:42:49 PM DirectoryService[26] GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Server not found in Kerberos database)
1/23/12 12:42:51 PM kernel serialnumberd 406 FS_WRITE_DATA SBF /dev/dtracehelper 13 (seatbelt)
1/23/12 12:42:51 PM /usr/sbin/serialnumberd[406] serialnumberd started as /usr/sbin/serialnumberd.
1/23/12 12:42:51 PM kernel serialnumberd 406 FS_READ_DATA SBF /dev/autofs_nowait 13 (seatbelt)
1/23/12 12:42:51 PM /usr/sbin/serialnumberd[406] SN_Register(): New persistent, network record [tag=xsvr, extra=mec105-73.med.utah.edu] registered successfully by pid 406.
1/23/12 12:42:51 PM kernel serialnumberd 406 FS_READ_DATA SBF /usr/sbin 13 (seatbelt)
1/23/12 12:42:51 PM kernel serialnumberd 406 FS_READ_DATA SBF /usr/sbin 13 (seatbelt)
1/23/12 12:42:57 PM /usr/sbin/serialnumberd[406] launchd did not pass version 1 Mach port (bad launchd plist?)
1/23/12 12:42:57 PM /usr/sbin/serialnumberd[406] launchd did not pass version 1 Mach port (bad launchd plist?)
1/23/12 12:43:05 PM /usr/sbin/serveradmin[435] Port mapping operation attempted for 1 port(s)
1/23/12 12:43:05 PM /usr/sbin/serveradmin[435] 0 : Adding a mapping for port 80 for TCP
1/23/12 12:43:05 PM /usr/sbin/serveradmin[435] synch needed /private/etc/nat/autoportmap.plist
1/23/12 12:43:05 PM /usr/sbin/serveradmin[435] synch needed /private/etc/nat/autoportmap.plist

I also had to restart the server and client after applying the "fix" I described above. Basically, no user should have multiple, simultaneous file sharing sessions on the server. But even clearing the user sessions does not resolve the problem beyond the next Time Machine backup, so I also tried disabling and enabling file sharing, but the problem also returns after doing this. Only restarting both the client and server after clearing the sessions has worked for me when I have this problem. The problem may return much later, but this work aroudn definitely works as a temporary solution.
Next time I encounter this problem I will try restarting just the server or just the client, because it is unlikely that the problem exists due to something on both systems. Server 3.x is definitely not as stable as it should be, but for my use, it is getting the job done.

Time Machine:Backup failed with error: 11

All of a sudden this weekend my Time Machine backup stopped working. I just installed a new Time Capsule about 2 months ago and was backing up with no problems until now. When the backup starts it runs for a few minutes, then throws the following error:
So I ran Disk Utility on the Time Capsule and I got this:
Verifying volume “Time Machine Backups”
Checking file systemChecking Journaled HFS Plus volume.
Detected a case-sensitive volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking multi-linked directories.
Incorrect number of directory hard links
Checking volume bitmap.
Checking volume information.
The volume Time Machine Backups was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Click Repair Disk.
My question is this, if I run Repair Disk on my Time Capsule, am I going to lose all the data on there? Granted, I'd be punting 2 months worth of backups, which isn't the worst thing in the world, but if there is any way to save the data I'd prefer that option.

You have to repair to get the data to copy off.. generally.
But you can try to copy beforehand.. plug in a USB drive of adequate size and archive off the current backups.. you do this via the v5 utility.. apple simply left it out of v6.
That means you have to install v5 on Mountain Lion do it thusly.
How to load 5.6 into ML.
1. Download 5.6 for Lion.
http://support.apple.com/kb/DL1482
Click to open the dmg but do not attempt to install the pkg.. it won't work anyway.
2. Download and install unpkg.
http://www.timdoug.com/unpkg/
Run unpkg on the desktop.. it is very simple.. drag the AirPortUtility56.pkg file over to unpkg.. and it will create a new directory of the same name on the desktop.. drill down.. applications utilities .. there lo and behold is Airport utility 5.6 .. drag it to your main utilities directory or just run it from current location.
You cannot uninstall 6.1 so don't try.. and you cannot or should not run them both at the same time.. so just ignore the toyland version.. the plastic hammer.. and start using 5.6.. a real tool.
If the file doesn't copy that is half-expected as it is corrupt.
Run the repair.
Do the archive if you want.. of the repaired backup.
Now do an erase of the TC.. I would recommend a one pass erase which will take several hours as it has to low level format the drive. Any errors means the drive is no longer to be trusted. Take it back to apple and say the drive is corrupt.. that isn't good enough and you want a new one.

Time Machine backup problem. Stuck indexing 101. Any suggestions?

Hi
I am having trouble with my Time Machine backup and would be grateful for your help.
I have downloaded the widget and copied the script below.
Time Machine has been operating without issue since bought, around a year ago.
The last backup was 18th May. Nothing comes to mind that may have triggered a change on that date.
I placed the "My Book" backup volume in the private folder for Spotlight.
The indexing process has been running without interruption for over 24 hours.
The backup drive is connected via USB
I have changed the USB port to ensure the connection is sound, which it appears to be
Starting standard backup
Backing up to: /Volumes/My Book/Backups.backupdb
Event store UUIDs don't match for volume: Mac HD
Node requires deep traversal:/ reason:must scan subdirs|new event db|
No pre-backup thinning needed: 12.19 GB requested (including padding), 592.88 GB available
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
I am hoping that the script may help you direct me toward where I should concentrate my efforts.
Many thanks
M

woodwam wrote:
Event store UUIDs don't match for volume: Mac HD
start with A6 (blue box) in this user tip, also D1.

Time Machine backup disk no longer available since upgrade to Mountain Lion

He everyone,
I've been using Time Machine for years to backup my iMac to an external USB harddrive (Samsung HD103Sl), and everything used to work just fine up until I installed Mountain Lion.
Now Finder nor Time Machine can see my external harddrive. If I go to DIsk Utility, the harddrive is listed there, and everything seem to be just fine. I tried to run a disk verification and a repair, but Disk Utility tell me everything is OK.
Is it a Mountain Lion bug? Can someone help me with that?
TIA
Charles

I'm not sure if I have exactly the same case as yours....
I got the problem with my external HDD (with 2 partitions) while I was using one of the encrypted partition as Time Machine backup. I could not erase it after I upgrade to Mountain Lion, and it shown "this patition contain a locked disk and can not be resized until it is unlocked" in Disk Utility.
You may have a look if that's the same in Disk Utility.
Finally I get it fixed by the "diskutil" command in "Terminal" in "OSX > Applications > Utilities".
I used the command "diskutil" to verify the UUID of the "Logical Volume Group (LVG)" of the locked partition.
Then use the command to delete the LVG.
** All logical volume under this groiup will be deleted!!
Once the operation finished, I am able to recreate the partition in Disk Utility.
Hope this help!!

Old Time Machine Backup Problems - Permissions

Today, I figured out how to access my iPhoto Library photos from my old Time Machine backups. I was SO happy! The backups were from 2011 and earlier (hardrive crashed in May 2012). I had not done a Time Machine backup since 2011, so I decided to do a new backup today. After the backup finished, I decided to look at my old photos again (in the old backups) and when I tried to click on any of the files in the old backups, I get the message: The folder “Pictures” can’t be opened because you don’t have permission to see its contents.
Of course, now I am crushed/frustrated because I do not understand why I cannot access the old backups anymore. *Note: the new backup is accessible.

No problem.
You probably need to use Browse Other Time Machine Disks and within that older backup go to User/Pictures and restore the file "iPhoto Library" to a separate folder on your drive (so as not to replace your current iPhoto library) and then look in that restored photo library.
You need to do this in the Time Machine "Star Wars" interface from "Browse Other...."

Time Machine Backup Options with old powerbook

I'm looking for some suggestions on the following. I have two computers running Leopard, my wifes iMac and my Macbook. I have an older powerbook (running tiger) that jumped out of an airplane, bounced hard, and rattled its monitor hard enough to be unviewable. I can, however, connect to it and control it via Chicken of the VNC.
What I would like to do is unclutter my wifes workspace by removing the 2 external HD's connected to the iMac, connect them to the powerbook and run our Time Machine backups through the powerbook onto the external harddrives.
How can I connect and use those drives with Time Machine if the powerbook is running Tiger, not Leopard?
If that isn't doable, what other options are there to make those hard drives mountable over a network?
Is there any other way to keep those hard drives out of sight while still running our backups to them?
Thanks for your help,
-JJ

Even with an 802.11n wireless card you will have to change your wireless router to one that also supports 802.11n. Every element of your home network will have to support 802.11n in order to use it. If the router doesn't support it then the network will default to 802.11g. 802.11n has a throughput rate of about 140 Mbits/sec which is only a little faster than 100BT Ethernet. Still quite slow. Not even as fast as USB 2.0 which is slower than FW400 in this type of use.
Frankly, if you can't use Gigabit Ethernet then I don't think you will be very pleased with using networked backup or storage.
The better option is to connect an external Firewire drive to each computer and use TM or third-party backup software. Use FW800 if the computers have a FW800 port. You can always use wireless for file sharing between the computers. Put the Pismo in the closet.
That's my opinion.

Limiting Time Machine backup Size with WD MyBookLive and 10.8

I cannot take credit for the any part of this solution; merely for merging and clarifying how the solutions discovered by 2 Apple Support Communities contributors much smarter than I (namely “Pondini” – Florida and “himynameismarek”) - worked perfectly for my situation. All cudo’s to these two!
I have about average or better PC skills, but am an absolute newbie with Apple. This week I got a new iMac. Having a number of home PC’s all sharing files and back up space on a Western Digital MyBookLive (“WD MBL”) 3TB network drive (NAS), naturally I wanted to use it to backup the new Mac rather than rushing out to buy an Apple Time Capsule.
There are hundreds of threads on limiting size of a Time Machine (“TM”) backup, many of which required entries in “Terminal” or were devised on older versions of OSX. I’m running OSX Mountain Lion 10.8, so was concerned they may not work.
The issues I wanted to resolve were:
Time Machine will use up all of the space on my WD MBL if left to it’s own devices.
The WD MBL is compatible with Mac and PC’s… which is good… but unlike a back up in Windows 7 Pro which will allow you to make backups in a mapped “share” you create yourself, Apple TM Backups will not; they end up in a hidden folder on the NAS (much like PC backups done with WD Smartware)
At first I thought maybe I could limit the size of a share created in the MBL, but not possible, at least not that I've seen and I have searched for days.
The solutions:
First make sure you have the latest firmware for the WD MBL as of today it is MyBookLive 02.11.09-053. From what I’ve read Western Digital fixed the compatibility issues with 10.8 Mountain Lion just recently.
Next you need to start TM so that it starts to create a back up. You can stop the back up once you see files being copied. Do this before you walk thru the video tutorial by my Marek below. WD MBL will create the hidden folder you need to find for TM Backups. This folder is called “TimeMachine” but it is not visible even in the “MBL_NAME-backup” folder in Finder.
Open safari and type “ afp://xxx.xxx.x.xxx ” but use your own ip address of your MBL. Mine was 192.168.1.120, yours will be different.
It will ask how you want to connect. CHOOSE AS A GUEST even if your MBL is protected… I’m not sure why it works but it does. Then a window will come up asking which share you’d like to mount. You will see all of your own shares plus one called software and now one called “TimeMachine”. Choose that one.
Now in “Finder” you will see a mounted shared item called “YOUR_MBL_NAME-“ (the same as the one that is probably already there but with a dash(-) at the end). You’ll also see a new “device” in the device list called “Time Machine Backups” (If you already have watched the video tutorial by Marek, you’d know you are looking for a file called “YOUR_MACHINE_NAME.sparsebundle”. Well if you browse the folder “Backups.backupdb” in the Time Machine Backups device you won’t find it… again I don’t know why but you won’t. It resides in the hidden folder called “TimeMachine” that is now visible in the thing you just mounted in step 4)
NOW watch this video tutorial http://youtu.be/Nq7mSizqUSI and follow it step by step.
Voila... issues resolved. Thank you Pondini and Marek!

Try Use Terminal to limit Time Machine sparcebundle size on timecapsule,
should work to limit Time Machine backup size on any NAS or external disk (or not...)
sudo defaults write /Library/Preferences/com.apple.TimeMachine MaxSize 500000
to return to ilimited
sudo defaults delete /Library/Preferences/com.apple.TimeMachine MaxSize
if you want to reclame deleted files space shrink it use
hdiutil resize -size 500g -shrinkonly /Volumes/TimeMachineYOURNAME/YOURNAME.sparsebundle/
Regards

I just moved iPhoto (9.6) library to EHD from my MBP. I had been running time machine backups. With the library now on an EHD, will time machine run a seamless backup next time i connect (if i allow TM to see other drives)?

I have MBP 2012 running Yosemite and iPhoto 9.6. I run Time machine backups daily.
I just moved iPhoto library to EHD and removed the iPhoto library on MBP. I have enabled external drives to be accessed on TM. The next time i run a TM backup with the EHD connected, will TM run a seamless backup or will it not like the fact that a backup is now spread across two devices where it used to be on only one?

By default EHDs are excluded for TM backups - you have to go to the TM preferences ==> options and remove them from the excluded list
And you need two disks connected -one for your iPhoto library and one for the TM backup - TM will backup all hard drives that ar not excluded - you do not need multiple TM backup disks
LN

Time Machine backup problems with firewire 800 since Mavericks

Similar Messages

Maybe you are looking for