| Previous | Next |
| STATUS_REGISTRY_RECOVERED | STATUS_FT_WRITE_RECOVERY |
STATUS_FT_READ_RECOVERY_FROM_BACKUP
The read succeeded through redundancy while a member remained unhealthy
STATUS_FT_READ_RECOVERY_FROM_BACKUP is a success-class informational status from NT fault-tolerant volume handling. The important operational detail is not merely that the read completed: a member of the redundant volume failed, the requested data was recovered from another copy, and the failing area could not be reassigned.
Windows documentation describes a fault-tolerant volume as one that maintains more than one copy of data so a copy can remain available after a disk failure. Mirrored and RAID-5 volumes are documented examples in the VDS terminology. This status is consistent with that redundancy role, but it is a degraded-health signal rather than proof that the volume has repaired itself.
Preserve which member failed and which redundant copy supplied the data. Do not wait for an application-visible read failure before investigating. If the unhealthy member or unreassignable area remains in service, later requests can consume the same redundancy margin that just protected this read.
What to inspect
- The fault-tolerant volume and member that produced the original read failure.
- The copy or member that satisfied the read and current redundancy or resynchronization state.
- Disk, controller and volume-management events showing why the failing area could not be reassigned.
References
- Microsoft Open Specifications: VDS glossary
- Microsoft Open Specifications: Disk Management Remote Protocol glossary
- Microsoft: Basic and Dynamic Disks
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.