d00dism

It’s been a long time since I took a hard look at my backup situation, but a series of blog posts in my reader has caused some naval gazing.

A long time ago in a computer far far away

My backup plan was once dead simple. I used CCC or Super Duper to create a clone of my boot drive whenever I thought of it. Sometimes I was good and did it weekly, sometimes I went months without.

Thankfully I had no crashes during this period. I never had to experience the frustration of losing a month of data.

Let’s do the time warp again

Time Machine! I was so excited when I finally got a drive to use with it. I turned it on and got frustrated any time it monopolized my I/O attempting to back up. Honestly I can’t tell you if specifically Snow Leopard fixed it, but I haven’t gone searching for the Time Machine menu to stop the backup for a long time.

I still did my Super Duper backups, but it became less of a priority because it wasn’t automated.

Disaster

It finally happened. I lost my boot drive (which was under warranty thankfully). I could cool off the drive and get a few minutes of work, but not enough time to do a Super Duper backup and I/O just made it die faster. I was using my Super Duper drive to temporarily back someone else up.

Luckily, I had a Time Machine backup ready to go. That was almost not the case as just weeks before I finally replaced the power supply on my Time Machine disk (thank you OWC for quick diagnosis and replacement).

It was time to see if the machine would do its job.

It just worked

Once I got my replacement boot drive, it was time to stick in the SL disk and try the restore. As you can already guess, it worked. I selected my Time Machine disk and initiated the restore.

Your mileage may vary, but Time Machine is now my preferred method for incremental and bulk backup. There are a few reasons why.

1. I don’t have to do anything to keep it up to date. Seriously, no matter how many calendar reminders or OCD you are, backup plans fail when you need to do something on a schedule rather than the machine do it for you.
2. It protects you from your own stupidity. Clones are great, but they won’t help you dig out a file you deleted three weeks ago unless you either didn’t backup since then (shame on you) or you keep a clone rotation large enough to have a backup old enough (expensive and impractical for most as well as having the problem of requiring lots or manual interaction).
3. You can do a bulk restore easily despite it not being a bootable disk. Stick in your Mac OS X install DVD and you can do it with a few clicks.

The moving target

Time Machine works great if you have a desktop or regularly connect your computer to a series of peripherals, but I haven’t chained a laptop down like that in years. Needless to say, the cloning plan I used on my MacBook wasn’t working for me.

I could in theory use a Time Capsule to use Time Machine for this situation. Problem 1 is that I’m cheap. Time Capsules are expensive. Problem 2 is that assuming I could get it accessible using Back to My Mac behind my FiOS router, it’s not really supported.

The solution was to use Crashplan. If you use their software to backup to another computer belonging to you or a friend, it’s free. I have a computer that’s on a lot with lots of storage and it’s own backup plan in place! I installed the software, told the Mac Pro to use a specific hard drive as the destination, and initiated backup from the MacBook.

Now anytime the two are on at the same time, the MacBook will back up to my Mac Pro regardless of local network or over the Internet proximity. Crashplan has fantastic in the background incremental backup. It meets the requirement of doing its work without me.

I only have it set up to back up my home directory, but I don’t store significant irreplaceable data anywhere else, so at worst I reinstall and then restore my home directory.

The Achilles heel

As written (correctly) elsewhere, my backup plan is incomplete. One fire at my house would wipe it all out. More specifically, my plan doesn’t include offsite backup.

When I finally stop being cheap (can’t help it), I will probably sign up for Crashplan’s subscription service. I have two options for that.

1. I purchase the single computer plan and backup only the Mac Pro. That actually covers both computers.
2. I buy the family plan and set both computers to use it. The MacBook would still back up to the Mac Pro as well because assuming I connect it to my network, restoration would be much faster from the Mac Pro. It also lets anyone living with me back up their computers.

I’m not saying my plan is a blue print for everyone else. I am saying that you need to consider the profound importance of a backup strategy that requires no action on your part. The biggest risk in any backup plan is always you. Backups are for the improbable situation. The most probable unfortunate event is you failing to connect your backup drive and running your backup software. Take it out of the loop, or at the very least, make it a redundant bonus.

Something has been building steadily for a couple weeks now and I just can’t contain it anymore. After countless hours of reading though, the rage within me has reached the spilling level. I read nearly every Mac website I can find (via RSS). I can give non-Mac news sources a pass on this, but the rest of you should hang your heads in shame.

Macworld, as in Macworld Magazine and Macworld Expo, is spelled as I have it. Macworld Expo is like Mecca, but for Mac users. It’s the ultimate event in the Mac universe. Given that fact, why is it so god damned hard to spell it right?

I’ve noticed two groups are the worst offenders, or at least get under my skin the most: vendors sending out promotional emails and Mac news outlets and blogs. The two most common misspellings are MacWorld and Mac World. Let me tell you something guys, it’s your responsibility to at least be able to spell the name of the event.

The news sites/blogs are the worst because they act as authoritative sources about Mac culture and information. How am I supposed to take your predictions and prognostications seriously when you don’t even spell it right. No matter how hard I try to displace my thoughts, all those articles end up looking like:

At teh MacWorld expo I preedict the AWEsome iPhone!!11!!!!!11!!

So please, I beg of the Mac community: spell it right. Don’t look like an idiot. Don’t make us all look like idiots.

If you keep your eye on Macs, you probably already know about Boot Camp. It’s a bit of a surprise, but I suspect it was done so that users choosing to run Windows can do so in a safer manner with proper drivers. The drivers included with the new software are the key part of this announcement.

Hacking the firmware to coerce a Mac into booting Windows took a little while, but it wasn’t really all that complicated. However, putting money into a development staff for Windows drivers is quite an expensive proposition and it goes to show Apple’s commitment to leverage the move to x86 to their full benefit. They can easily scoop up fence sitters that afraid of losing the ability to run Windows.

It’s a bold move and I’m a fan.

Back in December, I made some predictions.

The quick recap is, I was completely right about the Powerbook (though I didn’t see the moronic name change coming). I didn’t see the iMac coming. The Mac mini rumor was nice, but ultimately, it wasn’t in the cards. My hope clouded my judgment.

iLife ’06 and iWork ’06: Yawn. Again.

I’m surprised at the complete lack of information about Leopard. The prospect of getting surprised is actually exciting. Apple may just sit on the features until after Vista appears. That might slow Microsoft just a bit.

Tags: macworld, puppy

Macworld’s lab tests of the new intel iMac confirm what I’ve been telling people since the Intel transition was announced.

I can summarize the results pretty quickly. Considering that the Intel processor in the new iMac is a dual core, the speed isn’t really that much better. In fact, taking that into account, it’s slower. Also, Rosetta isn’t the panacea that everyone bought into. I knew it wouldn’t be. It doesn’t work with anything that requires precise timing and it’s slow. Slow.

This shouldn’t be surprising, but considering what all the pundits said, you’d think it would be. I don’t think that the Intel transition will break Apple, but let’s not pretend it’s all candy and roses. It ain’t.

Tags: imac, intel, rosetta