Storage Technologies and Data Protection
Compare HDD, SSD, and NVMe behaviour, plan RAID levels, and protect data during migrations and failures.
- Certification
- CompTIA A+
- Recommended study time
- 5h 35m
- Status
- Not started
Recommended study time
About 5h 35m in total, measured from the material on this page. At your session length of 45 minutes that is 8 sittings.
- Read the lesson21 min
About 2,740 words at a careful technical reading pace.
- Second pass with notes13 min
Re-read the harder parts and write your own notes.
- Recall from memory12 min
2 written recall questions.
- Practice decision12 min
One applied decision with feedback.
- Teach it back20 min
Write the topic in your own words.
- Real-world scenario15 min
Read the situation and justify your decision in writing.
- Hands-on practice2h 40m
Labs, commands and configuration until you can do it unaided.
- Spaced review1h 20m
4 short review sessions spread over the following weeks.
Learning objectives
- Compare interface and media types by performance, endurance, and failure behaviour.
- Choose an appropriate RAID level for a stated availability and capacity requirement.
- Plan a migration that protects data before any destructive step.
Start here
About 8 minutes of reading, in 10 short parts.
Storage is where data survives after the power is switched off, and the choice of storage technology affects speed, reliability, and cost in ways that matter to real customers. This lesson compares hard disks, SSDs, and NVMe drives, and explains how RAID and backups protect data against failure.
Where you meet it: You use this when specifying a new machine's drive, planning a server's fault tolerance, or responding to a failed or degraded disk in a live system.
The lesson, part by part
Open one part at a time. Each part stands on its own, so you can stop and come back.
Think of a hard disk drive as a tiny record player: a spinning platter and a needle-like arm that has to physically move to the right spot before it can read anything. An SSD, by contrast, is more like flipping through a well-organised filing cabinet with no moving parts at all, so it can jump straight to any piece of information almost instantly.
RAID (Redundant Array of Independent Disks) is like keeping duplicate copies of important paperwork spread across multiple filing cabinets, so that if one cabinet is destroyed, the information still exists elsewhere and can be reconstructed. A backup, on the other hand, is a completely separate copy stored somewhere else entirely, protecting against events, like theft or fire, that could destroy all the cabinets in the same room at once.
Key ideas
If you remember nothing else from this topic, remember these.
- HDDs store data magnetically on spinning platters, while SSDs store data electrically in NAND flash cells with no moving parts.
- NVMe drives communicate over the PCIe bus and vastly outperform SATA SSDs, which are limited by the SATA III interface's 6 Gbps ceiling.
- RAID levels trade capacity, performance, and redundancy differently: RAID 0 stripes for speed with no redundancy, RAID 1 mirrors for redundancy, and RAID 5 stripes with parity for a balance of both.
- Optical media and legacy interfaces like eSATA still appear in real environments and must be recognized even though they are declining.
- Drive health should be monitored using SMART attributes, which can predict failure before data loss occurs.
- Choosing the correct interface, form factor, and RAID level depends on the workload, not simply on the fastest available option.
Selecting and configuring storage for a small office file server
A worked example, step by step.
A small business needs a file server that balances redundancy and performance on a limited budget, using four identical drives.
- 01Step 1Confirm the four drives are identical capacity SATA HDDs, since mismatched RAID members waste capacity.
- 02Step 2Decide against RAID 0 immediately since it offers zero redundancy and one drive failure loses all data.
- 03Step 3Evaluate RAID 5, which uses parity striping across all drives, tolerating a single drive failure while using only one drive's worth of capacity for parity.
- 04Step 4Enter the RAID controller's configuration utility during boot and create a RAID 5 array across the four drives.
- 05Step 5Initialize and format the resulting virtual disk in Windows Server using Disk Management, assigning NTFS as the file system.
- 06Step 6Configure SMART monitoring alerts through the RAID controller's management software so a failing drive is flagged proactively.
- 07Step 7Simulate a single drive failure in a test environment by pulling one drive and confirming the array remains accessible in degraded mode.
- 08Step 8Replace the failed drive and confirm the array rebuilds automatically, restoring full redundancy.
Outcome: The file server tolerates a single drive failure without data loss, and staff can continue working during a rebuild after a real drive replacement.
Storage Technology Reference
Worth keeping at hand while you work.
- HDD
- Magnetic spinning platters, mechanical, cheaper per GB
- SSD (SATA)
- Flash-based, limited to SATA III 6 Gbps
- NVMe SSD
- Flash-based over PCIe, far higher throughput than SATA
- RAID 0
- Striping, improves speed, zero redundancy
- RAID 1
- Mirroring, full redundancy, 50 percent capacity usable
- RAID 5
- Striping with parity, tolerates one drive failure
- RAID 10
- Mirrored pairs striped together, high performance and redundancy
- SMART
- Self-Monitoring Analysis and Reporting Technology for predictive drive health
- eSATA
- External SATA interface for external drive enclosures
- M.2 form factor
- Compact card-edge slot for SSDs, both SATA and NVMe variants exist
- Optical drive
- Reads/writes CD, DVD, or Blu-ray media
- IOPS
- Input/output operations per second, a key SSD performance metric
Common misunderstandings
What most beginners get wrong here.
RAID is a backup solution.
RAID provides redundancy or performance, not protection against accidental deletion, corruption, or ransomware; backups are still required.
All M.2 drives are NVMe and equally fast.
M.2 is just a form factor; some M.2 drives are SATA-based and much slower than NVMe drives in the same slot type.
RAID 5 can tolerate two simultaneous drive failures.
RAID 5 tolerates only one failure at a time; two lost drives destroy the array.
SSDs never fail and require no monitoring.
SSDs have finite write endurance and can fail; SMART monitoring still applies.
More RAID drives always means more usable capacity.
Parity or mirroring overhead reduces usable capacity depending on the RAID level chosen.
Exam traps
How the question writers try to catch you out.
- Expect a scenario asking which RAID level provides redundancy with the least capacity overhead among the options listed.
- Questions may test the difference between SATA SSD and NVMe SSD performance and interface, not just the word SSD.
- Watch for trick options claiming RAID replaces backups.
- A question may ask which RAID level offers no fault tolerance, expecting RAID 0.
- SMART-related questions test recognition of the term as predictive failure monitoring, not a repair tool.
Check yourself
Answer in your head first, then reveal. This is not scored.
What is the key difference between RAID 0 and RAID 1?
Why is NVMe faster than SATA SSD?
How many drive failures can RAID 5 tolerate at once?
What does SMART monitor?
Does RAID eliminate the need for backups?
Quick reference
A condensed summary of the lesson above, for revision.
What It Is
Storage combines media (magnetic platters, NAND flash), an interface (SATA, SAS, NVMe over PCIe), and an organisation layer (partitions, filesystems, RAID, or a storage pool). RAID combines drives for performance, redundancy, or both: RAID 0 stripes, RAID 1 mirrors, RAID 5 stripes with distributed parity, RAID 6 uses double parity, and RAID 10 mirrors then stripes.
Why It Matters
Support work involves failing drives, slow machines, cloning, and recovery requests. Knowing that RAID is availability and not backup, or that an SSD's SMART wear indicator predicts end of life, changes the advice you give before data is lost.
How It Works
- NVMe drives use PCIe lanes and deep queues, removing the SATA command bottleneck.
- Parity RAID computes redundancy across stripes so a member can be rebuilt from the survivors.
- Filesystems map logical files onto blocks; deletion typically clears references rather than data.
Where You See It
- Laptop upgrades, server arrays, NAS appliances, virtualisation datastores, and data-recovery requests.
Key Terms
- NVMe
- A protocol for flash storage over PCIe with far lower latency than SATA.
- IOPS
- Input/output operations per second, the usual measure of random performance.
- Parity
- Calculated redundancy data allowing reconstruction after a drive loss.
- SMART
- Drive self-monitoring data that reports reallocated sectors and wear.
- Hot spare
- A standby drive that automatically replaces a failed array member.
Examples
- Replacing a SATA HDD with an NVMe SSD often improves boot and application launch more than a CPU upgrade.
- A RAID 5 array survives one drive loss but runs degraded and slower until the rebuild completes.
Common Problems
- Full system volume
- Failing drive with reallocated sectors
- Rebuild failure in degraded RAID 5
- Cloning to a smaller target
How It Fails
- A second drive failure during a long RAID 5 rebuild loses the array.
- Filesystem corruption after unexpected power loss leaves unmountable volumes.
- Continuing to use a drive with growing reallocated sectors risks total loss.
How to Troubleshoot
- Check SMART and controller logs before assuming a software fault.
- Image a suspect drive before running repair tools that write to it.
- Verify array status and rebuild progress before any further member replacement.
Practical Knowledge
- Take a verified backup before cloning, repartitioning, or firmware updates.
- Match replacement drives in size and, ideally, model to keep rebuilds predictable.
Exam Coverage
- Drive types and interfaces
- RAID levels and usable capacity
- Storage troubleshooting and data protection
Interview Questions
- Why is RAID 6 preferred over RAID 5 for large drives?
- How would you handle a laptop with a failing drive that has no backup?
Watch and read
Verified official and reputable sources for this topic. Links open in a new tab.
Video training
Reading and courses
Lesson notes and bookmark
Notes and bookmarks for this lesson, saved with everything else you have marked.
No notes on this item yet.
Learning progress
0% across six evidence areas. Reading alone does not change progress.
Prerequisites
Next steps
- 01Read the SMART attributes of a drive you own.
- 02Calculate usable capacity for four 4 TB drives in RAID 5, RAID 6, and RAID 10.