A database export creates a portable recovery or migration copy of database structure and data. Keep it separate from the website files, and treat it as confidential because it may contain customer information, password hashes and application settings.
IN THIS ARTICLE
What you need before you begin
Identify the correct database and database engine. For an active shop or other write-heavy application, plan a consistent backup or maintenance window. Check available space and choose a private destination outside every public document root.
01 Export and download a database dump in Plesk
- Open Databases for the intended website and locate the exact database.
- Select Export Dump. Choose the private destination directory offered by the form; do not use
httpdocsor another publicly served folder. - Select the automatic-download option if you need a local copy. Start the export and wait for completion before leaving the page.
- Save the complete archive in protected storage and record its date, engine and source database. Preserve all files produced by the selected export workflow.
- Check the archive and perform a test import into a separate compatible database when practical. MySQL/MariaDB and Microsoft SQL Server are different engines; an export is not a universal cross-engine conversion.
How do I verify the exported database dump?
Confirm a plausible size and a readable archive rather than an HTML error page saved with a database filename. Verify important tables and representative records in a test restoration. An export file alone does not include the website code, uploaded media or every external dependency.
Troubleshoot unexpected results
If the export control is missing for a remote Microsoft SQL Server, its server-side backup settings may need administrator configuration. For timeout or quota errors, use the provider-supported export method rather than repeatedly launching jobs. Remove unnecessary temporary server copies only after confirming the protected copy is usable.