Skip to main content

Migrating from the Macbook Air to the Macbook Pro

My Macbook Air started to show wear and tear after a couple of years of heavy use. Five of the keys on the keyboard broke and had to be replaced, despite my light touch typing--honestly, and the battery has moved from the warning that it needs service to retaining electric charge for shorter and shorter periods of time, to not holding a charge at all.

For my next device I contemplated getting another Macbook Air with the highly enviable 12hr battery life, or switching back to a 15 inch Macbook Pro, and enjoying a more powerful machine, with a retina display and a respectable 8 hours of battery life. The prospect of more screen real-estate, and more processor power was too enticing, so I ended up getting the Macbook Pro despite the weight difference.

Since I accumulated 3+ years worth of data and software on the Air, I did not want to repeat the process of reinstalling apps from scratch and searched for an easy way to migrate the data to the new machine.  Most of the online recommendations were to use the Migration Assistant during the initial install phase. I decided to give it a try. I ran through the install process, created an account on the new new Macbook Pro, and started the Migration Assistant on the old Air and the new Pro. I chose migration over Wifi since I did not have a firewire cable handy, which turned out to be a mistake. Either due to a bug or an unreliable Wifi connection, the migration assistant would crash on both computers when it tried to migrate data between the machines.

I did not give up on the Migration Assistant, and decided to try another method: migration using a Time Machine backup. I took a full backup of the Macbook Air, which took roughly 8 hours to finish, and used the Migration Assistant to transfer that to the new Pro. The migration initially failed since my user name existed on the new machine--an easy fix by renaming the user, but then after starting the migration again,  the data copying was stuck for almost 11 hours with no progress. A quick search online revealed that this is a widespread problem, and not an isolated instance.

I decided to try my luck elsewhere. Although Apple does not recommend restoring a computer from a backup of another computer, I decided to give that a try,  especially since some of the applications I have installed including VPN and MacPorts store their data in non-standard locations.

I booted the new Macbook Pro in recovery mode, and  chose restore from Time Machine. I left the machine running overnight--the full restore took about 6 hours to finish, and by the end I had an identical setup to the one I had on the Macbook Air. I had to re-enter my license information for my applications, and apart from a couple of minor glitches with the Kindle App, and iCloud accounts which were easy to fix, everything worked like a charm, and I am very pleased with the result.

Hopefully I won't need to migrate computers anytime soon, but if I have to, now I know how to do it using Time Machine backups.
Labels:

Comments

Post a Comment

Popular posts from this blog

Kindle Paperwhite

I have always been allergic to buying specialized electronic devices that do only one thing, such as the Kindle, the iPod, and fitness trackers. Why buy these when technology evolves so fast that a multi-purpose device such as the phone or a smart watch can eventually do the same thing, but with the convenience of updates that fix bugs and add functionality? So, I was shocked when this weekend I made an impulse buy and got the newest Kindle Paperwhite—a special purpose device for reading eBooks. I was walking past the Amazon store in the mall and saw that the newest Kindle Paperwhites were marked down by $40 for the holidays. The device looked good in the display, so I went in to look at it closely. The Paperwhite is small and light, with a 6” screen that is backlit and waterproof.   The text was crisp and readable, and in the ambient light, it felt like I am reading a printed book. I was sold and bought it on the spot. At home I have struggled to put it down. The bo...
2 comments
Read more

A paper a day keeps the doctor away: NoDB

In most database systems, the user defines the shape of the data that is stored and queried using concepts such as entities and relations. The database system takes care of translating that shape into physical storage, and managing its lifecycle. Most of the systems store data in the form of tuples, either in row format, or broken down into columns and stored in columnar format. The system also stores metadata associated with the data, that helps with speedy retrieval and processing. Defining the shape of the data a priori, and transforming it from the raw or ingestion format to the storage format is a cost that database systems incur to make queries faster. What if we can have fast queries without incurring that initial cost? In the paper " NoDB: Efficient Query Execution on Raw Data Files ", the authors examine that question, and advocate a system (NoDB) that answers it. The authors start with the motivation for such a system. With the recent explosion of data...
Post a Comment
Read more

A paper a day keeps the dr away: Dapper a Large-Scale Distributed Systems Tracing Infrastructure

Modern Internet scale applications are a challenge to monitor and diagnose. The applications are usually comprised of complex distributed systems that are built by multiple teams, sometimes using different languages and technologies. When one component fails or misbehaves, it becomes a nightmare to figure out what went wrong and where. Monitoring and tracing systems aim to make that problem a bit more tractable, and Dapper, a system by Google for large scale distributed systems tracing is one such system. The paper starts by setting the context for Dapper through the use of a real service: "universal search". In universal search, the user types in a query that gets federated to multiple search backends such as web search, image search, local search, video search, news search, as well as advertising systems to display ads. The results are then combined and presented back to the user. Thousands of machines could be involved in returning that result, and any poor p...
Post a Comment
Read more