Our NabWP backup tools can restore a website from an available recovery point, but the date and scope of that recovery point matter. Restoring older files or a database can replace newer work. Before starting, decide what failed and what you need to recover, then identify the most suitable completed backup for that purpose.
IN THIS ARTICLE
01 Prepare and carry out the restore
- Select a suitable completed recovery point. Open the correct website in WordPress Manager and review its available backups. Check the timestamp, backup source and restore options. If the problem began after a known update or edit, a recovery point from before that event may be useful. When the issue involves suspected malware, confirm that the chosen backup is suitable rather than assuming any older copy is clean.
- Preserve current data. Preserve the current state first where practical. Even a broken website can contain recent orders, enquiries, uploads or drafts that are absent from the older backup. If the website continues accepting transactions, coordinate the recovery with our team so that new activity is accounted for. A database restore does not automatically merge newer customer records into the old database.
- Run the supported restore. Start the supported restore operation only after reviewing what it will replace, then wait for its reported result. Avoid launching overlapping restores or making unrelated edits while recovery is running.
- Verify the recovered website. When it finishes, verify the public website, WordPress login, important content and the functions involved in the original problem.
02 Check the original cause and the recovery method
Check forms, checkout or other integrations if your site uses them, and review whether the original cause still needs repair. A full backup restore is different from recovering a page revision or undoing a supported Engineer file edit. We can help select the smallest appropriate recovery method when you explain the affected website, the change that preceded the issue and the data you need to preserve.
What happens to new orders or registrations during a restore?
- Choose a suitable completed backup and preserve any newer orders, submissions or uploads that must survive.
- Coordinate the live site's ongoing activity before replacing database data.
- Wait for the reported restore result, then test the public site, administrator access and the function that originally failed.
A restored database is not automatically merged with newer business records. If only one file or page changed, a narrower supported recovery method may avoid unnecessary data replacement. Check that the restored copy is appropriate for the incident, particularly when malware may predate the backup.