# RAID 1

> Source: Courseiva IT Certification Glossary — https://courseiva.com/glossary/raid-1

## Quick definition

RAID 1 makes a mirror of everything you save. When you write a file, it is written identically to two drives. If one drive breaks, the other still has your data. It gives you protection against hardware failure without slowing down reading.

## Simple meaning

Think of RAID 1 like having two identical notebooks. When you take notes in one notebook, you instantly copy every word into the second notebook. If you lose the first notebook, the second one has exactly the same information. You never have to start over. In the computer world, RAID 1 works the same way with hard drives. When you save a file, the computer writes it to two separate drives at the same time. The drives are mirrors of each other. If one drive stops working, the other drive still has the file. You can keep working without missing anything. 

 The main benefit of RAID 1 is safety. You do not get extra speed for writing because both drives must finish writing before the system says the file is saved. However, reading can be faster because the computer can read from either drive at the same time. The downside is that you lose storage space. If you have two 500 GB drives in a RAID 1 array, you only have 500 GB of usable space, not 1000 GB. The other 500 GB is used for the mirror copy. 

 RAID 1 is a common choice for people who want to protect important files, like a small business keeping financial records or a photographer storing client photos. It does not protect against viruses, accidental deletion, or theft. It only protects against a single drive failing. For that reason, RAID 1 is often combined with regular backups.

## Technical definition

RAID 1 is a standardized data redundancy technique defined under the original RAID levels proposed by Patterson, Gibson, and Katz at the University of California, Berkeley in 1987. It is formally known as disk mirroring and may optionally include duplexing when separate disk controllers are used for each drive. The fundamental operation of RAID 1 involves writing identical data blocks to two or more physical disks simultaneously. The array controller, which can be implemented as a hardware RAID controller or as software RAID (e.g., Windows Storage Spaces, mdadm on Linux), presents the set of mirrored drives as a single logical volume to the operating system. 

 When a write input/output request is issued, the controller writes the data to every drive in the mirror set. The write operation is not considered complete until all drives have acknowledged successful writing. This ensures write atomicity, meaning either all drives have the data or none do. This guarantees consistency across the mirrored copies. Within a RAID 1 array, the total usable capacity is one drive’s capacity, regardless of how many drives are in the set. For example, a RAID 1 array with three 2 TB drives provides only 2 TB of usable storage, with the remaining 4 TB dedicated to mirroring. 

 Read performance in RAID 1 can improve over a single drive because the controller can service read requests from any member drive. In a multi-drive RAID 1 array, the controller can distribute read loads across all drives, effectively increasing read throughput. This is sometimes referred to as read load balancing. RAID 1 does not use parity calculations or striping, which means there is no computational overhead for parity generation. The simplicity of the mirroring operation also means that rebuild times after a drive failure are generally fast, as the controller only needs to copy data from the surviving drive to the replacement drive. 

 RAID 1 is supported by nearly all operating systems and hardware RAID controllers. In modern enterprise environments, RAID 1 is often deployed for boot drives, critical application databases, and virtual machine hypervisors where high availability and low latency are required. The standard does not impose a minimum or maximum number of drives, though practical implementations typically use two drives. Some enterprise arrays support up to three or four mirrored copies (RAID 1+0 or nested levels) for even higher fault tolerance. The primary trade-off is cost per gigabyte, because the storage efficiency is only 50% for a two-drive set.

## Real-life example

Imagine you are a chef who writes every recipe in a paper notebook. One day, a spill ruins the notebook. All your recipes are gone. To prevent this, you start keeping two identical notebooks. Every time you write a recipe, you copy it into both notebooks. If one gets wet, you still have the other. You can still cook without panic. 

 In the IT world, RAID 1 is exactly that. The two notebooks are your two hard drives. The chef’s actions are your computer’s writing operations. Every time you save a file, the computer writes it to both drives. The benefit is that if one drive physically fails, your data is safe on the other drive. You can replace the broken drive and the system will copy all the data from the good drive to the new one, rebuilding the mirror. 

 The downside is that you are using two notebooks but only getting the storage space of one. You are paying for an extra notebook only for security. In a business, this is like having a backup assistant who copies every document immediately. It costs more in hardware, but the peace of mind is worth it for critical data. 

 Another analogy is a team of two editors who each keep a copy of the manuscript. If one editor’s laptop crashes, the other has the full manuscript. They can continue working. In the digital world, this is why RAID 1 is often used for email servers or database logs where losing even a moment of data is unacceptable.

## Why it matters

