Restore one Virtualmin virtual server by selecting its archive and reviewing the exact features to be replaced. Virtualmin can recover a missing domain, but restoring an existing one can remove current mailboxes, aliases or databases and replace them with backup contents.
IN THIS ARTICLE
Prepare for the change
Confirm the archive identity, date and required keys. Preserve a current destination backup and check software compatibility and free space. For active applications, decide how to retain data created after the chosen recovery point.
01 Restore a single Virtualmin virtual server
- Open Backup and Restore > Restore Virtual Servers. Provide the precise local or remote archive path for the intended domain instead of a broad directory containing unrelated backups.
- Choose all features or only the required data types. A database-only repair should not casually restore unrelated global settings or all mail data.
- Select Show What Will Be Restored and read the preview. Confirm the domain, included objects and overwrite scope before proceeding.
- Test the archive in isolation where practical. Disable outbound notifications and production cron work in the test copy to avoid duplicate business actions.
- Control production writes during the final pre-restore backup and overwrite window. Then choose Restore Now and monitor the feature-by-feature result until completion.
- Check the recovered account and application before reopening writes or moving public traffic. Reconcile newer records through a deliberate application-aware process if they must survive.
Can a domain owner restore every server setting?
Restore permissions are deliberately scoped. Some configuration can affect other services and requires the master administrator. Use the correct authorized role instead of broadening permissions for convenience.
Confirm the expected result
Confirm known records and files from the expected date, then test login, database writes, email and scheduled tasks as relevant. Verify the intended IP and DNS settings on a different destination host. Check that unrelated virtual servers remain unaffected.
If the change does not work
If restoration fails, preserve the archive and detailed log. Resolve resource, permission or compatibility errors before repeating an overwrite. If the selected recovery point is wrong, use the protected pre-restore backup and maintenance plan instead of assuming another restore will merge the two states.