A RAID controller manages physical drives and presents storage to the operating system according to the configured RAID or HBA mode.
Practical example: choosing RAID for a file server
RAID availability and backup recovery solve different problems.
Scenario: A business file server needs usable capacity, reasonable write performance and tolerance for a drive failure.
RAID 0 would provide no redundancy, so it is unsuitable for this requirement. RAID 1 is simple but uses half of the raw capacity for mirroring. RAID 5 and RAID 6 introduce parity and different failure-tolerance and write-performance trade-offs. RAID 10 combines mirroring and striping but also has a significant capacity overhead.
Decision: Choose the RAID level from the workload, number of drives, rebuild risk, usable-capacity requirement and controller support. Then create a separate backup because RAID does not protect against deletion, corruption, malware or loss of the entire server.
Common mistakes and selection checklist
Common mistakes
- Selecting RAID only from the amount of usable capacity it provides.
- Ignoring rebuild time, drive count, write workload and the consequences of another drive problem during recovery.
- Treating RAID as a backup.
What happens if you get it wrong?
The array may have the wrong performance or resilience characteristics for the workload. A controller, corruption, deletion, malware event or complete system loss can still make the data unavailable even when the RAID level itself is working as designed.
Selection checklist
- Define the usable-capacity target and workload before selecting a RAID level.
- Check the minimum and practical drive count for the chosen layout.
- Consider write behaviour, rebuild exposure and failure tolerance.
- Verify controller, drive and server-platform support.
- Maintain a separate tested backup and recovery process.
Hardware RAID controller
A hardware RAID controller uses dedicated firmware and processing to manage arrays. Depending on the model it may include protected write cache, drive monitoring and management functions.
Cache protection
Write-back cache can improve performance, but cached data must be protected during power loss. Controllers may use battery-backed or flash-backed cache depending on the platform and generation.
HBA and pass-through modes
Some storage designs require direct drive visibility rather than hardware RAID. A controller or host bus adapter may support HBA or pass-through operation for software-defined storage and certain operating systems.
Compatibility checklist
- Supported server and firmware
- SAS, SATA or NVMe drive support
- Backplane and cable compatibility
- Supported RAID levels
- Cache module and protection
- Drive count and performance
- Operating system and management tools