Backup is about recovery

A backup is a separate recoverable copy of information. Its purpose is not merely to report success each night; it must let the business restore the right data within a useful time after deletion, failure, theft, ransomware or another incident. Synchronisation helps people work across devices, but it may also synchronise unwanted deletion or damage and is not automatically a complete backup.

Questions every business should answer

  • Which files, email, databases, cloud services and device configurations are essential?
  • Where is the original data, and where are the separate backup copies?
  • How much recent work could be lost without serious harm?
  • How long could each service be unavailable before operations become unacceptable?
  • Who receives and acts on failed-backup alerts?
  • Who is authorised to restore data, and how is their account protected?
  • Is at least one useful copy separated from the ordinary user accounts and affected systems?
  • When was a representative restore last completed and checked?

These answers turn a product subscription into a recovery plan. Different systems may need different schedules and retention periods.

Test the result, not only the job

Choose a safe sample of files and a system owner who understands them. Restore the sample to a separate location, open it, check dates and permissions, and record how long the process took. A database or business application may need an application-aware test rather than a folder copy. Testing should not overwrite the live system or the last known good copy.

Connect the technical recovery to a business continuity plan: who makes decisions, tells staff and customers, and provides a temporary way to work while systems are restored?

What not to do

Do not assume a recycle bin, mirrored drive, synchronisation service or one USB disk is a complete strategy. Do not leave every copy permanently connected under the same credentials. Avoid promising a recovery time that has never been measured, and never overwrite the only known good copy during an incident.

When to stop and ask for help

Get specialist help if ransomware is suspected, the only copy sits on the affected system, backup jobs repeatedly fail, encryption keys are missing or restoration has never been tested. Preserve logs and evidence. Isolate affected systems carefully, but do not destroy information or start a broad restore without understanding the incident.

Prepare for support

List important systems, data locations, approximate data size, backup products, copy locations, retention, recent alert messages and the last verified restore. Identify system owners and the business's acceptable data-loss and downtime limits. Do not attach confidential data or backup credentials to an initial enquiry.