There is a simple fact we all try to ignore (things die). In this case, one of the computers I use on a daily basis decided to have a snit (and go to digital heaven or what ever alternatives exist for bits) over the weekend. First, when I powered it on, I was presented with the famous chkdsk utility. After running through that, I then saw the infamous “Startup Repair Launcher.” That is never a good sign. I knew this was going to happen as I had experienced several bouts of chkdsk recently (and they seemed to be increasing in frequency). I thought readers might be interested in learning more details.
I realize that hard disk corruption can be the symptom of a virus. That being said, I keep my anti-virus suite up to date and periodically scan my computer. I did not see any evidence of malware. Nor do I see evidence of malware when I swap files from one computer to another (and I run different security suites on different computers). Frankly, I just wore the puppy out (as best as I can determine).
Since I was in the middle of some projects, I needed to obtain another computer to keep going on these projects. I realize this is not an option for everyone, but I do plan to do more traveling in the coming months and needed one a bit more lightweight anyway. The one I selected has a 4K display, the same processor, more memory and a slightly larger hard drive. Oh, yeah, I paid less than 50% of what I paid for the prior computer. Moore’s Law remains alive and well in 2015. Ok, it does lack a CD/ DVD drive. But, I can’t recall the last time I used one. The 4K display did take some getting used to (I am not used to over 3000 pixels wide on a laptop screen – and I have to remember to resize all my screen captures as they are now all gigantic). Since I needed to keep going on the projects (and it was going to take multiple days to obtain the replacement drive, my only choice was to go with a replacement. Yes, I could have used my MacBook, but I typically travel with that and did not want to mix projects on different devices (it just makes my life even more complicated and some of these projects should not be on computers I use while traveling).
So, what are some of my observations as I recover from the inevitable hard drive failure.
First, let me stress that your mileage may well (and should) vary from mine. That being said, there are some fundamental truths.
1 – Have a solid backup that you have tested. Yep, did that. I use Carbonite. You may want to use that or something else. That being said, backup your files (and back them up in some off site facility). It is also important to have the ability to selectively access files you have backed up. In the case of the particular computer, there were over 350,000 files backed up (taking up nearly 1/2 TB of storage online). Yes, it will take a while to download them. Fortunately, I have a fast network at home. Yes, I needed more immediate access to some files (which is where a web interface comes in very handy). I was able to download those files in a relatively short time (of course, it does help to keep materials organized so you can quickly locate them).
2 – Make certain you have key files (such as license keys also backed up). Yes, I keep a copy of everything I ever purchase (including the provided license key). You might want to keep these in a separate location (as executable files are often not backed up). This means you need to download and install the appropriate software. I also keep a copy of the website URL so I can more quickly reinstall. You will also need to have email access credentials available (in my case, I had to install a new version of my local eMail client). This meant I had to provide access credentials for each email account once I had installed the client again.
3 – Keep copies of your virtual machines on a removable hard drive (these are typically not backed up by software like Carbonite). If you think about it, restoring these files from the web would be a major chore (as many are multiple GB in size). Keeping local copies of the appropriate files means you only need to restore and then update each virtual environment (since changes will likely have happened since your last local backup).
4 – I tend to keep the majority of my materials online. This means I already have ready access (via sFTP) to the majority of the teaching materials I use (and the presentations I give in the summer). I recommend keeping materials in a secure area online.
5 – One thing I did not consider were the original drivers for the failed computer drive. Luckily, I was able to visit the vendor website and download those drivers anew. This helps me get ready when I replace the corrupt hard drive on the older computer.
So, how is this working out? As I write this, I have had to order a new hard drive for the affected computer (the drive really is toast). I also purchased a new machine. I was able to swap my Creative Cloud software overnight. The longest time was downloading the current versions of each application. I am in the process of restoring the majority of files. However, I have a meeting with a number of individuals Monday evening (I am writing this on Sunday and it will post on Wednesday). What I prepared for that meeting was readily available. Essentially, I spent a couple of hours setting up appropriate software installs (yes, I use tools like Ninite to pull a large amount of open source software). I have likely overlooked some software and will install that when I need it.
That being said, it took me roughly the same amount of time to locate and purchase a new computer as it took to be back up and running. Not everything is completely downloaded (although needed files are still readily available via the Carbonite web interface to selectively download backed up files), but in only a few hours, I do have the ability to continue various projects with limited interruption. This is partly why I keep so much information online (and on servers).
Once I install a replacement hard drive on the failed computer, I will try to remember to provide another weblog post on my experiences in that realm.
I am curious if you have experienced similar recovery issues (or what your recovery issues were when you experiences a hardware failure). As always, I look forward to your comments.