Practical guide

Choose a restore point with the data consequences in view

Last materially reviewed 2026-09-21

Quick answerAn older database can remove newer records even when the application files are correct.
What to know

Choose the recovery objective before the button

A restore point represents an earlier state, not a general repair command. Determine whether the problem concerns files, database content or both, and identify the latest acceptable data state. Cloudways documents application restore choices that can recover those components separately or together. Read the current behavior for the exact application before acting; selecting a recent-looking timestamp does not prove that it contains the version or records you need.

What to know

Account for changes since the snapshot

A fictional membership site may have received new registrations after the chosen backup. Restoring the database can remove those records even if the original technical problem disappears. Preserve and reconcile relevant changes through an authorized procedure before replacing data. Do not treat a successful restore response as evidence that all business information is correct. The acceptance check must include the application version and the data consequences of moving backward in time.

What to know

Understand temporary recovery aids

The Cloudways restore documentation describes a temporary pre-restore recovery point with a limited availability period. Do not confuse that short-lived aid with a permanent independent backup or a guarantee of complete reversibility. Record the exact supported window and operation when planning recovery, and keep the business requirement in view. If a necessary recovery control is unavailable or uncertain, do not invent one to make a risky restore appear routine.

What to know

Verify the restored service and record the result

After an authorized restore, check the affected functions and reconcile the data that matters. Confirm who can access the application and whether external services still use the intended configuration. Preserve the original incident, operation and recovery evidence instead of replacing the history with a clean success label. A restore is accepted when the required service and data are verified, not merely when the hosting interface reports that processing has finished.

Continue when useful

Next: Test a backup as a recovery process, not a badge

A backup is useful when the right person can recover the right data and verify the result.

Open Test a backup as a recovery process, not a badge →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Cloudways restore points and recovery boundaries — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21