Clinic certifies HDS on compute. Audit asks where nightly backups live, who restores, whether off-site copy is in scope. Vague answer — non-compliance on critical component.
HDS covers hosting health data, not only primary disks. Backups and restore are almost always mandatory in risk analysis.
Without HDS-scoped backup, continuity plan fails regulatory review.
Certified prod, forgotten backup
Prod DB, snapshots, off-site backup, restore procedure, logs — each component to align.
See health data HDS.
Demand from provider
Certificate mentioning backup/restore, prod→copy diagram, frequency, encryption, who restores, DR test reports. OVHcloud, Outscale, Cloud Temple.
DIY backup
If you manage backups: prove equivalent measures or subcontract HDS scope. Restore tests = your proof — restore proof.
The peak: badge on VM not copy
Continuity and authorities
In health, continuity is not isolated from regulatory file. If production is HDS-certified and backup copy is not, assume gap explicitly in risk analysis and establishment contract. Authorities watch full data path, not badge on primary VM.
Demand dated prod → backup → restore diagram with locations, frequencies, encryption, operator identity. Without it, two HDS providers are not equivalent.
Go further with the inquiry
Apply the article to your concrete case: what volume, what service level, what contractual constraints from clients or regulators? Write answers before opening the pricing page. Request written documents — full grid, DPA, certification scope, renewal terms — not homepage screenshots.
Compare at least two providers via the directory and compare tool on identical thirty-six-month assumptions. Share the short list with whoever signs the contract and whoever operates infrastructure daily. Archive terms dated at subscription so due diligence is defensible later.
Go further with the inquiry
Apply the article to your concrete case: what volume, what service level, what contractual constraints from clients or regulators? Write answers before opening the pricing page. Request written documents — full grid, DPA, certification scope, renewal terms — not homepage screenshots.
Compare at least two providers via the directory and compare tool on identical thirty-six-month assumptions. Share the short list with whoever signs the contract and whoever operates infrastructure daily. Archive terms dated at subscription so due diligence is defensible later.
Continuity and authorities
In health, continuity is not isolated from regulatory file. If production is HDS-certified and backup copy is not, assume gap explicitly in risk analysis and establishment contract. Authorities watch full data path, not badge on primary VM.
Demand dated prod → backup → restore diagram with locations, frequencies, encryption, operator identity. Without it, two HDS providers are not equivalent.
Continuity and authorities
In health, continuity is not isolated from regulatory file. If production is HDS-certified and backup copy is not, assume gap explicitly in risk analysis and establishment contract. Authorities watch full data path, not badge on primary VM.
Demand dated prod → backup → restore diagram with locations, frequencies, encryption, operator identity. Without it, two HDS providers are not equivalent.
Decide and move forward without blind spots
Start by framing your real scenario on one page: volumes, client constraints, required support level, and a thirty-six-month budget including domain, backup, and essential add-ons. Compare at least two hosts via the directory and compare tool with identical assumptions, archive pricing grids dated on subscription day, then have both the contract signer and daily infrastructure operator validate the short list.
Frequently asked questions
Backups in HDS scope?
If health data, yes — provider coverage or equivalent proof.
Copy outside France?
Depends certificate; undocumented = major gap.
Who tests restore?
Controller accountable; provider documents, you prove tests.
Managed backup covered?
Only if explicitly in certificate you use.
Ask for certificate and backup diagram — one without the other half-closes the file.