> For the complete documentation index, see [llms.txt](https://docs.migration-center.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.migration-center.com/24.2/installation-guide/backup-and-restore.md).

# Backup and Restore

Since in migration-center all the critical data and configuration is saved in the database, only backing up the migration-center database schema is needed. 

## **Backup a migration-center database**

{% hint style="danger" %}
Before starting the backup process ensure that there are no scanners, importers, transformation / validation jobs and no scheduled jobs running
{% endhint %}

To back up a database used by migration-center it is sufficient to back up only the data within the `FMEMC` schema. The easiest way to do this is with Oracle’s **EXP**. See screen shot below for the basic steps required to back up a schema. For more information consult the documentation provided by Oracle.

![](/files/-M7JoJznrZD686x5vW90)

{% hint style="warning" %}
Starting with Oracle 11g release 2, the empty table might not be exported at all. This happens when the database parameter DEFERRED\_SEGMENT\_CREATION is set to TRUE. Initially this p~~ar~~ameter is set to TRUE. To force exporting all tables from the FMEMC schema the following commands should be run connected as user `FMEMC`:\
`ALTER TABLE SCHEDULER_RUNS ALLOCATE EXTENT;`\
`ALTER TABLE SCHEDULERS ALLOCATE EXTENT;`
{% endhint %}

## **Restore a migration-center database**

To restore the backup, follow the steps below:

1. If the database instance where the backup should be restored does not contain the `FMEMC` user, please create it first as it this describe in the [Installation Guide](/24.2/installation-guide/install-migration-center.md#advanced-db-installation). 
2. Use Oracle’s “imp” utility for importing the dump file previously created by the “exp” utility. See screen shot below for the basic steps required to restore a database schema from a dump file. For more information consult the documentation provided by Oracle.

![](/files/-M7JoJzoDKyMC4qifS4F)

{% hint style="warning" %}
The same character sets in the Oracle Client should be used when exporting and importing the data.
{% 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.migration-center.com/24.2/installation-guide/backup-and-restore.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.