How to Back Up a Joomla Database Manually
Confirm which database Joomla actually uses
Before exporting anything, identify the database configured for the Joomla site. configuration.php contains the database connection settings, but handle that file carefully because it includes credentials. On hosting accounts with several databases, verify the selected database contains the expected Joomla tables before exporting it.
Choose an export method supported by the environment
Most shared hosts provide phpMyAdmin or a comparable database manager. Joomla documentation also describes command-line export methods and Joomla's CLI database exporter in supported environments. Use the method you can operate reliably and that can export the entire Joomla database.
Export all Joomla tables
In phpMyAdmin, select the correct database and use Export to create a database dump. Do not select only obvious core tables: installed extensions can have their own tables and may fail or lose data if those are omitted. Preserve table structure and data needed to recreate the database.
Use a consistent point in time
For a highly active site, coordinate the database export with the filesystem backup so content changes do not create a mismatched recovery set. Joomla's backup guidance traditionally recommends temporarily taking the site offline during manual backups. Database-native snapshot or transaction-safe methods may provide other consistency options when properly configured.
Protect the database dump
A Joomla database can contain user records, email addresses, configuration values, tokens, extension data, and other sensitive information. Move the dump to protected off-server storage and remove temporary public copies. Do not attach an unredacted production database to ordinary support tickets.
Inspect the export for basic validity
Confirm the dump is not zero bytes, opens as the expected SQL or database-export format, and includes table definitions and data for representative Joomla tables. Record the database server type/version when it may affect restoration. Compression is fine as long as the archive can be opened and the dump recovered.
Test importing into a separate database
The strongest verification is to import the dump into a disposable or staging database and confirm that the expected tables and records appear. Joomla's documented copy/restore procedures use database import as part of moving a site. Never test a restore by overwriting the only live production database.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.