What this means
What this means
Backups reduce risk, but recovery must be tested enough to know what can be restored, by whom, and how quickly.
Before you start
Before you start
Identify the service, backup source, latest backup time, database/files scope, and recovery objective.
Step-by-step guidance
Step-by-step guidance
- Check whether the service has backup or snapshot information in the portal.
- Do not delete old hosting until migrated content is verified.
- Ask what restore point is available before risky changes.
- For VPS, understand whether snapshots or backups are request-only.
- After restore, verify homepage, login, forms, email, and app health.
What CM Cloud support will review
What CM Cloud support will review
Support reviews backup availability, retention, data scope, restore risk, and whether rollback is metadata-only or needs provider action.
What is not automated yet
What is not automated yet
Reading this guide does not create backups, restore files, snapshot VPS, or change production data.
Safety note
Safety note
Reading this article does not capture payment, provision infrastructure, register or transfer domains, change DNS, write Cloudflare or WHMCS, call providers, start workers, create retries, or enable live execution.
Safe next action
Safe next action
Open a backup/restore support request with service ID, desired restore time, and reason.