> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.hodi.host/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How do I restore a backup of my Odoo instance?

A wrong move, a failed import, a module that did damage? From Hodiploy you restore any of your instance's backup sets yourself, with no ticket and no waiting.

## Where it happens

1. Log in to Hodiploy from your Client Area
2. On the instance's row, open the **"Actions"** menu, then **"Backups"**
3. Each set is listed with its date, its contents and its state

Two destinations are offered for each set.

## Option 1, restore onto the instance itself

The **"Restore onto this instance"** button puts the instance back into the state of the chosen backup.

> **Read this before clicking.**
>
> **The current data is replaced**, database and attachments. Anything entered since the backup is lost.
>
> **No backup is taken beforehand.** If the current state matters, even a little, run one first with "Back up now".
>
> **Your users will have to log in again**, sessions are not restored. Warn them before, not after.

The instance's **code** is not touched: it still comes from your Git repository. A restore rolls the data back, not your code.

Databases are recreated from scratch rather than restored on top of the old ones: a row deleted since the backup therefore really does disappear, which is the behaviour you expect from a rollback.

## Option 2, restore into a new instance

The **"Restore into a new instance"** button creates a fresh instance and loads the backup into it, without touching the original. That's the right option to:

* check what a backup actually contained before restoring it for real
* reproduce a production bug in an environment where breaking things is fine
* recover a few lost records, without rolling all of production back

The new instance inherits the source's configuration (resources, version, Git repository, email sending settings), and you give it a new name and a new domain.

Two important differences from the original:

* **Its scheduled jobs and email sending are disabled by default**, so a copy of production does not contact your real customers believing it is production
* **Its code is re-cloned from the Git branch**, so it starts in the branch's latest state, not the state of the backup day

## Or simply download it

If you're not after a rollback but after the backup itself, to archive it or open it on your own machine, the **"Download…"** button on the same screen hands it to you piece by piece, without changing anything on the instance. See [how to download a backup](https://help.hodi.host/en/article/how-do-i-download-a-backup-of-my-odoo-instance-14nha50/).

## A locked instance refuses a restore

If the target instance is **locked** ("Actions" menu), restoring over it is refused: that is exactly what the lock is for. Unlock it first. A locked instance's backups do however stay restorable **elsewhere**, into a new instance.

## During and after

The instance shows as **"Restoring…"** for the duration, and goes back to active at the end. The instance's **activity log** records the request, the start, the outcome and who clicked.

## Unsure before restoring?

If you're not sure which set to pick, or which option is the safer one in your case, [contact us](https://hodi.host/contact/) before rather than after, our team will be happy to help you.