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

Similar Messages

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

  • Using Time Machine Backup Drive with NEW Macbook Pro

    I just got a new Macbook Pro. I migrated from my old MacBook Pro. Now I want to use my Time Machine Disk with this new machine.
    When I connect the external drive, and select back up now, it says there is not enough space (due to the fact this is a new machine and it wants to backup the entire thing)
    Also, when I go into the TimeMachine, it doesn't show me anything past today. . . all of my backups are not displayed over the past year. . .
    How do I make it so that the external drive displays all my old backups. . . ??
    Thank you for your help.

    Turn off TM or set the backup drive to null. Rename your computer in Sharing preferences to the same computer name of your old computer. Turn TM back on and reselect the backup drive. TM will behave as you expect. Of course if the file dates on the new machine are all changed since the migration, then TM will correctly assume that they require backing up. You will then find that there will not be sufficient space on the drive for the new backups. If this occurs then you should simply erase the backup drive and start your TM backup anew.

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

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

  • I am trying to do a full Time Machine Backup to a new external disk. The backup starts, and it says "Time remaining about 4 days." That seems like a very long time, but the real problem is that the computer "logs off" after a few hours, and the b.u. stops

    I am trying to do a full Time Machine Backup to a new external disk. The backup starts, and it says "Time remaining about 4 days." That seems like a very long time, but the real problem is that the computer "logs off" after a few hours, and the backup stops. The system preferences are set to "Never" for Computer sleep and Display sleep. The computer does not ordinarily log off automatically, but it has done this twice since I started the Time Machine backup.

    If you have more than one user account, these instructions must be carried out as an 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.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. 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 (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
    If all you see are messages that contain the word "Starting," you didn't clear the search box.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Some personal information, such as the names of your files, may be included — anonymize before posting.

  • I used migration assn't to load a Time Machine backup onto a new mac.  The first TM backup after that took some time, perhaps not surprising.  But the backups thereafter have all taken hours, with huge amounts of "indexing" time.  Time to reload TM?

    I used migration assn't to load a Time Machine backup onto a new mac.  The first TM backup after that took some time, perhaps not surprising.  But the backups thereafter have all taken hours, with huge amounts of "indexing" time.  Time to reload TM?

    Does every backup require lots of indexing?  If so, the index may be damaged.
    Try Repairing the backups, per #A5 in Time Machine - Troubleshooting.
    If that doesn't help, see the pink box in #D2 of the same link.

  • HT201250 existing Time Machine backups to a new Mac

    how do i migrate existing time machine backups to a new mac from my time capsule?

    It took a little more research, but that link in the end solved my problem.  After mounting the Time Capsule and the previous backup sparsebundle, I ran these commands to inherit the old backup (with <capsule> and <machine> representing the names of the Time Capsule and machine/hard drive respectively:
              sudo tmutil inheritbackup /Volumes/<capsule>/<machine>.sparsebundle
              sudo tmutil associatedisk -a / /Volumes/Time\ Machine\ Backups/Backups.backupdb/<machine>/2012-12-09-114511/<machine>
              sudo tmutil setdestination /Volumes/<capsule>/
    "2012-12-09-114511" was the latest snapshot that was there.  According to the documentation, you can pick any snapshot, since the "-a" in that command will update all of the associated snapshots.

  • How does one SUCCESSFULLY transfer Time-Machine backup to a new (larger) hard disk drive using OSX 10.5.8

    I have read a number of articles about how to transfer a complete Time-Machine backup to a new (larger) hard disk-drive.  Some of these articles are specifically for OSX10.6 users, which are not applicable to me since I am operating with OSX 10.5.8.
    However, I have tried several times to use the Disk Utility 'Restore' function, dragging my old time-machine volume into the 'Source:' box and my new volume into the 'Destination:' box.  This works, of sorts, BUT the newly created volume on the new larger hard disk-drive remains the same size as the original volume on the old Time-Machine HDD, with no apparent way of increasing the new volume's size.  So I am not really any better off:
    E.g. the total capacity of my new HDD is stated by 'Disk Utility' to be 465.8 GB, of which I'm told 228.2 GB is used for the Backups.backdb folder, but only 4.6 GB of free space is actually available.  Yet under the 'Partition' tab of 'Disk Utility' it tells me that there is still 236.4 GB of available space.
    Does anyone know how to resolve this issue without upgrading to OSX 10.6?

    First, how did you prepare your new drive?  See:
    Drive Preparation
    1.  Open Disk Utility in your Utilities folder.  If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button.  When the menu bar appears select Disk Utility from the Utilities menu.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area.  If it does not say "Verified" then the drive is failing or has failed and will need replacing.  SMART info will not be reported  on external drives. Otherwise, click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
    If you plan to partition this new drive then be sure you create a larger partition for TM than your old volume.
    Next, clone your old TM volume:
    Clone using Restore Option of Disk Utility
    1. Open Disk Utility from the Utilities folder.
    2. Select the destination volume from the left side list.
    3. Click on the Restore tab in the DU main window.
    4.Check the box labeled Erase destination.
    5. Select the destination volume from the left side list and drag it to the Destination entry field.
    6. Select the source volume from the left side list and drag it to the Source entry field.
    7. Double-check you got it right, then click on the Restore button.
    Destination means the external backup drive. Source means the internal startup drive.

  • Can I transfer a Time Machine backup to a new empty hard drive, without installing Mountain Lion again?

    Can I transfer a Time Machine backup to a new empty hard drive, without installing Mountain Lion on that new hard drive?

    Yes - I just did it the other night. Took five hours, but it finally finished and is working great.
    I sort of followed the instructions found here -->> http://pondini.org/TM/18.html.
    Also, if you want to have dual backups, see -->>
    http://pondini.org/TM/27.html.
    I say 'sort of' because I used Carbon Copy Cloner to do a block-level transfer. I just didn't want to get hung up with a Finder copy.
    Give CCC a try - you have to enable the block copy in Preferences before using this method, but I was quite happy with it. I used it to move over 1TB of TM backups from a FireWire 800 drive to a 2TB Thunderbolt drive. 5 seconds short of taking 5 hours.
    It should work well for you.
    Clinton

  • Transfer Time Machine backups to a new drive

    Is there an automated or an easy way to transfer my current Time Machine back ups to the new Time Capsule (I am sure I will inevitably buy it]. Looks like a great system for notebook users but I wouldn't like to start again with time Machine I like having the security of back ups I have already accrued. My current drive is certainly not full and won't be for a while.

    So far not very many people have had much success in copying their Time Machine backups to a new drive although the Restore option in Disk Utility ought to be able to do this. However, SuperDuper will support that capability when their new Leopard compatible version is released which should be in a week or so.
    http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html
    http://www.shirt-pocket.com/blog/

  • HT201250 when restoring a time machine backup to a new computer, does it affect the new operating system on the new computer

    when restoring a time machine backup to a new computer, does it affect the new operating system on the new computer?

    That depends on how you do it.
    By far the best, easiest, most reliable method is to use Setup Assistant when your shiny new Mac first starts up, to transfer your apps, users, data, etc.   That doesn't disturb either the OS or basic Apple apps that came with the new Mac.  See Using Setup Assistant on Mountain Lion or Lion.
    There is a facility to restore an entire system from Time Machine backups, including the version of OSX on the backup, but that's for use when your internal HD has been erased or replaced only.  It's not a good idea to restore the full backup of one Mac to a different one.  Depending on the circumstances, the installer may not allow it.  Even if it does, the Mac may not start up, or may kernel panic, or not work properly.

  • How Can I Migrate My Time Machine Backups To A New External Hard Drive?

    I have a external hard drive that has 500 GBs left, but I want to buy a larger drive.

    ivan wrote:
    How Can I Migrate My Time Machine Backups To A New External Hard Drive?
    I have a external hard drive that has 500 GBs left, but I want to buy a larger drive.
    Hi iVain
    Fire up *Disk Utility*, click the Restore tab, then drag your old and new TM drives into the Source and Destination fields. Click Restore, and a complete copy of your old TM files will be made on the new drive. Go to TM preferences and select the new drive, and it will continue backing up just as it left off.
    Hope this answers your question. See:
    http://discussions.apple.com/thread.jspa?threadID=2595485&tstart=0

  • Can I still use my "old" Mac after restoring Time Machine backup to a new Mac?

    Hi guys.
    Will I still be able to use my old Macbook Pro 2008 (Leopard) after restoring his latest Time Machine backup on a new Macbook Pro 2012 (Lion)?
    Using Setup Assistant and transfering data using Time Machine creats the same Account on the new machine that was on the old one. I just don't know how the old machine will react towards his clone. I don't want to make a mess...
    Please let me know.
    Thanks

    It should work if the drive is connected directly to your Mac. That is not the same as saying that it will work.
    Since Mountain Lion was just released, it might make sense to hold on a few weeks and watch the forums for new and unforeseen issues before you dive in.

Maybe you are looking for