A database restore can replace recent orders, posts, user accounts and settings. Define the intended recovery point and preserve newer business activity before starting.
IN THIS ARTICLE
01 Prepare and restore
- Confirm the exact live database and the backup point that addresses the incident.
- Export the current database and record transactions after the proposed recovery time.
- Arrange an appropriate maintenance window or pause of writes with the application owner.
- In CodeGuard, locate the database's available backup and Restore Options. For an unassigned database, open it from Other Databases and inspect its own history.
- Choose the supported automated restore or download the backup for a controlled manual import, then verify the application's expected records.
02 Coordinate application state
Match the restored database with compatible application files. Reconcile newer orders and other business activity using an approved application-aware process. A full database rollback does not merge new records into the old copy automatically.
Common questions
Does restoring website files include every database?
No such coverage should be assumed. Unassigned databases require separate handling, and only successful retained database backups can be restored.
What if the database connection is broken?
Repair access before an automated restore, or use a downloaded backup through the authorised database administration process. Do not delete the live database merely to test whether the connection improves.
How do I verify completion?
Check application login, important tables or records, a harmless write and the relevant business workflow. Confirm the site's configured database points to the restored target.
Keep maintenance in place until the responsible owner accepts the result. Record the restored timestamp, validation and any newer data that still needs reconciliation. Run a new verified backup after the accepted recovery.