Bootable backups always pay off eventually

I’ve been wondering, on and off for the last few months, why I persisted in nightly SuperDuper! backups in addition to Time Machine. Well now I know πŸ™‚

In the middle of my last post I mentioned that I may have just screwed my USB ports. I had. This is a real problem when USB is the only input device – even my bluetooth keyboard wasn’t working! Thankfully I have just booted from the SuperDuper backup and am trying to restore all of the kext in the system folder, according to the package list that’s what the installer changed.

Even if this doesn’t work though, and I have to restore from backup, I at least have something I was able to use instead of being left with a brick requiring 2-3hrs of system restoration. Note to self though: when booting from the SuperDuper backup, don’t leave the Time Machine drive plugged in. TM just tried to do a backup which really wouldn’t end well πŸ˜‰

I knew it was a good idea to keep these bootable backups going, I’d just forgotten why. As annoying as this will be it’s good to remind yourself now and then what the value of multiple backup strategies is. Even if it results in being so worried you’re up until 1am trying to fix it.

3 thoughts on “Bootable backups always pay off eventually

  1. You can also just boot from the OS X install CD and open the terminal application, or boot from a fresh install on an external drive or do an install in place instead of an actual restore from back up (it leaves all the data and just replaces the OS itself).

    In other words, OS X has tons of restore options from before the days of Time Machine that will still serve you well.

  2. I could even boot from the install CD and use a disk restore from my bootable backup πŸ™‚

    I hadn’t realised the OSX Installer has a terminal, that’s cool. However, doing a fresh install on an external drive has been obseleted by my Time Machine backups; it takes the same length of time but the TM restore will give me my system back immediately. Install-in-place would also do that except I’m running 10.5.7 and my install CDs are for an earlier release. Not impossible to recover from, but TM wins again.

    In any case I will probably do a TM restore tonight. Simply copying the kext extensions back onto the boot drive caused a kernel panic and I can’t be bothered finding the “rebuild kext cache on this other drive” command πŸ™‚

  3. haha, well that turned out to be really freakin easy.

    In my 1am sleepiness I restored the contents of /System/Library/Extensions but forgot to delete /System/Library/Extensions.mkext – hence the kernel panic.

    Surprisingly even deleting it on the non-boot partition immediately caused a rebuild, and now my system is booting normally. Woot!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.