How do I download a backup of my Odoo instance?

Your backups aren't only there to be restored with us: you can download them, piece by piece, and do whatever you like with them. An offline archive, an analysis on your own machine, or a move to another host: it's your data, and it comes out.

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. On the set you're interested in, click "Download…"

The set's contents then appear, piece by piece, each with its size. That's the information that matters before clicking: a 40 MB database and a 12 GB database are not downloaded under the same circumstances.

What you can retrieve

Each set breaks down into separately downloadable pieces:

• Database {name}, one entry per database in the instance
• Attached files, the Odoo filestore: documents, images, attachments
• Configuration and add-ons
• PostgreSQL roles, the accounts and their rights
• Addon services, if the instance runs any that hold data worth keeping

You take what you need. Fetching only the database to open it on your own machine is a perfectly normal use.

In which formats

Each piece is downloaded exactly as it was captured: a PostgreSQL dump in custom format for a database, a tar archive for the rest. Nothing is repackaged for the occasion, so nothing can be lost in conversion.

These are precisely the formats Hodiploy's import accepts as input. A downloaded backup can therefore be loaded back into another instance with us, and reads with standard PostgreSQL tooling anywhere else.

What happens during the download

The stream goes from the backup storage to your browser without ever landing on our disks. Fetching a 12 GB database therefore doesn't require 12 GB free somewhere on our side, and we keep no copy of what you download.

One visible consequence: your browser shows progress without a total, because the exact size of the stream is only known once it's finished. The size listed before the click stays your reference. On a large piece, leave the tab open until it's done.

Worth knowing

A locked set downloads like any other. The lock prevents replacement and deletion, not reading.

Downloading uses no slot and changes nothing: it's a read, and the instance keeps running normally.

Your code is not in the backup, and doesn't need to be: it lives in your Git repository. The modules in the "Configuration and add-ons" piece are the ones shipped alongside the instance, not your Git history.

Every download is written to the instance's activity log, with the date and the person who asked for it.

And to put a backup back into service?

If your goal is to roll back, don't go through the download: restoring is one click from the same screen, onto the instance itself or into a new instance. See how to restore a backup.

A question?

Unsure which piece to take, or how to read a dump back on your side? Contact us and our team will walk you through it.

Updated on: 24/08/2026