Select a CodeGuard recovery point by its contents and timing, not merely because it is the newest backup. A recent backup may already contain the mistake or infection you are trying to remove.
IN THIS ARTICLE
01 Choose the right point
- Establish when the site last worked and when the problem first appeared. Include the time zone.
- Open the site's backup history or Restore area and display additional backups if needed.
- Compare available file and database timestamps with the incident window.
- Browse or download a candidate to check a representative affected file or record.
- Record the chosen point and the changes that occurred after it before approving a restore.
02 Review retention
Check the account's configured retention and actual available history. Shortening retention can remove older recovery points across the configured scope. Review business requirements and preserve required exports before making that change.
Common questions
Does daily backup mean it runs at the same time each day?
CodeGuard's documented backup times can vary. Use the actual completed timestamp for a restore decision.
Can I recover a date that is not listed?
Only an available retained copy can be used. Check all history and any independent backup source, but do not assume missing periods can be recreated.
Should files and database use the same date?
They should form a compatible application state. Match the incident and deployment context, and account for any data written between their backup times.
For a busy store, identify orders, payments and customer updates after the proposed database point. A rollback can remove that newer activity. The owner and developer should decide how to preserve or reconcile it before the restore starts.