New Laptop Time revisited — aftermath and more thoughts

When last we talked I’d just picked up my new laptop and was about to delve into migrating my universe onto it. I”m now fully migrated and settled in, and so it’s time for a bit of a post-mortem on the process and discuss what I did (and why) and which parts I like and which parts I probably need to think about some more…

The first thing I needed to do was install the upgraded hard drive (500 Gig, 7200 RPM). thanks to some very nice instructions from Other World Computing (where I bought the drive) and the fact that Apple made the unibody Macbook Pros easy units to swap drives in (Thank You Apple!) that took all of ten minutes.  I’ve done that enough times by now I could pretty much do it in my sleep, but it’s not always easy.

Once I did that, though, a bit of a quandry. I now have a Mac with an unformatted drive, a drive attached to nothing with MacOS X on it, and a need to get MacOS X on the new drive somehow. There are all sorts of ways to do that; I ended up using the recovery DVD and simply booting it, formatting the drive, and installing fresh from the DVD. That took about 30 minutes, very painless.

Other options: I could have wired the original drive into a housing and booted the mac onto it, then cloned the drive (or cloned the drives via my old Mac, or… or… and in reality, all of the other ways to do it would have been more complicated and taken longer, IMHO. That’s why the recovery DVD exists…

First thing I did: Cloned my old laptop drive (via Superduper) and then put that boot drive far away from potential chaos. I also took my old backup drives and put them far away as well. Before I started, I had THREE current, bootable copies PLUS my Time Machine backup. I took my secondary firewire drive and turned it off and unplugged the firewire so I couldn’t accidentally trash it (there was a 2nd current copy of that data in Time Machine). More copies a good thing when it comes to backups.

Once the OS was installed on the new drive, I booted onto it and it ran through Apple’s standard setup process. Put my old mac in firewire target mode, connected the two, and let Apple’s software copy the data. 4.5 hours later, data is copied and my new mac looks like my old Mac (except where it doesn’t… there are a couple of things to remember here….)

Then you fire up Software Update and let it download all of the updates. That took about an hour.

Then I fired up the Application DVD and fired it up (it is also the hardware test DVD in this generation of new-machine disks) – since I never upgraded to iLife ’09, I needed to restore the applications that were on the disk I didn’t use, and I couldn’t do that until after the migration was done. That took another 45 minutes or so.

One thing that isn’t done by the migration assistant is XCODE; if you have the Apple developer environment installed, it won’t migrate it. That’s not a big deal, and there was an update I needed to install anyway, so the last thing I did before crashing was start a download of the latest tools from the developer site. And then I crashed.

Started about 5:30PM, crashed at 1AM with the migration complete and the system fully functional (minus XCODE). And almost all of that time was doing things I wanted to do while the system was doing whatever it was doing. I probably spent an hour total actively working on the update, the rest was the computer doing things while I waited.

I know some people still prefer to move stuff over manually and don’t want to trust the migration assistant, and I suppose if you’re someone who’s off hacking the guts of the system, you might need to. My view is “have fun. let me know when you’re done”, and I long ago learned to trust Apple knowing how to do this better than me. I also learned long ago not to hack the parts of the system that Apple “owns” — if I need a custom version of Perl or want to run an Apache server, I create a user and install the software into that user and build my own custom versions and run those instead. That does two things: it isolated the installed system from breaking because I inadvertantly step on something it depends on, and it isolates my custom stuff from being broken at a bad time by a software update that steps on my customizations. Everyone wins — and since it lives in a user account, it’s compatible with the migration assistant. (this was a trick we learned to figure out how to build custom hacks into Perl and Apache while still being generic and compatible inside the Apple data center, so the data center could maintain the boxes and OS without impacting production systems, and we could build the tools we needed without the data center staff having to be involved or approving stuff. works great, once you get in the habit of doing it).

One thing to realize when you upgrade your computer is that a few things are going to change. In my cast, the necessary changes were that my old laptop had a DVI video out, and my new one has this new mini-video plug thing. Also, my old laptop was Firewire 400, the new one is Firewire 800. That meant a trip to Fry’s for a new video dongle and cable, and some replacement firewire cables with the new plug types. While there, I realized they had a 2Tb drive for $110, and that solved my backup problem. This all happened while my data was migrating, so it was all ready when the new machine was ready…

Next morning was installing the dev tools, upgrading a few apps I realized needed patches (especially Parallels and the XP partittion), and then setting up backups.

These things are easier if you’re careful how you store stuff on disk. Over the years, I’ve gotten pretty careful about where I put my data — yes, I use Documents and Pictures and Music and Movies and I keep stuff where it “belongs”, and I limit what lives on my Desktop to active files and projects. That REALLY simplifies major migrations like this. Times like this ARE a good chance to go through your files and identify stuff that you can throw out or archive offline, and in fact, I did take about 250 Gigs of data (mostly low-quality pictures) and copied them to two separate drives, one which will live in my desk, one which will live offsite. Next time I do this kind of archiving, I’ll buy a couple of new drives, copy the data from this archive onto it, add the new archived data, and then store a copy offsite. One way to limit the “I can’t read my only copy of this” is to keep two copies, and the other important way is to refresh the archive every so often. Given you can buy 2TB drives for $110 today, there’s really no reason not to simply replace your archives with a new, really larger drive every couple of years. And so I shall. And remember, THIS is the data I never expect to ever need or touch again, but am keeping around in case I’m wrong. So I’m comfortable only keeping two copies of it…

I plopped the new 2Tb drive in the dock. I ALSO took the old 2Tb backup drive and stuck it in a static free envelope and it and the offsite copy of the archive data and my old laptop then were put far away from my working area so I wouldn’t accidentally do something to them. In the morning, when I go to work, the offsite data will go with me. In a week or so, once i’m absolutely sure I have everything I need off of it, I’ll wipe the disk on the old laptop, and then it’ll go to a friend who refurbishes them and lends them out to underpriviledged kids that otherwise wouldn’t have computers.

Backups… When you’re schlepping around half a terabyte of data, it takes time. I fired up Superduper to clone my new boot drive to the 2TB drive and set up a timed refresh for every night at 1:30AM. Once that was done, I fired up Time Machine and got it started.

DAMN but Time Machine is slow. It copied data at maybe 40% of the speed of SuperDuper, and SuperDuper is pretty much as fast as you can get. I keep finding reasons not to like Time Machine in large data environments, but not enough that I’m ready to turn it off. Just don’t depend on it as your primary backup, folks, not if you do large data sets  like this. For my mom — it’s great. For me, I get annoyed a lot.

Once my boot disk was copied (twice — once cloned, once Time Machine) I plugged in my secondary firewire and turned it on. And then fired up the backups on IT. And timed them, because I was now annoyed at Time Machine and wanted to make sure there wasn’t a performance problem with the dock. It took me 2 hours to finder copy 280 gigabytes to a 5400RPM drive in the dock. It took me over 5 hours for Time Machine to back up 165 gigabytes from that same source drive to that same dock with a 7200 RPM drive in it.

DAMN but Time Machine is slow.

And once that was done — I was done. Total time invested: about a day and a half of clock time. 7.5 hours of upgrade and migration, of which my time spent actively involved was about 1 hour. Getting backups set up and all of the data backed up? About 12 hours, of which I probably spent 2 hours actively involved and the rest of the time puttering. And about 2 hours involved in getting XCODE re-installed and doing the various updates I did (most of the time updating was getting XP patches up to date and getting the anti-virus stuff updated…)

Not bad.

Pretty much everything went as planned. there was one thing I did I want to do differently: I bought a VGA dongle and a VGA cable to replace the DVI setup I had. I don’t think it’s as crisp as the DVI was, so I’m going to go get a DVI dongle and go back to the old cable. I do need the VGA dongle as well, but it’ll live in my bag and get carried around for when I need to wire into a project for a presentation… All in all, not bad at all.

I also need to find and invest in a few really short (1-1.,5 foot) 800-800 firewire cables for neatness sake. Maybe a firewire hub; and clean up my cable monster behind the desk, now taht I know where everything needs to go…

When doing something like moving everything to a new laptop I find it’s a good time to reconsider how you use the system and what needs to be fixed or changed or upgraded. There have been a couple of projects I’ve been meaning to get to — and this seems to be a perfect excuse to actually get to them. One is that my contact list/address book has become a complete shambles; some of you are in my gmail lists, some in my Mac Address book, some in my entourage book at work, some on my phone and nowhere else. That’s long-term untenable and potential disaster, so I’m merging everything into a single list again (using gMail, and that syncs to my mac address book, and THAT syncs onto MobileMe and back out onto my phone), That’ll at least get the chaos under control for  awhile, and keep it organized to the degree that I’m smart enough to only add data to the primary address book (but don’t bet on it…).

the other is that it’s well past time to get more paranoid about online accounts and passwords and get all of that data out of the way too useful but not terribly secure browser autofill and into something a bit more — discrete. And that is 1Password, a secure wallet that can keep a set of data and make it available on my Mac and iPhone/iPod_Touch (and there’s a way to sync data out to webOS via Dropbox). I’m going to be installing it tonight and as I start hitting up sites setting them up in 1Password, changing all of the passwords (way overdue) and getting that data out of the browser. If you haven’t done that yet — you really need to think about it. Just for peace of mind, if nothing else.

The new box? awesome. Spent some time in Lightroom 3, and rendering of images is a LOT faster, which makes me happy. I haven’t done a test import, but I can definitely feel the speed difference, so I’m hopeful. We’ll see, I’m going to head out and shoot monday or tuesday and see how import speed goes.

All in all, I don’t miss the larger screen or faster CPUs at all. At this point, that seems like money well not-spent.

You might also want to read:

1. new laptop time….   So a few weeks ago my laptop started giving me hints it was thinking about retirement. It’s given me yeoman service — it was...
2. Did Some Insider Just Spill The Beans On New Apple Laptop? Why does everything suck?: Did Some Insider Just Spill The Beans On New Apple Laptop?: Sure would be cool if they sold a product that...
3. At the rate the market is going, Apple may need a sub-$500 laptop on Tuesday » VentureBeat At the rate the market is going, Apple may need a sub-$500 laptop on Tuesday » VentureBeat: Former Engadget editor Ryan Block more or less...
4. Flickr interestingness revisited A while back I posted some thoughts on Flickr Interestingness. While playing around with MyBlogLog today, I noticed a new link to that posting. It’s...
5. James Mirtle: Todd Bertuzzi: The aftermath – A hockey journalist’s blog James Mirtle: Todd Bertuzzi: The aftermath – A hockey journalist’s blog: To those who have coshed Bettman’s decision: At some point, Bertuzzi does have to...