For IT professionals, RAID 1 is a fundamental building block of data resilience. In many small to medium businesses, budgets are tight, and the cost of a dedicated backup server might be prohibitive. RAID 1 offers a hardware-level safety net that ensures a single drive failure does not bring down a critical service. For example, a company’s file server running RAID 1 can continue operating after a drive fails, allowing the IT team to schedule a replacement drive installation during business hours without an emergency shutdown. This uptime directly reduces productivity loss and potential revenue loss. 

 From a career standpoint, understanding RAID levels is a baseline requirement for roles such as systems administrator, storage engineer, and IT support specialist. You will encounter RAID 1 in server setups, NAS devices, and even some high-end desktop workstations. Knowing how to configure, monitor, and recover a RAID 1 array is a practical skill that interviewers often test. 

 RAID 1 also serves as a stepping stone to more complex nested RAID levels like RAID 10, which combines mirroring with striping. Without a solid grasp of RAID 1, you will struggle to understand how RAID 10 provides both performance and redundancy. In day-to-day operations, troubleshooting a failed drive in a RAID 1 array is straightforward: the system alerts you, you replace the disk, and the array rebuilds. This simplicity is why many IT professionals choose RAID 1 for mission-critical data that does not require high capacity. 

 However, it is important to remember that RAID 1 is not a backup. If a file is corrupted or deleted accidentally, the corruption is instantly mirrored to the other drive. You must still maintain separate backups to recover from logical errors. This distinction is a common interview question and exam topic.

## Why it matters in exams

RAID 1 appears prominently in several major IT certification exams. In CompTIA A+ (Core 2), RAID levels are covered under the domain of storage configuration. Candidates may be asked to identify RAID 1 from a description of mirroring. In CompTIA Server+, RAID 1 is a core objective under storage configuration and troubleshooting. The exam expects you to know the minimum number of drives required (2), the usable capacity (one drive’s size), and the fault tolerance characteristics (tolerates one drive failure in a two-drive array). 

 For CompTIA Network+, RAID 1 is less directly tested, but it appears in the context of high availability for networked storage systems. The Network+ exam may present a scenario where a server uses RAID 1 for its OS drive to maintain network services like DHCP or DNS. Understanding how RAID 1 contributes to uptime helps answer questions about fault tolerance. 

 In the Microsoft Azure and AWS certification paths, RAID 1 is discussed in the context of cloud-based virtual machine storage. For instance, the Azure AZ-900 exam might ask about strategies for protecting data, where RAID 1 is an option for on-premises systems, though cloud services typically offer built-in redundancy. Similarly, the AWS Cloud Practitioner exam may reference RAID 1 as a configuration for EC2 instance store volumes. 

 In Cisco CCNA, RAID 1 is not a primary topic, but it can appear in questions about server hardware within network infrastructure. The exam might ask you to identify the best RAID level for a specific requirement, such as redundancy with minimal complexity. RAID 1 is often the correct answer for scenarios demanding high fault tolerance with minimal performance hit. 

 Exam questions typically test the following: number of drives, usable capacity vs. total capacity, read/write performance characteristics, and fault tolerance limits. Common question formats include multiple-choice “select the best RAID level for this situation” and true/false statements like “RAID 1 provides striping.” You must be precise: RAID 1 is defined by mirroring, not striping. A common trick question states that RAID 1 requires a minimum of three drives, which is false. Always remember the minimum is two.

## How it appears in exam questions

In IT certification exams, RAID 1 questions generally fall into three categories: definition-based, scenario-based, and troubleshooting. Definition-based questions ask straightforwardly, “Which RAID level uses disk mirroring?” The answer choices include RAID 0, RAID 1, RAID 5, and RAID 10. If you know that mirroring is the key characteristic, you choose RAID 1. Another common variant is, “How many drives are required for a RAID 1 array?” The correct answer is two, though exams sometimes include distractor answers like one or three. 

 Scenario-based questions present a real-world situation. For example, “A small business wants to protect its accounting database against a single drive failure. They do not need maximum storage capacity and want to keep configuration simple. Which RAID level should they choose?” The answer is RAID 1 because it provides mirroring with only two drives, uses the capacity of one drive, and is simple to set up. Another scenario might describe a user who needs high read performance for a database but is less concerned about storage efficiency. In that case, RAID 1 would be a good fit because it can double read speed while providing redundancy. 

 Troubleshooting questions describe a RAID 1 array that has experienced a drive failure. The question might ask, “A server with a two-disk RAID 1 array stops responding. The administrator notices one disk has a red status light. What should the administrator do first?” The correct answer is to replace the failed drive and allow the array to rebuild automatically. A distractor answer might suggest reformatting the good drive or switching to RAID 0. Another troubleshooting question could involve the operating system not recognizing the full capacity available. The incorrect assumption might be that both drives’ capacities are usable, while the correct understanding is that RAID 1 uses only one drive’s capacity. 

 A more advanced question might compare RAID 1 with RAID 5. For example, “Which RAID level offers better write performance under heavy load?” RAID 1 generally has better write performance than RAID 5 because it does not compute parity. However, the question could be tricky by stating that RAID 1 writes to two drives, implying slower writes, but the correct answer is that RAID 5 is slower due to parity overhead. You must understand the trade-offs clearly to answer such comparative questions. 

 Finally, questions about disk failure impact appear regularly. “In a RAID 1 array with three drives, how many drive failures can be tolerated?” The answer is two, because with three drives the array can survive failures as long as at least one drive remains functioning. This contrasts with a two-drive array, which only tolerates one failure.

