A restore replaces selected data with an earlier copy. Before using CodeGuard recovery, decide what needs to be restored and what newer data must be preserved. Restoring a whole website to yesterday can remove today's orders, uploads or customer changes.
IN THIS ARTICLE
01 Choose a suitable recovery point
Identify when the fault began and inspect the available backup history. For a compromise, choose a copy from before the suspected entry point, while recognising that an older copy can still contain a vulnerable application. Confirm that the selected backup includes both the needed files and database.
- Preserve the current state if possible. Download important recent records or create a separate backup so useful data is not lost during recovery.
- Open the correct website in CodeGuard and review the restore options provided by your package. Choose individual files, a database or a wider restore according to the incident.
- If a staging or preview restore is available, test there first. Confirm the restored application opens and its database content is consistent.
- Arrange a maintenance period for a live database restore. Pause writes, orders and background jobs as appropriate so changes do not continue during replacement.
- Confirm the target website, backup date and scope, then start the restore once. Wait for the recorded result before retrying or running another recovery action.
- Review completion details and test the site. Check login, images, forms, database reads and a reversible write, then re-enable scheduled jobs carefully.
02 After a security incident
Update vulnerable software, replace exposed credentials and investigate the cause before returning to normal operation. Restoring clean-looking files without fixing the entry point can lead to another compromise. Keep relevant logs and incident notes for the investigation.
What should I check if the CodeGuard recovery is incomplete?
Check whether the missing data was in the selected backup and whether its connection or directory had been excluded. A successful file restore does not prove the database was restored. Preserve the restore report and ask support about the specific failed items rather than repeatedly replacing the whole site.
Once the recovered site is verified, create a fresh recovery point and check subsequent scheduled backups. Keep any evidence or reconciliation copy you still need in protected storage. Remove publicly accessible backup archives from the website.