An SQL export records database structure and data for a later import. It is useful before a schema change, migration or database deletion, but it does not include website files, mailbox data or the whole hosting account.
IN THIS ARTICLE
What you need before you begin
Choose the correct full database name and decide whether the application needs a quiet maintenance window for a consistent export. For a busy transactional application, confirm the export method provides the consistency required by your recovery plan.
01 Download an SQL database backup from DirectAdmin
- Open MySQL Management and locate the intended database.
- Open its action menu, often shown as a plus symbol, and select the available SQL or compressed SQL download option.
- Save the file to trusted local or independent storage. Keep a descriptive name with the database and date, and protect it because it can contain personal data and application secrets.
- Confirm the download completed successfully. A login page or error response saved with an SQL filename is not a database backup.
- Test the export in an isolated compatible database where practical. Review whether the application also requires routines, triggers, events or other objects and confirm their presence rather than assuming every export includes them.
How do I verify the downloaded SQL backup?
Check that the archive opens, the SQL has expected table definitions and records, and a test import succeeds on the intended database family and version. Keep the accompanying application files and configuration when they are needed for a complete recovery.
Troubleshoot unexpected results
If the browser export times out or the database is too large, ask support for a supported consistent export method. Avoid placing SQL dumps in public_html or emailing an unencrypted dump. Do not overwrite your only known-good backup with an unverified replacement.