## Example scenario

You are the IT support technician for a small law firm. The firm stores all client case files on a single external hard drive connected to a Windows desktop. The office manager calls panicking because the hard drive made a clicking sound and is no longer accessible. They need to resume work immediately. After inspecting the drive, you determine it has failed mechanically. 

 You explain that RAID 1 would have prevented this emergency. You recommend that the firm purchase a two-bay external RAID enclosure and two identical 2 TB hard drives. You configure the drives in RAID 1 mode. Now, when a paralegal saves a contract to the D: drive, the data is written to both hard drives simultaneously. The system shows only one 2 TB drive to the users, which is the usable capacity. 

 A few months later, one of the drives fails. The RAID controller emits a beep and the status light on the failed drive turns red. The office manager sees a notification on the screen that the RAID array is degraded. They call you. Because the array is still functioning on the remaining good drive, the paralegals can continue working without interruption. You order a replacement drive, install it, and the RAID controller automatically copies all data from the good drive to the new drive. The rebuild takes about four hours, but the system remains online throughout the process. After the rebuild, the status light returns to green. The firm experienced zero downtime and zero data loss. 

 This scenario illustrates the core value of RAID 1: immediate redundancy. Without RAID 1, the first drive failure would have resulted in days of lost productivity and potentially lost case files. With RAID 1, the failure was a minor inconvenience. The scenario also highlights that RAID 1 is not a substitute for off-site backup. If a fire destroyed the office, both drives would be lost. Therefore, you also set up a cloud backup service that runs nightly. The combination of RAID 1 for uptime and cloud backup for disaster recovery provides comprehensive protection.

## Common mistakes

- **Mistake:** Thinking RAID 1 doubles storage capacity.
  - Why it is wrong: RAID 1 mirrors data, so the total usable capacity is equal to the size of one drive, not the sum of both. Using two 1 TB drives gives only 1 TB of usable space.
  - Fix: Understand that mirroring creates an exact copy, so you lose half the raw capacity to redundancy.
- **Mistake:** Believing RAID 1 protects against file corruption or accidental deletion.
  - Why it is wrong: If a file is corrupted by a virus or accidentally deleted, the change is instantly mirrored to the other drive. Both copies will have the same problem.
  - Fix: Use regular backups (e.g., external drives or cloud backups) for protection against logical errors.
- **Mistake:** Assuming RAID 1 requires three drives minimum.
  - Why it is wrong: RAID 1 requires a minimum of two drives. Three or more drives can be used, but two is the standard minimum.
  - Fix: Memorize the minimum drive requirements: RAID 0 needs 2, RAID 1 needs 2, RAID 5 needs 3, RAID 10 needs 4.
- **Mistake:** Confusing RAID 1 with RAID 0.
  - Why it is wrong: RAID 1 mirrors data for redundancy, while RAID 0 stripes data across drives for performance but offers no redundancy. They are opposites in terms of fault tolerance.
  - Fix: Remember: RAID 1 = mirror = safety, RAID 0 = stripe = speed, no safety.
- **Mistake:** Thinking RAID 1 slows down all operations.
  - Why it is wrong: Write operations may be slightly slower because data must be written to multiple drives, but read operations can be faster because the controller can read from either drive.
  - Fix: Consider RAID 1 as balanced: writes are equal to or slightly slower than a single drive, reads can be up to two times faster.
- **Mistake:** Believing RAID 1 is only for large enterprise servers.
  - Why it is wrong: RAID 1 is available in many consumer NAS devices, external drive enclosures, and even some desktop motherboards. It is accessible for home users and small businesses.
  - Fix: Check if your hardware supports RAID 1. Many inexpensive two-bay NAS systems have RAID 1 capability.

