The reference desk / In practice

Backup

A copy of data kept so integrity and availability can be restored after loss, preferably beyond the production identity’s reach.

What it means

A backup is useful when it enables recovery of the data and service the organization actually needs. That requires more than a successful copy job. Teams must know which versions exist, how long they are retained, who can delete them, and whether restoration needs keys or identities that could also be lost. Separate protection from production administration can reduce the chance that one compromised account destroys both originals and copies. Recovery planning also defines acceptable data loss and downtime; those requirements determine whether the backup approach is adequate.

AN ILLUSTRATIVE SCENARIO

A dental practice tests recovery

A dental practice copies appointment data every night. A restoration exercise reveals that the backup contains the database but not the application configuration or encryption key needed to open it. The team adds those dependencies to its protected recovery process and restores into an isolated test environment. Reception staff confirm that appointments and attachments are usable. They also learn how to operate a temporary schedule while restoration runs, rather than discovering the procedure during an outage.

Put it to work

  1. Identify the service, data, configuration, keys, and dependencies needed for recovery. Agree how much data loss and downtime the business can tolerate, and select copy frequency and retention accordingly.
  2. Protect backup access separately, restrict deletion, and use appropriate offline or immutable copies where feasible. Monitor failed jobs and expired retention instead of relying on an occasional dashboard check.
  3. Restore representative data and whole workflows on a schedule. Keep the test isolated, record the elapsed time and missing dependencies, and fix the recovery instructions while the findings are fresh.

How to check your work

Restore a selected recovery point without relying on the original server. Have the business owner check record completeness and application use, compare actual recovery time and data loss with requirements, and confirm production credentials cannot erase the protected copy.

Connect the ideas

  • Ransomware

    Malware or an operator model that denies availability of data, often by encryption, sometimes with theft for extra pressure.

  • Availability

    The property that authorized people can use a system or record when they need it.

  • Postcondition

    The independently checked state of the world that should be true after a response action.

Explore a field lesson

Find your next idea.

Tip: press / to open search. Escape closes this window.