Restore a Webuzo backup only after confirming its date, scope and intended destination. Recovery can replace current files, databases or mail with older data, so it needs a planned overwrite decision rather than a trial-and-error click.
IN THIS ARTICLE
Prepare for the change
Preserve a current backup of the destination account. Confirm archive integrity, free staging space, required runtimes and the exact data types included. For an active shop or mailbox, identify newer records that must be retained before restoring an older recovery point.
01 Restore a Webuzo account from a backup
- Open Server Utilities > Backup & Restore and select the appropriate backup-type tab. Locate the exact dated archive, verifying its source and account identity.
- Review the restore scope. A database restore and a home-file restore affect different components and may need matching points in time.
- Where practical, validate the archive in an isolated test environment before a production overwrite. Prevent the test copy from sending customer email or running duplicate scheduled jobs.
- Control new writes during the production maintenance window, then choose the restore action for the intended archive. Confirm only after reviewing what current data can be replaced.
- Follow the Logs tab until the restore finishes. Do not launch another restore because the first takes longer than expected.
- Test website functionality, database state and mailbox access before reopening the application or changing DNS. Reconcile newer data through a separate documented process.
Will restoring merge current and old databases?
Do not assume a merge. A restore normally reinstates the selected backup data. Preserving newer orders or edits requires an explicit application-aware reconciliation plan.
Check the backup or recovered data
Check a known file and database record from the intended backup date. Test login and a controlled write, confirm ownership and runtime compatibility, and ensure the next backup protects the recovered state. Retain the pre-restore copy until validation is complete.
If the change does not work
If the task fails, preserve the archive and exact error. Investigate space, permissions and version compatibility before retrying. If the recovered state is wrong, use the pre-restore recovery point and maintenance plan; repeated restores do not merge conflicting business data.