A useful backup contains the data needed to recover your service and can be restored when needed. Website files alone may omit the database, and an email export may omit server settings. Backup access, schedules, destinations, retention, and any provider-managed copies depend on your plan and permissions.
In Control Center, Hosting services → Manage website → Backups currently reports that dashboard backups are not configured. There are no dashboard backup, schedule, restore, or archive-download controls. Do not assume a backup exists because this section appears. Contact support to confirm storage, scope, frequency, retention, and recovery arrangements before relying on them.
- Decide what you need to protect: website files, databases, mail, and configuration. Record where each item is stored and how frequently it changes. Ask support which components your available backup method includes.
- If support confirms backup access is enabled for your account, choose Open Virtualmin, then Backup and Restore → Backup Virtual Servers. Select only your intended domain and permitted features. Domain-owner access can be limited; do not assume a full server backup is available.
- Choose a permitted destination and a unique, dated backup name. Keep backups outside public website directories. A copy stored only in the same hosting account cannot protect against every account or server loss.
- Start the backup and read the completion report. Download or transfer the result to private storage outside the hosting account using a supported secure method. Confirm the transfer completed and the file is plausible for the data selected.
- If Virtualmin's Scheduled Backups is permitted and a destination is configured, arrange a schedule within your plan's confirmed allowance. Configure an accessible report destination and review selected features. Virtualmin's backup guide describes the controls and required permissions.
- Set retention deliberately. Keep enough versions to recover from a problem discovered later, and avoid overwriting the only known-good copy. Confirm deletion rules apply only to the intended backup set.
- Arrange a test restore to a safe location or with support. Securely retain any encryption keys separately from encrypted backups.
Check the result: You should have a completed report, a readable backup stored in the intended location, and a documented way to restore it. Check later scheduled runs; saving a schedule is not proof it has run successfully.
Common problems: Insufficient space, expired remote credentials, incomplete database exports, and a failed transfer can leave unusable backups. If the menu is missing, request the service's supported backup options. Never assume a daily schedule or a specific retention period is included unless your plan states it.
Related: Restore a backup, Email exports, Compromise response.
Leave a Reply