> 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/monolith-features/on-premises-deployments/backups/restoring-backups.md).

# Restoring Backups

This section will cover restoring a database backup of your Monolith MySQL database.

## Backup Data

This restore process assumes you have previously created a SQL dump of your Monolith database from MySQL.  A SQL dump file is a plain text file that contains your database data in a SQL format.

## Database Schemas

MySQL has a concept called "schemas".  Schemas are the data segments within MySQL that store tables and data.  You can have any number of schemas within a MySQL database.  Your Monolith data is stored within a single schema within MySQL.

Schemas are the data object that we will backup and restore from backups.

## Restore Steps

Recommended Tools:

* MySQL Workbench
  * This is a free tool provided by the MySQL team to access and manage MySQL databases.  It also has several useful utilities including database backup and backup import services.

1. Open MySQL Workbench
2. Ensure that Workbench has a connection to your Monolith database.
3. Open your Monolith database in MySQL workbench.
4. Select "Server >> Data Import" from the Workbench menu bar.
5. The import wizard should start at the "Import from Disk" tab - select this tab if its not selected.
6. Under "Import Options", check the radio button for "Import from Self-Contained file".
7. Use the file select browser to locate and choose your Monolith database backup, which should have a ".sql" extension.
8. (Optional) Select a default target schema or create a new one.
   1. This is optional because your SQL dump file likely already has a directive to create a new schema with the correct name.
9. Click the "Start Import" button.

This process will create a new "schema" and populate it with tables and data from your Monolith database backup.

{% hint style="info" %}
If the new schema has a different name from your original Monolith schema (database), then you may need to update your Monolith deployment configuration.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.monolithforensics.com/monolith/monolith-features/on-premises-deployments/backups/restoring-backups.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.