## Exam trap

{"trap":"The question asks: 'Which RAID level provides both increased read performance and fault tolerance without parity overhead?' Learners often choose RAID 5 or RAID 6 because they associate parity with protection. The correct answer is RAID 1.","why_learners_choose_it":"Learners see 'fault tolerance' and 'performance' and automatically think of parity RAID levels like RAID 5. They forget that RAID 1 also provides fault tolerance and can improve read performance through load balancing across mirrored drives.","how_to_avoid_it":"Read the wording carefully. The phrase 'without parity overhead' eliminates RAID 5 and RAID 6. Only RAID 1 and RAID 10 meet that criteria. Since the question says 'without parity overhead' and often implies a simple setup, RAID 1 is the cleanest answer. Also note that RAID 1 can increase read speed because data can be read from either drive simultaneously."}

## Commonly confused with

- **RAID 1 vs RAID 0:** RAID 0 splits data across drives for speed but provides zero redundancy. If one drive fails, all data is lost. RAID 1 mirrors data for full redundancy. Use RAID 1 when data safety is priority, RAID 0 for performance-only tasks like video editing scratch disks. (Example: A gamer might use RAID 0 to load games faster, while an accountant would use RAID 1 to protect tax records.)
- **RAID 1 vs RAID 5:** RAID 5 uses striping with distributed parity and requires at least three drives. It offers better storage efficiency than RAID 1 (e.g., three 1 TB drives give 2 TB usable). However, RAID 5 has write performance penalties due to parity calculation. RAID 1 is simpler, generally faster for writes, and tolerates the same number of failures as a two-drive RAID 5 set (one drive). (Example: A file server with many small files might use RAID 1, while a large video archive might use RAID 5 to get more usable capacity.)
- **RAID 1 vs RAID 10:** RAID 10 (also called RAID 1+0) combines mirroring and striping. It requires at least four drives. It provides both performance and redundancy, but costs more in hardware. RAID 1 is simpler and uses fewer drives. RAID 10 offers better read and write performance because it stripes across mirrored pairs. (Example: A high-demand database server might use RAID 10 for speed and safety, while a small office email server would use RAID 1 to save costs.)
- **RAID 1 vs JBOD:** JBOD (Just a Bunch Of Disks) simply combines drives into one volume without any redundancy or performance benefit. RAID 1 provides fault tolerance, JBOD gives none. JBOD is not a RAID level. (Example: JBOD is used when you need a large volume from mismatched drives, while RAID 1 is used when you specifically need data protection.)

## Step-by-step breakdown

1. **Install physical drives** — You install two or more identical hard drives into your system or NAS enclosure. For best performance, use drives of the same model and capacity. The drives are connected to the RAID controller, which can be a dedicated card or integrated into the motherboard.
2. **Create the RAID 1 array** — Access the RAID configuration utility during system boot (e.g., pressing Ctrl+I for Intel RST). Select the option to create a new RAID volume. Choose RAID 1 as the RAID level and select the two drives you want to mirror. The controller will then initialize the array, which may take some time.
3. **Data mirroring begins** — When the array is active, any data written to the logical volume is written simultaneously to all member drives. The controller ensures that the data on each drive is identical. This process happens in real-time with every read and write operation.
4. **Monitor array health** — The RAID controller continuously monitors both drives. If a drive fails, the controller changes the status of the array to 'degraded' and alerts the administrator. The system continues running on the remaining drive(s) without interruption.
5. **Replace failed drive** — When a drive fails, you physically remove it and insert a new drive of equal or larger capacity. The system detects the new drive. You must add it to the RAID 1 array as a spare or as a replacement member.
6. **Rebuild the array** — The RAID controller automatically starts copying all data from the surviving drive to the new drive. This is called a rebuild. The system remains online during the rebuild, though performance may be slightly reduced. When the rebuild finishes, the array returns to the 'normal' or 'optimal' state.

## Practical mini-lesson

