Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Backups

RAID is not a backup: what redundancy protects and what it cannot recover

Published August 2026 · 2 min read · Updated 2026-09-05

RAID improves availability against certain disk failures by keeping redundant live data, but it immediately mirrors corruption, deletion, ransomware, and application mistakes. Backup keeps historical recovery points and should survive failures outside the live array. They solve different problems.

Know what RAID can keep running through

A mirror or parity array can tolerate a defined number/type of drive failures while the array remains degraded. It can reduce downtime waiting for a disk replacement, but rebuild itself creates stress and does not guarantee protection from multiple failures.

Monitor SMART/array state so degraded operation is not ignored.

Know what RAID cannot undo

Deleting a directory, overwriting a database, encrypting files with ransomware, or an application writing bad data is reflected across redundant members. Controller/filesystem/server/site failures can also exceed the RAID boundary.

Snapshots add history but may still share the same system failure domain.

Design backup independently

Keep versioned copies on separate storage with credentials/retention appropriate to recovery objectives. Include application-consistent databases and the configuration needed to rebuild, not only raw filesystem bytes.

RAID status should not decide whether backup jobs run.

Test both disk and data recovery

Practice replacing/rebuilding a failed member according to the array procedure and separately practice restoring lost data from backup. These are distinct runbooks.

  • RAID = live redundancy.
  • Backup = historical recovery.
  • Keep backup outside array failure domain.
  • Test both runbooks separately.

Next step

Understand how RAID handles some disk failures while deletion, corruption, compromise and site loss still require independent, versioned backup copies.

Explore DotMoose backup storage

Keep reading

Related guides.

Backup capacity planning: estimate storage from change rate and retention

Model source size, daily change, compression, deduplication, retention and growth so backup storage is sized from the workload instead of one full-copy estimate.

Read the guide

Backup encryption basics: protect copies at rest and in transit

Choose where backup data is encrypted, how keys are stored and recovered, and how restore operators gain access without putting the only key beside the backup.

Read the guide

Backup recovery drills: prove the restore process before an outage

Run isolated recovery tests, measure restore time, verify application state and record missing dependencies so the backup plan is based on tested recovery.

Read the guide

More backups guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move