{"id":33663,"date":"2020-07-05T14:43:40","date_gmt":"2020-07-05T12:43:40","guid":{"rendered":"http:\/\/blog.open-e.com\/?p=33663"},"modified":"2025-04-04T06:42:08","modified_gmt":"2025-04-04T06:42:08","slug":"why-raid-is-not-a-backup","status":"publish","type":"post","link":"https:\/\/www.open-e.com\/blog\/why-raid-is-not-a-backup\/","title":{"rendered":"Why RAID is Not a Backup"},"content":{"rendered":"

\t\t\t\tLast update: July 05, 2021<\/strong><\/p>\n

Today I would like to discuss the topic of RAID<\/a> \u2013 more specifically backup issues. In the blog post title, I proposed a daring thesis which I would like to develop and, as far as I\u2019m able, to prove or defend it. At the very beginning, a few definitions and terms related to RAID have to be introduced, so the readers who aren\u2019t familiar with RAID won\u2019t feel confused.<\/p>\n

What is RAID?<\/h2>\n

RAID technology extends the capabilities of drives and unifies individual disks in a group (or groups). Such groups are called arrays. Thanks to the combination of disks into arrays, extra disk capabilities become available. For example, fault-tolerant disk (or disks) arrays, an increased read\/write array transfer (or both) in comparison to the transfer on a single disk, or the possibility of expanding arrays to additional drives.<\/p>\n

But let\u2019s take it easy, not all at once. There are different types of arrays and their features depend on what types of arrays were used. In this article, I would like to focus on just one of the properties of RAID, mainly redundancy or the array’s resistance to hard disk failures. Now let the fun with backup begin.<\/p>\n

 <\/p>\n

Proof No. 1 \u2013 All copies are not created equal<\/h3>\n
\"RAID_1.svg\"<\/div>\n

Imagine dear reader, that you are an administrator of a data server where drives work in RAID 1. To make matters clear, this is a type of array known as \u2018mirror-type RAID\u2019, as it saves the same data on all disks found in the array. Saving SOMETHING on your array means that you will find SOMETHING on each of the RAID array disks.<\/p>\n

Suppose that one beautiful day you find a corrupted file on your data server and, to add a dash of drama, assume that this file is a document that belongs to your boss. According to how RAID 1 works, the corrupted file was instantly saved on all disk arrays and there is no possibility to retrieve it. All in all, despite the fact that the copies of data are located on all disks, in case of file corruption – all copies on all disks are damaged. That is the first difference between a copy on a RAID array and a backup copy. When it comes to backup, the moment a file becomes corrupt its copy will still be safe on a backup server. Thus, all copies are not created equal.<\/p>\n

 <\/p>\n

Proof No. 2 \u2013 Attention, virus!<\/h3>\n

Let\u2019s go back in time about two paragraphs, to the moment when your boss\u2019s file hasn\u2019t been damaged (same file server and array). Now, your boss downloaded something from torrents. It was supposed to be a free program for VAT taxes, but it turned out that it was a virus that deleted all the data. Just like in the first example (see proof No. \u00a01), your boss\u2019 data have been deleted from all disk arrays. A backup system should protect the data against deletion, giving a chance for data recovery at the same time.<\/p>\n

 <\/p>\n

Proof No. 3 \u2013 File system bites the dust<\/h3>\n

File systems also tend to fail. In such case, if a file system in a RAID array is damaged, the damage will be replicated X times, where X is the number of disks in the array. But there\u2019s also the other side of the coin. If you manage to fix the file system, it will also be repaired on all of the disk array components. However, if some data will be lost during a file system repair and the data protection with a backup system was not done, then you can write those data off.<\/p>\n

 <\/p>\n

Proof No. 4 \u2013 Fire!<\/h3>\n

I would like to devote my last proof to the topic which is substantially unpleasant \u2013 a complete damage of the data server. Fire in the server room or any other factor that could destroy the whole server means data loss. Yes, yes, I understand that in the same burning server room there can be (but doesn\u2019t have to) a backup server. However, there are some techniques that deal with the problem, even when there\u2019s fire – a fireproof cabinet for storing magnetic tapes with data or data storage outside the company (called Off-site Backup<\/a>) or even outside the building with the data server.<\/p>\n

 <\/p>\n

Now it will only get better<\/b><\/h2>\n

I have outlined four arguments that show why RAID is not the same as backup. I have focused on the weak points of RAID as a system of protection when it comes to data loss. Luckily, there are also many positive aspects of using RAID. Unfortunately, apart from those that were mentioned in the introduction, I\u2019m not going to discuss them as this is a very broad topic and it\u2019s not directly connected with the topic of my post.<\/p>\n

If you\u2019re interested, try finding some material on the topic of RAID on the Internet. The ‘data protection’\u00a0 feature of certain types of RAID can protect the data on disks in case of a disk or disks failure, depending on which RAID type is used and the number of disks in the array. And in my view, that\u2019s a strong point of some types of RAID – fault tolerance.<\/p>\n

 <\/p>\n

RAID<\/b> together with backup<\/b><\/h2>\n

RAID technology is often used on servers recording data backups. It is an environment usually supervised by a backup server application that uses RAID arrays as a storage unit. Personally, I consider this as a good practice, provided that a suitable RAID was chosen.<\/p>\n

\n

RAID Calculator<\/h3>\n

We know that your data is priceless \u2013 calculate how many disks you need to get it safe with our Open-E JovianDSS Storage and RAID Calculator!<\/p>\n

\"RAID<\/a><\/p>\n

\n

 \t\t<\/p>\n","protected":false},"excerpt":{"rendered":"

Last update: July 05, 2021 Today I would like to discuss the topic of RAID \u2013 more specifically backup issues. In the blog post title, I proposed a daring thesis …<\/p>\n","protected":false},"author":4,"featured_media":45553,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[14,27,765,28],"tags":[86,523],"class_list":["post-33663","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-storage-technology","category-open-e-joviandss","category-open-e-legacy-products","category-raid","tag-backup","tag-raid"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/posts\/33663","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/comments?post=33663"}],"version-history":[{"count":1,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/posts\/33663\/revisions"}],"predecessor-version":[{"id":55162,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/posts\/33663\/revisions\/55162"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/media\/45553"}],"wp:attachment":[{"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/media?parent=33663"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/categories?post=33663"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.open-e.com\/blog\/wp-json\/wp\/v2\/tags?post=33663"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}