Diary of a Network Geek

It’s almost the end of the year and most people are wrapping up projects and thinking about how they’re going to squeeze in their last vacation days.

But, not if you’re in IT.
No, if you’re one of the over-worked, under-paid technology “elite” in the corporate world, you’re working harder than ever right now.  While everyone else is taking time off, you, like me, are trying to get all the system maintenance done that requires everyone else to be off your systems.   Well, while you’re waiting for them to get out of the office so you can start your work, here are some things to think about.

When was the last time you had to restore a backup?  Have you ever even tried to restore any files from those backups that you worked so hard to get running right when you setup your servers?  Well, now is the time to try it.  Trust me on this, but you don’t know how good your backup is until you try to restore.  Now, you may not be able to do a full server restore on fresh hardware, but, if you can, do it.  That’s the only true test of your disaster recovery plan.  Barring that, though, at least try to restore some files from random places on the server, just as a check to make sure it works.

And, while we’re talking about backups, how is your off-site rotation working?  If you’re in a large company, you probably have a long-standing system for rotating backups off-site in case of a massive disaster, but many smaller companies don’t.  Generally, what I suggest to people is that there should be one full backup off-site, one coming back or leaving, and one on-site.  The most current, usually, should rotate off-site just after completion and be off-site for two weeks, or, really, off-site for one week and coming back on the second.  There are plenty of  services to do this, but even just taking them to the network manager’s house is better than nothing.  Just somewhere relatively secure that’s not the same as the site you’re backing up, just in case the entire building catches fire or is demolished in a hurricane.  You get the idea.

Now, something else to consider, if you run Windows Server is Active Directory.
Mostly, your backup program should be taking care of this, but sometimes funky change creeps in when you don’t expect it.  Back in the days when I was more than an IT department of one, I was a big believer in getting baselines.  Every once in a while, it’s nice to take a snapshot of what’s working so that when it inevitably breaks, you can see what might have changed to break it.  This is especially true of things like Active Directory.  Every year, AD gets more and more complicated and, as your network grows, your individual AD tree will get more complicated, too.  Now, assuming that things are running well, is a great time to take a snapshot of your AD tree for a baseline to use in the coming year.
Tech Republic has a good article on how to use a free tool from Sysinternals to do just that.  Check it out.

And, for those of you who don’t have an IT department, or are a sole-proprietor, don’t think you can just slide, either.
Chances are your clients are taking more time off and you’ll have some down-time, too, so now is the perfect time to review your backup plans.  Many of you may not have much of a plan, or much of a budget to get something working for you.  Well, don’t worry, Tech Republic has some creative suggestions for backups to fit most situations. Do yourself a favor and go check them out now.  Then actually implement one before the start of the new year.  Do it now, before you need to restore data from a crash.

Trust me.  Make sure your backups are running before you need them.  You’ll thank me later.

Advice from your Uncle Jim:
"Men are born with two eyes but with one tongue, in order that they should see twice as much as they say."
   --Charles Caleb Colton

I was going to share this right before Halloween, but something better came up, so consider this a “Halloween Chaser” to clear your palate.

If you’re like me, you have a lot of computer systems floating around and the one thing they all have in common is that they could use some more drive space.  So, again, if you’re like me, that means you end up buying all kinds of storage space, in one form or another, to meet that need.  Now, you can do it as economically as possible thanks to Gigs4Less.  No matter what kind of storage you need, from compact flash to hard drives, they list everything they can find on the web and sort it by price, price per megabyte, and any other way you can think of sorting it.
So stop wasting money and hit this site to find the biggest drive you can afford, for less!

And be safe out there trick or treating, okay, kids?

I spent two days trying to teach someone just part of this once.

Now, you may think my failure in this regard is due to me being a bad teacher.  Sadly, it was not.  Two other people, one of whom I had already taught about RAID, and more specifically, SCSI RAID configurations, couldn’t teach this to my failed student either.  Shockingly, when I was “encouraged to find other opportunities to excel”, outside that company, naturally, that student took over my job.  Oddly enough, a few years later, I heard the person who had made that organizational choice had also been encourage to find other opportunities to excel.  Funny how that works.

So, now, in part to make up for not being able to educate that person, and also to spare someone the same teaching fate I faced, here are two articles about RAID.
First, from ExtremeTech, RAID 101, Understanding Multiple Drive Storage.
And, secondly, from TechRepublic, Choose A RAID Level that works for you!

