A restore can overwrite current data. Choose the smallest recovery that solves the problem and identify what changed after the backup was created. For a store or membership site, newer orders, accounts, and messages may need to be preserved before an older database is restored.
Control Center's Hosting services → Manage website → Backups section is currently unconfigured and has no restore button. Ask support whether a usable recovery copy exists and which restore route is permitted. The steps below apply only to an available backup and authorized Virtualmin or support-assisted recovery.
- Describe the loss and choose a recovery time. Identify whether you need a single file, the database, mail, or several components. Confirm the selected backup predates the problem and contains those components.
- Make a separate copy of the current state where possible, even if it is broken. Label it clearly so it is not mistaken for a clean recovery point. Preserve recent business records before overwriting their storage.
- Confirm you have restore permission and a compatible backup format. Domain-owner restore access may be limited to home-directory and database contents; other settings or mailbox recovery can require support.
- If available, open Backup and Restore → Restore Virtual Servers, choose the source, and select the intended domain and features. Use Show What Will Be Restored to inspect the scope before proceeding. Virtualmin warns that restored components can replace existing data. Virtualmin restore guide
- Prefer a permitted staging or temporary recovery location for inspection. If restoring production, arrange a maintenance period and prevent conflicting writes while related files and databases are restored together.
- Confirm the scope and run the restore. Read the result for each component. If it fails partway through, record the message and contact support before repeatedly rerunning it.
- Check application settings, file ownership through supported tools, database connectivity, and any URLs that may differ in the recovery environment. Restore required current secrets from your secure records rather than reusing known-compromised credentials.
Check the result: Test public pages, login, forms, images, and other key functions. Compare relevant record counts or recent entries with the expected recovery point. Reopen normal writes only after checks pass, then create a fresh backup.
Common problems: A backup can be incomplete, encrypted without an available key, or made after a compromise. Restoring old vulnerable software without fixing the cause can recreate the incident. Ask support about selective recovery when a full restore would discard newer data. Backup availability and successful recovery are not guaranteed.
Related: Create backups, Mailbox exports, Compromised website response.
Leave a Reply