Healthcare custody technical note
Healthcare RAID recovery can begin while the drives remain onsite.
The failed server does not need to boot, the volume does not need to mount, and the failed array does not need to be brought online before ADR can begin evaluating the member state. When the drives can be labeled, connected independently, and read safely, the client can retain custody while protected images and reconstruction evidence are developed.
This is case-dependent. Member stability, available hardware, security controls, usable destination capacity, and the failure history determine whether work can proceed onsite or whether a specific member requires laboratory attention.
A different recovery environment
The failed server is evidence. It does not have to become the recovery workstation.
Depending on the case, members may be connected to a suitable bootable computer through direct SATA/SAS hardware, supported adapters, or a controlled multi-bay environment. ADR evaluates source readability, creates protected images when appropriate, determines array geometry, and reconstructs from those protected sources.
When onsite custody fits
The decision follows source condition—not a blanket remote-versus-lab rule.
A case may begin onsite even when the server is offline. The limiting question is whether the relevant sources can be accessed and protected without exposing them to avoidable writes or unstable repeated reads.
- 1
Stable, independently readable members
ADR can guide source identification, protected imaging, geometry analysis, and reconstruction while the drives remain under client control.
- 2
An unstable or unreadable member
Stop repeated reads. That member may require targeted firmware, electronics, mechanical, or specialist work before a trustworthy image can be produced.
- 3
Database or repository failure above stable storage
Preserve the complete file, log, backup, export, VM, and repository set before attachment, repair, or extraction.
- 4
Security or infrastructure constraints
Confirm approved access, encryption, destination storage, network controls, staffing, and chain-of-custody requirements before work begins.
Choose the controlled path
Keep the full array onsite when the evidence supports it. Escalate only what requires escalation.
Need to keep the drives onsite?
ADR can evaluate the failure and define the recovery environment before anything ships.
Provide the server, controller, enclosure, number and size of drives, displayed errors, actions already taken, available connection hardware and destination capacity, required healthcare data, and custody constraints.