mirroring · shipping

Mirroring (storage)

Storage mirroring maintains a copy of source data on another storage device or system.

Related Observatory article: Read on hesela.com

Mirroring describes a maintained-copy relationship, not an unconditional promise of instantaneous failover. The acknowledgement policy determines how far an update must progress before success is reported. Failover additionally depends on failure detection, replica eligibility and preventing conflicting writers. DRBD illustrates different completion boundaries for replicated block writes; those are not database query-visibility guarantees. A mirror set is one local redundancy group, not necessarily a full copy of a striped array or pool. The RAID10 example explains why the positions of failed members matter. [5]

Relations

related
RAID, Enterprise SSD, Synchronous replication, Asynchronous replication, Replication lag, I/O fencing, Failure domain, Mirror set, RAID 10, LVM, Striping (storage), RAID 1

Citations

  1. Hesela: RAID 10 mirror topology and exact failure-set counts (accessed 2026-10-15)

Further reading

  1. Mirroring (storage) (accessed 2026-03-26)
  2. SNIA Swordfish 1.2.8: ReplicaType Mirror (accessed 2026-10-12)
  3. LINBIT DRBD 9 guide: section 2.3, replication modes (accessed 2026-10-12)
  4. Replication acknowledgements: received, durable, applied (accessed 2026-10-12)

JSON: /data/terms/mirroring.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Mirroring (storage). Hesela. 2026-10-15. https://hesela.dev/terms/mirroring/