Export a database before a migration, application upgrade, or data change. Store the export with a matching backup of your website files. A SQL import can replace existing tables, so verify the destination before you run it.
Start in Hosting services → Manage website → Databases to identify the database and create a destination if needed. Imports, exports, user permissions, and deletion remain in Virtualmin. The dashboard's Backups tab is not a configured backup service.
Export a MySQL or MariaDB database #
- Select the site's domain and open Edit Databases.
- Find the required database and choose Manage, then Backup Database, if those actions are available.
- Include the complete structure and data unless your developer has requested a partial export. Choose a private destination permitted by your account, outside the public website directory.
- Run the export, check the completion result, and download it through a secure connection. Label it with the site and date. Virtualmin database management
For a site accepting orders or other frequent changes, arrange a consistent backup window with your developer. A file's existence alone does not prove that the export contains a complete, usable snapshot.
Import a SQL backup #
Create a fresh destination database where possible and keep the existing application database intact until testing succeeds. Confirm that your dump suits the destination engine and version.
In the destination database's management page, open Execute SQL and locate the SQL-file execution section. Choose an uploaded file or a private server-side file as offered, confirm the destination, then execute the import. Read the final output for errors before retrying. Webmin's database module uses this route for SQL-file restoration. Webmin backup and restore guide
If your host provides phpMyAdmin instead, use its export/import tools for that database. PostgreSQL backups require its supported tools and formats; a MySQL dump is not interchangeable.
Verify the restored site #
Check table presence, recent records, text characters, and the application's login. Update its private connection settings if the destination database name or credentials changed. Test a write operation through the application.
Troubleshooting #
For timeouts or upload limits, ask support to handle a large import; do not repeatedly import into partially populated tables. Share the first error and engine versions, not the database contents. Preserve your verified copy before removing temporary server exports.
Related: website migration checklist.
Leave a Reply