RAID 1 is a foundational skill for IT professionals, but its practical implementation involves more than just selecting 'mirror' in a menu. In a typical server deployment, you will work with either a hardware RAID controller or software RAID. With hardware RAID, the controller has its own processor and cache, handling all mirroring operations independently of the CPU. This offloads the work, providing better performance, especially during rebuilds. You need to know how to enter the RAID BIOS (often by pressing Ctrl+R or F10 during POST) to configure arrays. You must also understand how to replace a failed drive without rebooting the system if the controller supports hot-swap drives. 

 In software RAID, the operating system handles mirroring. On Windows, you can use Storage Spaces to create a mirrored space. On Linux, the mdadm utility is the standard. Software RAID is cheaper but consumes CPU cycles for every write operation. In virtualized environments such as VMware vSphere, RAID 1 is often configured at the hardware level on the ESXi host, then presented as a datastore. You must ensure that the RAID controller is supported by the hypervisor. A common mistake is forgetting to check the RAID controller’s compatibility list before installation, which can lead to unrecognized drives. 

 Performance considerations are critical. If you use a hardware RAID controller with a battery-backed write cache, you can enable write-back caching, which greatly improves write performance because the controller acknowledges writes before data is fully written to the disks. However, if the battery fails, you risk data corruption. In software RAID, writes go directly to the drives, which can be slower. Also, rebuilding a RAID 1 array with large capacity drives (e.g., 4 TB or more) can take hours or even days. During the rebuild, the array is vulnerable to another drive failure, so you should prioritize replacing drives quickly. 

 Monitoring is essential. RAID controllers often include management software (e.g., Dell OpenManage or HP Smart Storage Administrator) that sends alerts when a drive fails. You must configure email or SNMP notifications. In a data center, a failed drive might not cause downtime, but it raises the risk of data loss if the second drive fails during the rebuild. Therefore, best practice is to keep spare drives on hand and monitor the array status regularly. 

 Another practical aspect is choosing drive types. For RAID 1, using SSDs can drastically improve performance, especially for read-heavy workloads. SSDs also rebuild faster because they do not have mechanical delays. However, SSDs wear out with writes. For a write-intensive database, you should evaluate the SSD’s endurance rating. In mixed-use scenarios, many IT professionals use RAID 1 with two SSDs for the operating system and a separate RAID 5 or RAID 10 array for bulk data.

## Memory tip

RAID 1 = One Mirror = One Duplicate. Remember: two drives, one copy of data is safe.

## FAQ

**Can I use two different sized drives in RAID 1?**

Technically yes, but the array will only use the capacity of the smaller drive. For example, a 1 TB drive and a 2 TB drive together will give you only 1 TB of usable space. It is best to use identical drives.

**Does RAID 1 protect against data corruption from a virus?**

No. If a virus corrupts a file, the corruption is mirrored to the other drive. RAID 1 only protects against physical drive failure, not software-based threats.

**Can I convert a RAID 1 array to a different RAID level after it is set up?**

Some RAID controllers support online migration, but the process is risky and often requires a backup. It is generally safer to back up the data, delete the array, create a new one, and restore the data.

**How many drive failures can RAID 1 survive?**

In a two-drive RAID 1 array, at most one drive can fail. In a three-drive array, up to two drives can fail. As long as at least one drive remains operational, the array can function.

**Is RAID 1 faster than a single drive?**

Read operations can be faster because the controller can read from either drive simultaneously. Write operations are roughly the same speed or slightly slower because data must be written to all drives.

**Do I need special hardware for RAID 1?**

Not necessarily. Many motherboards have built-in RAID controllers. You can also use software RAID built into operating systems like Windows (Storage Spaces) or Linux (mdadm).

**What happens if I remove one drive from a RAID 1 array?**

The array will show as degraded or failed, and you may lose access to the logical volume depending on the controller. It is best to never remove a drive without properly shutting down the system or following the controller’s disconnection procedure.

## Summary

RAID 1 (mirroring) is one of the simplest and most reliable ways to protect data against a single drive failure. It works by writing identical data to two or more drives, so if one drive fails, the system continues operating on the remaining drive(s). The key trade-off is storage efficiency: you lose at least half of the raw capacity to redundancy. However, the benefit of immediate availability and simple design makes RAID 1 a go-to solution for boot drives, critical servers, and any scenario where downtime or data loss is unacceptable. 

 For IT certification candidates, RAID 1 is a frequent exam topic across CompTIA A+, Server+, Network+, and various vendor-specific exams. You must remember the minimum number of drives (2), the usable capacity (one drive size), and the fact that it provides fault tolerance without parity overhead. Common exam traps include confusing mirroring with striping, thinking RAID 1 protects against logical errors, and misunderstanding the capacity arithmetic. 

 In the real world, RAID 1 is a practical choice for small businesses and home users who need a simple, cost-effective redundancy solution. However, it is not a replacement for a comprehensive backup strategy. In your career, you will use RAID 1 in combination with backups, drive monitoring, and hot spares to build truly resilient storage systems. Mastering RAID 1 gives you a solid foundation for understanding more advanced RAID levels and nested configurations like RAID 10.

---

Practice questions and the full interactive page: https://courseiva.com/glossary/raid-1