A recoverable website backup includes its application files, uploaded content, database and the configuration needed to connect them. The exact set depends on the site: a static HTML site may not have a database, while WordPress stores important content in both places.
Write down what recovery needs
Include the domain mapping, runtime version, scheduled tasks and external services in a small recovery note. Keep secrets in an appropriately protected store. An installer export or content-only WordPress export should not be assumed to contain a complete hosting account.
- Identify files and databases that change together.
- Choose a backup time or application-aware method that keeps them consistent.
- Create the backup through supported hosting or application tools.
- Download or replicate a protected copy outside the live hosting account.
- Record the date, application version and intended restore procedure.
- Check that the archive opens and contains the expected data.
Restore away from production
Use a private staging destination with its own database. Disable real email, payments and scheduled jobs before starting the restored site. Check login, media, a representative page and the most important data. A successful download alone is not a restore test.
Record how long recovery takes and which manual steps were needed. If the backup is encrypted, verify you can access the recovery key independently of the failed account. Keep the test copy private because it may contain customer data.
Choose the restore point deliberately
Preserve the current state before replacing it, even if the site is broken. A restore can discard orders, comments or edits created after the backup. Identify the last known-good point and decide how newer valid changes will be recovered.
Retention and restoration options vary by service. Check the copies actually available to your account rather than assuming a daily backup means every historical date is recoverable.
Use staging for the rehearsal and the migration checklist when moving the restored site to a new host.
Sources and references
Hosting documentation. Publication and update dates reflect this edition.
Related articles
- Moving a WordPress Website to Another Hosting AccountMove files and database together, test before DNS cutover and preserve a clear rollback path.2 min read
- Creating a Private Staging Copy of Your WebsiteTest updates with separate files and data while preventing indexing, real emails and accidental production writes.2 min read
- Diagnosing a WordPress Critical Error After an UpdateFind the first PHP failure, isolate the changed component and recover without exposing debug logs.2 min read
