# Export local database ## Recommended method : via CLI Once connected in CLI on your server hosting your database, run the following commands: ``` mysqldump -u myuser -p myglpibase > mydump.sql tar -czf mydump.sql.tar.gz mydump.sql ``` ## Alternative method: graphical tool (HeidiSQL) If you are not comfortable with command lines, you can use a graphical tool like HeidiSQL which we recommend here to build your dump. Follow all the steps in this guide to make sure the dump is complete and well built! * Connect HediSQL to your database * Once connected to your database, right click on it. * Click on **`Export database to SQL`** (graphical tool) ![Alt text](/files/XcfT4tyav8lHphxm06sy) In the export tool, make sure that **only** your database is selected. * Check **`Create in Table(s)`** * Choose **`INSERT`** in Data * Choose **`.sql file compressed in ZIP`** in the Destination * Name your file * Click on **`Export`** ![Alt text](/files/c5dQkcu0yNeg4VNjUonn) ## Not recommended * Export via **PHPMYADMIN** : most of the time, dumps are incomplete, with syntax errors, change undesired variable, etc. * **Maintenance menu of GLPI** : Legacy feature, dumps export is incomplete * **Powershell** : most of the time, dumps is done with non-standard encoding --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.glpi-project.org/tutorials/my-instance/export_database.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.