← All articles & guides

A “backup successful” status does not prove that the application will recover when you need it. An organised restore test demonstrates that.

Choose what to restore

Start with a representative application or dataset and define which user will confirm that the result works.

Prepare a safe environment

Run the test in a suitable isolated environment. Check resources, licences, network settings and dependencies such as databases or identity services.

Record the entire process

  • Access to the correct backup.
  • Transfer and preparation time.
  • Application startup.
  • Functional verification by a user.
  • Errors and manual steps missing from the documentation.

Turn findings into corrective actions

Assign an owner and a retest date to every gap. A successful test provides evidence for that specific scenario, rather than a general guarantee for every incident.

Related services

UniLoud Backup organises data protection, while Disaster Recovery covers the overall return to operation.

Necessary functions keep the site and forms working. Optional Google Maps stays off until you allow external content. Web push and advertising tracking are not enabled.