You can go to those articles and get lots of detail, but I’ll break it down for you in brief here.
Something that people tend to forget, for some reason, is that RAID stands for Redundant Array of Inexpensive Disks.  That’s not as true as it used to be, thanks to server pricing and how cheap SATA drives have become compared to SCSI drives.  Back in the day, we always used SCSI and I still do for server systems, mostly, because it tends to be faster and more reliable than anything else.  That’s not as true as it used to be thanks to improvements in SATA, but if you still want to do a BIG array of disks, SCSI is pretty much the only real option.
There are a bunch of RAID “levels”, but, realistically, you’re mostly going to deal with three or four: RAID 0, RAID 1, RAID 5 and, maybe, RAID 10.

RAID 0 is generally referred to as “disk striping”.
In a nutshell, what this configuration does is stripe data across multiple drives.  Generally, this is done to make more available disk space and improve performance.  The down-side is that there is no redundancy.  In other words, with RAID 0, you can take several disks and make them perform like one larger, faster drive, but if one disk crashes, they all do.

RAID 1 is generally referred to as “disk mirroring.”
And, that’s essentially what it is, a system which saves everything to a duplicate drive or drives.  Most often in server configurations, you’ll find the operating system on two drives that are mirrored.  That means that if one drive goes bad, the admin can reconfigure the other drive to take over running the server.  In theory, this works pretty well.  In practice, it takes a little finagling sometimes to get that mirror drive reconfigured as the primary.  The other thing to remember is that the second drive is essentially lost storage.  In other words, if you put two 1 terabyte drives in a RAID 1 array, you only have 1 terabyte of available storage when the system is running.
This is pretty much bare-bones, bottom-of-the-barrel redundancy.

RAID 5 is what most people think of when you talk about RAID arrays.
In RAID 5, data bits and “pairity” bits are striped across three or more drives.  Basically, data is broken up and written to multiple drives and then another, sort of “record-keeping” bit of data is written, too, so that the RAID 5 system knows where all the pieces of the data are.  Now, that’s a bit of an oversimplification, but, what it means is that if one of the drives in a RAID 5 array fails, the array keeps running and no data is lost.  Also, when a replacement drive is put into place, the RAID 5 array automatically rebuilds the missing drive on the replacement!  This, my friends, is like system administration magic!  Somehow, with a lot of really big math, that I frankly don’t understand, they can tell what the missing bit is based on the stuff they do have and fill it in.  This is the best invention since sliced bread!
Also, an option on many RAID 5 systems is something called the “hot spare”.  The hot spare is a drive that is part of the array but not active, until one of the other drives fails.  Then, the hot spare becomes active and will automatically start to rebuild the missing data on that new drive.  That means that the system admin and order a new replacement drive at their leisure and actually schedule down-time to replace it.  What a concept!  Not always doing things at the last minute or under fire, but planning ahead and taking your time.  It’s unheard of!
Finally, the best option available on many RAID arrays is the “hot swapable” drive.  In that case, you don’t need to schedule downtime at all, but only need to pull the damaged drive out of the array and pop the replacement right in.  All without even shutting the production system down for even a minute!  Again, this is like magic!

The last “common” RAID level is RAID 10.
Basically, this is a combination of RAID 1 and RAID 0.  In other words, it’s a set of mirrored arrays.  This setup requires at least four drives and is fairly pricey.  It’s mainly used for redundancy and speed and, realistically, is almost only used for database servers.  In fact, I can’t think of any other instance that I’ve heard of this being used, outside of database servers.

There are other levels, too, of course, but you can hit the articles for more info about them.  They’re pretty uncommon outside of really high-end or experimental configurations of one kind or another.
Oh, one last thing…  RAID can be implemented either via hardware or software.  In general, software RAID, such as you might find in Linux, is cheaper, but is slower and more prone to having issues if something goes wrong.  Hardware RAID is faster, a little more expensive, but a far more robust solution.

So, there you have it, RAID in a nutshell.
And, yes, for those of you who have noticed, articles like this are me turning this blog back toward its roots as a technical blog.  I hope to have more basic info like this as well as some new projects over the next 18 months or so.  Certainly, more than there have been in the past two or three years.
I hope you’ll keep coming back for more!