I want to take just a moment to talk about RAID and backups.<\/p>\n
First off, what is RAID? \u00a0RAID stands for\u00a0Redundant Array of Independent\/Inexpensive Disks, and was\u00a0conceived to create larger storage systems out of smaller and cheaper disks (versus buying single expensive disks). \u00a0In addition to just expanding space, most RAID levels also provide for the failure of one or more disks without losing data (disks fail often). \u00a0In more recent times RAID can be quite complex and used for a variety of reasons including the creation of large storage systems, increased performance, and increased reliability.<\/p>\n
To state it simply, RAID is just a fancy way to get a lot of storage on a given computer system.<\/p>\n
RAID is a great technology, and has been around over two decades, but it is not the panacea of data protection like many may have thought. \u00a0The problem with RAID is that things can certainly still go wrong. \u00a0RAID systems can be complex and it creates more\u00a0opportunity\u00a0for human error while maintaining the system, and there is a decent chance of firmware (software) issues to crop up as well.<\/p>\n
Thus, RAID is not <\/strong>good for backups. \u00a0RAID systems fail. \u00a0Two drives can fail, operators can make mistakes when replacing bad drives, and of course power surges, water\u00a0damage, and fire will\u00a0destroy\u00a0all disks in a RAID system. \u00a0Also, RAID does not protect you from users removing important files, nor from applications corrupting important documents and rendering them useless.<\/p>\n If a RAID system stores any important business data, make sure it is backed up. \u00a0Furthermore, make sure your applications are backed up as well, which can mean the difference between recovery in hours versus weeks.<\/p>\n I once visited a business whose 10 employee company all ran on one large server, with a large RAID array (array just means a collection of disks). \u00a0The array was showing signs of failing, and they called me in with some haste to resolve the errors. \u00a0It turned out one drive had failed, but the array refused to rebuild onto a replaced drive. \u00a0Luckily this business had\u00a0diligently\u00a0backed up their\u00a0critical\u00a0business data on a daily basis, but they neglected to backup the operating system and applications they needed to run their business.<\/p>\n We tried several options to backup the applications and operating system, and worked with the RAID vendor to get the array rebuilt. \u00a0Unfortunately we were never able to access the application data, and were forced to rebuild the server from scratch. \u00a0The rebuild took two 60 hour weeks and a team of IT consultants to finish, costing the company tens of thousands of dollars not including the days of productivity lost by employees. \u00a0A data protection system to avoid that incident would have cost just a few\u00a0hundred\u00a0dollars a month.<\/p>\n Another small business I spoke with, a photography studio, had their entire body of work on one RAID system. \u00a0One day a disk failed and they mistakenly replaced the wrong drive, corrupting the system and prevented them from\u00a0accessing their entire body of work. \u00a0Luckily, they were able to have the system painstakingly put back together by a data recovery expert for a fee likely equal to one\u00a0quarter of their yearly revenue and a week without access to the data — ouch. \u00a0The cost to protect that data? \u00a0About $350\/mo.<\/p>\n If you are interested in the nitty-gritty, check out the Wikipedia article on RAID<\/a>.<\/p>\n If you are using RAID and are not sure it is adequately protected, give us a call.<\/p>\n","protected":false},"excerpt":{"rendered":" I want to take just a moment to talk about RAID and backups. First off, what is RAID? \u00a0RAID stands for\u00a0Redundant Array of Independent\/Inexpensive Disks, and was\u00a0conceived to create larger storage systems out of smaller and cheaper disks (versus buying … Continue reading