GUIDE · HEALTHCARE SECTOR

Clinical data backups: retention and restoration

After this guide you will know which clinical data to copy, how to organise the copies so that an attack or failure does not delete them along with the original, how to test restoration and how to estimate the time needed to return to operations. The subject concerns every facility, even a very small one.

Updated october 2026
7 min read
Altovar Technical Editorial Team

1. Why clinical data backup matters

A backup is a copy of data that can be restored if the original is lost, deleted, encrypted by malware or made inaccessible. For a healthcare facility, losing a patient record or an imaging archive is not merely an administrative problem: it can delay treatment, force information to be reconstructed from the patient and create liability issues. The value of a backup is measured at the moment it is needed, not when it is created.

The best-known rule is 3-2-1: three copies of the data, on two different types of media, one of them off-site or separated from the network. It is not a regulation, but a sound starting point that holds up well in many scenarios. What really matters is that a copy exists, is separated from the working network and has been successfully restored at least once, because a copy that has never been tested proves nothing.

2. Prerequisites: what to know first

Before choosing or changing a solution you need to know which systems hold clinical data, how much space they occupy, how much they change each day and how long they must be retained. Diagnostic images, for example, take up far more space than an administrative system and require different copy and restore times. This information must be requested from the suppliers of the individual systems, as they know their internal structure and the copy mechanisms available.

Also define two parameters with management: how long you can go without a system and how much working data you can afford to lose. These are the two measures that drive how often copies are made and how quickly restoration must happen, and they are management decisions before they are technical ones. Without these decisions in writing, every discussion about frequency becomes a matter of opinion.

3. The steps to set up backups

Work in this order, because the frequency of copies depends on the timings defined in the second step. Do not copy folders at random: a backup whose contents are not known cannot be restored with confidence. Each step must produce a verifiable document or configuration, to be kept together with the facility's continuity plan. An undocumented step should be treated as an undone step until it has been verified.

Always ask your supplier in writing how they back up the systems they manage, because some solutions copy only the database and not the linked files, such as images or attached documents. A generic statement such as the system is protected is not enough: ask what is copied, how often and who can restore it. Keep the document with the continuity plan and update it whenever a system changes.

  1. List all systems that hold clinical data, including those not managed by the IT department, such as shared files and local disks.
  2. For each system, write down the maximum acceptable downtime and the amount of data you can afford to lose.
  3. Check with the supplier whether the system has its own copy mechanism and what exactly it includes.
  4. Set up a frequent local copy and a separate, encrypted copy moved to a different medium or service.
  5. Make the separate copy non-modifiable for a defined period, so that malware cannot delete it along with the original.
  6. Assign an owner to each backup and a deputy, with documented access.
  7. Set a schedule of test restores and record every result.

4. Common mistakes

The first mistake is considering a backup done because the software reports that the operation has completed. A successful result only indicates that the process has finished, not that the data is readable and complete. The second is keeping the copy permanently connected to the working network, where malware can reach it and encrypt it along with the original files. The third is copying only a system's database and forgetting the images or attached documents, which are often the heaviest part.

A fourth mistake concerns retention: copies that are never deleted grow unchecked, while copies deleted too early do not respect the planned timescales. For each type of data, define how long to keep copies and ask an adviser to confirm that these periods are consistent with your obligations. A written plan avoids improvised decisions at clean-up time.

5. How to check that restoration works

A backup is reliable only once you have tested restoring it. Periodically choose a real case, such as a test patient's record or a test image archive, and restore it to a separate environment. Measure the time taken and compare it with what you expected from the second step, because the gap between planned and actual is the most useful information the test gives you.

Also verify that the credentials needed for restoration are available to more than one person and do not depend on a single account. Record the date of the test, who carried it out, the time taken and the problems encountered. This document is the most useful evidence when something goes wrong, because it shows the copy was verified and how long a return to normal operations really takes.

6. How to get started

This week write the list of systems holding clinical data and, next to each one, ask the supplier whether a copy exists and where it is. A complete answer is not needed today: what matters is discovering which systems lack a separate copy. Even an incomplete list with open questions is already a concrete starting point for management. Before closing the meeting, set the date of the next test and the name of the person who will carry it out.

If you find a system without a copy, that is the first thing to schedule, before optimising those already protected. Agree a restore test with the supplier in the following weeks and record the result in the continuity plan. A single successful restore is worth more than a generic statement of compliance. A decision without an owner and without a date tends never to be carried out.

Frequently Asked Questions

Is an external drive enough to back up a medical practice?

An external drive can be part of the solution, but on its own it is not enough. If it remains connected to the computer, the same malware can encrypt or delete it. You need at least one separate copy, with limited access and not always connected. Check with your adviser or supplier that the copy really exists and that a restore test has been carried out.

How often should I make copies?

It depends on the maximum downtime and the amount of data you can afford to lose, two values you need to define with management. A heavily used administrative system requires more frequent copies than an archive that changes little. There is no single frequency that suits everyone: work out the choice from your real working data.

Is the supplier's cloud backup sufficient?

It may be, but it must be verified. Ask what the copy includes, where and for how long it is kept, who can access it, how restoration works and what timescales are stated. Do not assume the copy is separate from your network or that restoration is quick. Put the answers in writing in the contract.

How do I protect copies from deletion by malware?

By separating them from the working network, restricting access to a few credentials protected by multi-factor authentication and, where available, using a mode that prevents modification or deletion for a defined period. A shared common password is not enough: malware that obtains administrator credentials can act on everything.

How long does it take to restore data?

It depends on the data volume, the speed of the medium, the type of system and the procedure available. Diagnostic images usually take longer than a database. The real time is known only by testing the restore, and it should be compared with the maximum downtime management has defined.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →