A “backup completed successfully” notification does not by itself prove that your entire website will work when you need it. Checks should demonstrate that the right data was backed up, the copy is accessible, and restoration works. Business owners do not need to learn every server command; they need to know what evidence to request from the maintenance team.

Define backup scope around your business first

A corporate website’s files may be backed up while recent quote requests remain only in the database. In e-commerce, products, orders, customer accounts, and uploaded media may be stored in different places. Work with the technical team to list which data sits in which system. Set backup frequency, retention, and acceptable data loss according to business needs. For example, in a system handling many transactions during the day, an old copy may bring the site online without recovering recent transactions. Request coverage for the database, files, media, and configuration rather than a single general maintenance item. Do not assume data held by another provider is automatically included.

  • Which systems and datasets are included?
  • When was the last successful copy made?
  • How will missing transactions be reconciled?

Test restoration separately from the live website

The NCSC recommends testing restoration as well as taking regular backups. Do not copy production data to a publicly accessible test website for this check. With appropriate privacy measures in an access-restricted environment, assess whether the application starts, data can be read, and files can be found. Handle connections that send real emails, payments, or messages externally in a controlled way in this environment. ReklamKlik’s recommended acceptance record includes the date of the copy used, functions checked, gaps identified, and person responsible. The check date and backup date differ: a restoration test performed yesterday does not by itself verify the integrity of today’s copy.

  • An access-restricted restoration environment
  • Checks that generate no real payments or customer notifications
  • Recorded dates, results, and gaps

Protect the backup copy and the recovery decision together

A single copy within the same access boundary as the main system may be affected by the same incident. Assess independent copies, access restrictions, and recovery methods with your maintenance team. Having authority to decrypt an encrypted copy matters as much as where it is stored. Document in advance which copy will be selected, how missing transactions will be checked, and who will decide when recovery is needed. Before going live again, review administrator access, forms, critical pages, and order flows where relevant. Do not close the check with a single word such as fine; state which scope was successfully tested. This turns the maintenance report from a file-creation notification into an actionable business continuity record.

  • A copy independent of the main system
  • Recovery authority and owner
  • Critical function checks before publication

Sources

LET’S ADAPT IT TO YOUR BUSINESS

Let’s define the next step together.

Share your goal and current situation; let’s discuss a scope suited to your needs.

Request a quote →