Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

LV426

macrumors 68000
Original poster
Jan 22, 2013
1,920
2,381
I’ve placed an order for a 16” MacBook Pro, as I’m getting sick to death of the flaky keyboard on my 2016 model. The latter has been repaired 3 times. I do have up-to-date software and a recent TM backup.

I was wondering if it’s safe to do a Time Machine install on an upgraded model like this, OS and all, to save a lot of time. I’m just thinking that the new machine might need different device drivers to work properly (e.g the display) that don’t exist in the TM backup files. How would the install handle that kind of situation?

Thanks for any advice.
 

LV426

macrumors 68000
Original poster
Jan 22, 2013
1,920
2,381
So, here we go, I did it. Installed on my new laptop from a TM backup using the Cmd-R option on boot-up.

It reported a success message after a few hours (I have several 100GB+ files). But, after a reboot, a solitary flashing folder icon with a question mark showed up. Ouch, that’s annoying. The option to analyse and repair didn’t help.

So, another reboot, Cmd-R, I chose the option to reinstall the OS, which it does by asking for a Wifi password and getting the code directly from the internet.

That worked. When it finished, I saw my familiar desktop login. All’s well that ends well, but I’m wondering if I did something wrong by invoking Cmd-R on a brand new machine...
 

Honza1

macrumors 6502a
Nov 30, 2013
940
441
US
I am confused. Why did you simply not migrated data from TM disk? There is Migration Assistant there for this purpose.
That is what is normal procedure. That way user accounts with data, apps, settings etc - all except system files - is migrated. You effectively overwrote everything, including system, and when system files were not suitable for the new hardware (no surprise with TM from older hardware) you had to reinstall new system files...
It should be fixed, but seems lot of unnecessary work.
 

LV426

macrumors 68000
Original poster
Jan 22, 2013
1,920
2,381
Well, I google how to install on a fresh machine from a TM backup before I started, and the migration assistant wasn't mentioned, but the Cmd-R option was. That's why I started this thread, because I was concerned that the TM backup wouldn't contain all the files needed for a new installation. Thus, apparently, this proved to be the case.

It's working now, but for future reference, if you get a new machine, at what point are you presented with the Migration Assistant doing setup? Thanks.
 

Fishrrman

macrumors Penryn
Feb 20, 2009
29,243
13,317
My pre-written suggestions:
=================
Fishrrman's "you can do it!" routine for migrating to a new Mac:

If you follow my instructions below, I guarantee a success rate of 98%:
PRINT OUT these instructions and check them off as you go along.

1. BEFORE you do anything else, run a "final" backup on your old Mac. Use an external drive for this. It can be either TM or a cloned backup using CarbonCopyCloner or SuperDuper. I prefer CCC.
2. Shut down the old Mac and disconnect the external drive
3. Take the new Mac out of the box and set it up on the table. DO NOT PRESS THE POWER ON BUTTON until step 8 (read on). You don't want to begin setup until "the right moment".
4. If you're using an external display, connect the display using the usb-c/VGA adapter/cable that you have
5. Connect the keyboard and mouse if you use them. I STRONGLY SUGGEST that you connect them DIRECTLY to the Mac.
6. If you use a hub, leave it DISCONNECTED for now
7. Connect your backup drive -- use a usb-c adapter if needed.

OK, we're ready-to-go, so let's get goin':
8. Press the power on button for the first time.
9. The new Mac may ask for help "finding" the keyboard, just follow instructions.
10. Begin setup. At the appropriate moment, setup assistant will ask if you wish to migrate from another Mac or drive. YES, you want to do this.
11. "Aim" setup assistant at the external backup. Setup assistant will need a little time to "digest it all". BE PATIENT and give setup assistant the time it needs.
12. You will now see a list of things that can be migrated, such as applications, accounts, settings and data.
13. I suggest that you select ALL of them.
14. Let setup assistant "do its thing". It's going to TAKE A WHILE to move things over. Again, be patient. If you have a lot "of stuff", it will take a lot of time!
15. When done, you should see the login screen. Go ahead and login.
16. Once logged in, things should look pretty much as they looked on your old Mac.
17. You should check all your apps. Some may not run, and may require upgrading.
18. You can set aside the old backup, or ... "repurpose it" to become the backup for the new Mac. I'd keep the old one around for a week or so, at least.
 
  • Love
  • Like
Reactions: Honza1 and LV426

zorinlynx

macrumors G3
May 31, 2007
8,352
18,581
Florida, USA
Always make sure your Mac is fully updated and do one more Time Machine backup before attempting to install from a TM backup on new hardware. This makes sure you have the latest version of MacOS that has hardware support for the new system.
 

Honza1

macrumors 6502a
Nov 30, 2013
940
441
US
Well, I google how to install on a fresh machine from a TM backup before I started, and the migration assistant wasn't mentioned, but the Cmd-R option was. That's why I started this thread, because I was concerned that the TM backup wouldn't contain all the files needed for a new installation. Thus, apparently, this proved to be the case.

It's working now, but for future reference, if you get a new machine, at what point are you presented with the Migration Assistant doing setup? Thanks.
Well, the #6 has complete extended explanation.

Short answer is "start and follow the steps"

Every Apple computer I got in the last ~12 years or so did this. Start, say hello, get few minor things done, and present me with question if I want to migrate from Time Machine or another computer. Impossible Should be impossible to escape it.
As I found out many times, for standard operations, do not over think these things. It was engineered to work, with high reliability, for dumbest user. It is the smart users, who are causing troubles. Normal Mac user has no clue what cmd-r does and what to do with it.
 

zorinlynx

macrumors G3
May 31, 2007
8,352
18,581
Florida, USA
Well, the #6 has complete extended explanation.

Short answer is "start and follow the steps"

Every Apple computer I got in the last ~12 years or so did this. Start, say hello, get few minor things done, and present me with question if I want to migrate from Time Machine or another computer. Impossible Should be impossible to escape it.
As I found out many times, for standard operations, do not over think these things. It was engineered to work, with high reliability, for dumbest user. It is the smart users, who are causing troubles. Normal Mac user has no clue what cmd-r does and what to do with it.

Yeah, technically cmd-R was meant for people restoring the SAME machine from backup after replacing or having to format the startup disk. That shouldn't happen normally for most users, especially since most Macs from the past few years have a built in startup disk that you can't easily change.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.