|
|
10.5: Reconnect Time Machine backup after drive swap
Fantastic! Although I'm not a Terminal pro at all, I managed to reconnect my backup with this guide. Since I moved my Data from one MacBook Pro to a new one using Migration Manager, I did the logic board / MAC re-pairing in the same time.
10.5: Reconnect Time Machine backup after drive swap
Since I moved my Data from one MacBook Pro to a new one using Migration Manager, I did the logic board / MAC re-pairing in the same time. I don't want to spoil your success, but... So, you've used the Migration Assistent to copy your documents and some more (but not the whole system), after you installed Mac OS X (or, onto a system that had OS X pre-installed)? If so, then the old (and now current) backup is simply not a good representation of your current Mac. Thus: you might not be able to use it for a full restore! I'd say this hint is only safe to reconnect a backup to its original hard disk.
10.5: Reconnect Time Machine backup after drive swap
Though the 36 hours deep traversal may have fixed this after all...? In that case a full system restore may be possible, using this new backup or any newer backup (but not using backups that were created before the deep traversal, as I think those certainly do not match your current Mac).
10.5: Reconnect Time Machine backup after drive swap
Thanks for your reply. My priority was to get the new machine ready to work as fast as possible. I first did a block copy clone of my entire HD onto that last generation MacBook Pro, but it wasn't really satisfied with my System. That's why I migrated it, yes the whole, while I cloned the Time Machine Partition to another Disk before starting to fumble on it. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.07 seconds |
|