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

ZFS mirror basics: redundancy, usable capacity and what happens on disk failure

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

A ZFS mirror stores redundant copies of blocks across mirror members so the pool can continue when a member fails. It provides live redundancy plus ZFS checksumming/self-healing opportunities, but it still does not replace backups, snapshots, capacity monitoring, or a plan for replacing failed devices.

Understand mirror capacity and fault model

Usable capacity is roughly bounded by the smallest member in each mirror vdev; adding a second member does not double usable space. A two-way mirror normally tolerates one member failure in that vdev, but independent simultaneous faults can still destroy data.

Pool topology matters more than the total disk count.

Use checksums and scrubs

ZFS verifies checksums on reads and a scrub systematically reads allocated data so latent errors can be discovered while redundancy is available for repair. Scrubs are maintenance, not backups.

Monitor error counters and scrub completion explicitly; do not assume ZFS will alert someone automatically.

Plan replacement/resilver operations

Know device identifiers, hot-swap procedure, replacement size requirements, and how to attach/replace the failed member. Resilvering can take significant time and I/O depending on data size and pool health.

Avoid offlining the wrong healthy member during a degraded state.

Keep independent recovery copies

Deletion, ransomware, pool-wide hardware failure, operator mistakes, and site loss can affect the mirror as a unit. Use snapshots for local history and backups/offsite copies for separate recovery.

  • Mirror is redundancy, not doubled capacity.
  • Schedule/monitor scrubs.
  • Document device replacement.
  • Keep independent backups.

Next step

Understand two-way ZFS mirrors, resilvering, scrub checks and fault tolerance while keeping separate backups for failures a mirror cannot undo.

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