> For the complete documentation index, see [llms.txt](https://docs.monolithforensics.com/monolith/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monolithforensics.com/monolith/deployment-and-security/on-premises-deployments/backups/restoring-backups.md).

# Restoring Backups

Restore a Monolith MySQL database from a previously created SQL dump using MySQL Workbench.

This page covers restoring a Monolith MySQL database from a previously created SQL dump.

### Backup File

This restore process assumes that you previously created a SQL dump of your Monolith MySQL database.

A SQL dump is a text-based backup containing SQL statements that can be used to recreate database tables, data, and other supported database objects.

### Database Schemas

MySQL uses databases, also referred to as schemas, to organize tables and data.

A MySQL server can contain multiple databases or schemas. Your Monolith data is stored within the Monolith database configured for your deployment.

When restoring from a SQL dump, confirm that the backup is being restored to the intended Monolith database or schema.

#### Recommended Tool

* **MySQL Workbench** is a MySQL administration tool that includes utilities for importing and exporting database data.

### Restore Steps

1. Open **MySQL Workbench**.
2. Confirm that Workbench has a connection to the MySQL server used by your Monolith deployment.
3. Open the connection to the Monolith database server.
4. From the menu bar, select **Server > Data Import**.
5. Open the **Import from Disk** tab.
6. Under **Import Options**, select **Import from Self-Contained File**.
7. Select the Monolith SQL backup file. The file should typically have a `.sql` extension.
8. Select the appropriate target schema if required.
9. Select **Start Import**.

MySQL Workbench will process the SQL dump and restore the database objects and data contained in the backup.

{% hint style="info" %}
Some SQL dumps include statements that create or select the original database automatically. Others require you to choose an existing target schema during import.

Before starting the restore, confirm that the SQL dump and target schema match the Monolith database you intend to recover.
{% endhint %}

{% hint style="warning" %}
Database restoration can replace or modify existing Monolith data. Before restoring a production database, confirm that you have a current backup and that the correct MySQL server and schema have been selected.
{% endhint %}

### Related Documentation

* [**Backups**](/monolith/deployment-and-security/on-premises-deployments/backups.md)
* [**Monolith Data**](/monolith/deployment-and-security/on-premises-deployments/monolith-data.md)
* [**Using External MySQL Database**](/monolith/deployment-and-security/on-premises-deployments/using-external-mysql-database.md)
* [**On-Premises Deployments**](/monolith/deployment-and-security/on-premises-deployments.md)
* [**Deployment**](/monolith/deployment-and-security/on-premises-deployments/deployment.md)