Time machine - starting over?

Can I just turn TM off, connect a new, larger, external drive and start over again? My current external is too small and for reasons too long to mention, it's not worth keeping the couple days of backup that are available. Is it that simple? Or if I do that, will it think there are backups on the other drive and not give me a complete backup first time through. I tried looking around but couldn't see this topic anywhere. Thanks for your help

Yes.
Note that the first update will take a couple of hours (I figure about 10 mins per GB).
But otherwise yes, plus it in go to System prefs time machine sleect the new disk and your all good to go!
If you want to sue the old one again use Disk utility and clear it out.
Also if you have a much larger drive now PARTITION IT (Disk Utility) make say 100 GB for stuff and 200 GB for backups....
Hope this all helps!

Similar Messages

  • Time machine started over after a complete restore, how to get to older?

    Yesterday, photoshop and parrallels started crashing and I could not get them working, So I decided to do a complete system restore from install disk time machine from the day before when everything was working fine.
    so it restored the system to its previous state. parrallels was still not working correctly so I restored the folder from a week or so ago. That didn't get it back either, so I thought of maybe reloading the application from an earlier time period might help.
    But, time machine has started itself over. there is only backup data from this morning in the time machine internal backup drive. How do i get to my older backups? Do they just go away after a system restore?

    Sam,
    No, you need to Ctrl-Click the Time Machine DOCK icon. Then choose "Browse Other Time Machine Disks...".
    Here is a thought. When you did the restore, what Mac OS version did you restore. Your states say 10.5.5 but might your Mac have been restored to 10.5.4 or earlier with your restore?
    I have found in my own testing, that since the 10.5.5 update, "Archive & Installs", "Erase & Installs", and "Restore System From Backup..." no longer trigger a new full backup. That is they continue to use the same backup set as before. (Note though, you will likely see a very large incremental backup, but not necessarily a new Full Backup set.) See my comments here:
    [http://discussions.apple.com/thread.jspa?threadID=1771493&tstart=0]
    If, however, you restored to a Mac OS version previous to 10.5.5, and then allowed Time Machine to perform a backup, then a new Full Backup would be preformed. Likely, you might be able to avoid this if you do the restore (prevent Time Machine from backing up), update to 10.5.5, then allow Time Machine to backup.
    Cheers!

  • Day Two: Time Machine Started Over Again

    I bought a new external 500 GB drive yesterday, connected it to my computer, and started Time Machine. A few hours (more than a few), the initial 70GB backup was complete. When I got home today I plugged it back in and it ran one or two more incremental backups. TM showed my oldest backup at last night, then several since.
    Then I did what I'd intended to do once I had the initial backup made: I plugged it into my Airport Extreme. Good old Apple software recognized it the moment I mounted it, and I didn't even have to select a new volume in TM preferences.
    Then, at the next scheduled incremental backup, TM started over from scratch. It is copying EVERYTHING to a disk image that it mounted, a disk image stored on the 500 GB drive. And now, in TM prefs, my oldest backup is '--' and the newest is the one in progress. It is like it disregarded everything I did today and is starting a brand new backup on the same drive.
    Is this normal behavior? How do I merge the two, or tell TM to just use the one that it started earlier? Is that earlier backup worth anything now, or is it just a lump of virtual coal on my drive?

    Take a look at this discussion. It is not a solution. Apparently it is normal behavior.
    http://discussions.apple.com/thread.jspa?messageID=6962658&#6962658

  • External WD Passport won't recognize after Time Machine start.

    I bought a WD passport 500 gb drive and when I initially plugged it in time machine saw it and when I asked it to use it- something happened and now NO icon appears in order to be selected nor does an icon show anywhere to even select. I changed the drive and the new one does the same. Cycles continously and never mounts. Did the usual- changed ports and changed wires. It just isn't recognized no matter what. What to do?

    jimmyb12015 wrote:
    No. The drive is not reflected in any window. Not on my computer or disk utility. It initially was shown just before Time Machine started. It was then I escaped from time machine and I eventually returned the first drive after reformating it to fat 32 (on a windows machine) and it still wouldn't show up the MAC. The second drive now does the same as the first (doesn't show and cycles) but never showed up in any form on the MAC.
    If the MAC has a register then my guess is some information about any external disk has been altered and I should need to to return it to it's original setting. That is because the second drive is doing the same as the first. I just don't know how to do that or even look.
    If it uses the MBR (Master Boot Record) partition scheme, for Windoze, TM may have started to reformat it to GUID, but had that interrupted when you cancelled. If DU can't see it at all, there's not much you can do from your Mac. You may need to reformat it on a PC, then do it over on your Mac, via item #5 in the FAQ.
    There are reports of problems with some WD drives having not working well on Macs. You might want to check their website support/forums, etc.

  • HT201250 once time machine starts running, it never stops. what could cause this?

    Using WD, My Passport for Mac, 2TB with Time-Machine. Updated software on MacBook, now once time machine starts running an update it does not stop untill  cancel it!

    1. The first time takes very long always, after that it will only do changes very hour and you will not notice it. The drive must be correctly formatted, Guid Partition Table, Mac Os Extended (journaled).
    2. If you installed any of the 'smart' software that came with the disk (specifically with the WD disk), you have to uninstall it completely immediately, because it will cause data loss and speed at the minimum: in macs you do not not need such additional software, just make sure that the disk is correctly formatted. If you had such software installed, and now uninstalled, you better reformat the drive, restart the mac, and then start all over again with TM.
    Lex

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

  • HT3231 Is it better to migrate to a new MacBook Pro using FireWire, from Time Machine, or over ethernet?

    Hello,
    Is it better to migrate to a new MacBook Pro (non Retina display) using FireWire, from Time Machine, or over ethernet? The older Mac is a MacBook (Intel, 2007 vintage). The Time Machine backup is to a Western Digital external drive with FireWire & USB ports.
    Thanks!
    Chips

    Thanks for the helpful reply.
    After posting, I read & researched further. We're going to be limited by the hardware – the MacBook & external drive both have FireWire 400, & we don't have a 400 to 800 cable or adapter. So we'll connect by ethernet, & be patient that it make take some time.
    I have to assume that Migration Assistant will be just as comprehensive regardless of the connection method / protocol.
    Best!

  • Since upgrade, Time Machine starts and stalls.  Waited 24 hours. Formatted disk-no change.

    Since upgrade to Mavericks on Mini, Time Machine starts and stalls.  Says "292 Mb of 147.68 Gb", wheel spins. Waited 24 hours, no change. Formatted disk-no change.  Tried every solution found in threads; no fix.  Doing manual backups. Help!

    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 that corresponds to an abnormal backup. Now
    CLEAR THE WORD "Starting" FROM THE TEXT FIELD
    so that all messages are showning, 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 (command-V) into a reply to this message.
    If all you see are messages that contain the word "Starting," you didn't clear the text field.
    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.

  • The backup disk image "/Volumes/Data/David Witkowski's Mac Pro.sparsebundle" is already in use.  Whenever Time Machine starts to backup to Time Capsuel I get the previous error message. I need some help to fix this.

    The backup disk image “/Volumes/Data/David Witkowski’s Mac Pro.sparsebundle” is already in use.  Whenever Time Machine starts to backup to Time Capsuel I get the previous error message Where can I find this disk image?. I need some help to fix this.
    Thanks,
    David W

    There are multiple answers and solutions if you look just to the right under the heading of More Like This.

  • Time Machine start then stop after few seconds

    Hi,
    I've tried to reset Time Machine (trashed the library plist file, erased the backup HD), also installed Time Machine Buddy widget.
    When I start a fresh new backup, Time Machine start indexing, then stops without backup anything.
    The error log of Time Machine Buddy widget is this:
    Starting standard backup
    Backing up to: /Volumes/TimeMachine/Backups.backupdb
    Backup content size: 156.0 GB excluded items size: 1.8 GB for volume Mastoidontico
    No pre-backup thinning needed: 185.11 GB requested (including padding), 1.82 TB available
    Waiting for index to be ready (101)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    LaunchServices: bad alias at 0x1041d7094, size 104, CSStore size 4391026
    * process 240 exceeded 500 log message per second limit - remaining messages this second discarded *
    2010-02-02 18:47:12.920 ReportCrash[271:2703] Saved crash report for backupd[240] version ??? (???) to /Library/Logs/DiagnosticReports/backupd2010-02-02-184712localhost.crash
    Any help to solve my problem?
    Thanks!

    Process: backupd [240]
    Path: /System/Library/CoreServices/backupd
    Identifier: backupd
    Version: ??? (???)
    Code Type: X86-64 (Native)
    Parent Process: launchd [1]
    Date/Time: 2010-02-02 18:47:12.319 +0100
    OS Version: Mac OS X 10.6.2 (10C540)
    Report Version: 6
    Exception Type: EXCBADACCESS (SIGSEGV)
    Exception Codes: KERNINVALIDADDRESS at 0x000000014c486000
    Crashed Thread: 2
    Thread 0: Dispatch queue: com.apple.main-thread
    0 libSystem.B.dylib 0x00007fff80044e3a machmsgtrap + 10
    1 libSystem.B.dylib 0x00007fff800454ad mach_msg + 59
    2 com.apple.CoreFoundation 0x00007fff868377a2 __CFRunLoopRun + 1698
    3 com.apple.CoreFoundation 0x00007fff86836c2f CFRunLoopRunSpecific + 575
    4 com.apple.CoreFoundation 0x00007fff868369b6 CFRunLoopRun + 70
    5 backupd 0x000000010000d2f1 0x100000000 + 54001
    6 backupd 0x0000000100004014 0x100000000 + 16404
    Thread 1: Dispatch queue: com.apple.libdispatch-manager
    0 libSystem.B.dylib 0x00007fff8005dbba kevent + 10
    1 libSystem.B.dylib 0x00007fff8005fa85 dispatch_mgrinvoke + 154
    2 libSystem.B.dylib 0x00007fff8005f75c dispatch_queueinvoke + 185
    3 libSystem.B.dylib 0x00007fff8005f286 dispatch_workerthread2 + 244
    4 libSystem.B.dylib 0x00007fff8005ebb8 pthreadwqthread + 353
    5 libSystem.B.dylib 0x00007fff8005ea55 start_wqthread + 13
    Thread 2 Crashed:
    0 ...ple.CoreServices.CarbonCore 0x00007fff85070987 CSStoreGetUnit + 84
    1 com.apple.LaunchServices 0x00007fff85df44a3 _LSBundleFindWithNode + 544
    2 com.apple.LaunchServices 0x00007fff85decc79 _LSFindOrRegisterBundleNode + 219
    3 com.apple.LaunchServices 0x00007fff85decb2d _LSCopyItemAttributeForRefInfoWithOptions + 201
    4 com.apple.LaunchServices 0x00007fff85deea77 prepareAttributeValueForKey(__CFURL const*, __FileCache*, __CFString const*, void const**, __CFError**) + 79
    5 com.apple.LaunchServices 0x00007fff85dee9dc prepareDistinctLocalizedNameValue(__CFURL const*, __FileCache*, __CFError**) + 36
    6 com.apple.LaunchServices 0x00007fff85dee9b3 prepareLocalizedNameValue(__CFURL const*, __FileCache*, __CFError**) + 9
    7 com.apple.LaunchServices 0x00007fff85dee7bc LSPropertyProviderPrepareValues(__CFURL const*, __FileCache*, __CFString const* const*, void const**, long, void const*, __CFError**) + 51
    8 ...ple.CoreServices.CarbonCore 0x00007fff85081c90 prepareValuesForBitmap(__CFURL const*, __FileCache*, _FilePropertyBitmap*, __CFError**) + 264
    9 ...ple.CoreServices.CarbonCore 0x00007fff85080779 _FSURLCopyResourcePropertiesForKeys + 980
    10 com.apple.CoreFoundation 0x00007fff8683f402 CFURLCopyResourcePropertiesForKeys + 98
    11 com.apple.DesktopServices 0x00007fff84b30169 TCFURLInfo::FetchProperties(bool) + 91
    12 com.apple.DesktopServices 0x00007fff84b2ffbd TCFURLInfo::Initialize(__CFURL const*, bool, bool) + 183
    13 com.apple.DesktopServices 0x00007fff84b8e07f TCFURLIterator::NextRaw(TCountedPtr<TCFURLInfo>&) + 79
    14 com.apple.DesktopServices 0x00007fff84b8e11a TCFURLIterator::Next(TCountedPtr<TCFURLInfo>&) + 40
    15 com.apple.DesktopServices 0x00007fff84b8f517 TDeepCFURLIterator::NextInternal(TCountedPtr<TCFURLInfo>&, int&, int&, bool&) + 73
    16 com.apple.DesktopServices 0x00007fff84b8f651 TDeepCFURLIterator::Next(TCountedPtr<TCFURLInfo>&, int&, int&, bool&) + 49
    17 com.apple.DesktopServices 0x00007fff84b95629 TCopyReader::GetNextItem() + 1039
    18 com.apple.DesktopServices 0x00007fff84b95fac TCopyReader::Read(unsigned long long, TCountedPtr<TCFURLInfo> const&, TCountedPtr<TCFURLInfo> const&) + 128
    19 com.apple.DesktopServices 0x00007fff84b80f27 TFSCopyOperation::CopyToTarget() + 607
    20 com.apple.DesktopServices 0x00007fff84b82d9f TFSCopyOperation::DoCopy(TCountedPtr<TCFURLInfo> const&) + 595
    21 com.apple.DesktopServices 0x00007fff84b78a68 _NodeOperation + 469
    22 backupd 0x00000001000164af 0x100000000 + 91311
    23 backupd 0x0000000100015923 0x100000000 + 88355
    24 backupd 0x000000010000ffc7 0x100000000 + 65479
    25 backupd 0x000000010000a7e2 0x100000000 + 42978
    26 backupd 0x0000000100006927 0x100000000 + 26919
    27 com.apple.Foundation 0x00007fff88a2be99 _NSThread__main_ + 1429
    28 libSystem.B.dylib 0x00007fff8007df8e pthreadstart + 331
    29 libSystem.B.dylib 0x00007fff8007de41 thread_start + 13

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

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

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

  • 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

Maybe you are looking for