-
Notifications
You must be signed in to change notification settings - Fork 16
restore
Sébastien Andreatta edited this page Apr 27, 2026
·
2 revisions

Restore a dump file on the local filesystem to a database. This will effectively replace all data in the target database.
odev restore [-v {CRITICAL,ERROR,WARNING,INFO,DEBUG,DEBUG_SQL,NOTSET}] [-h] [-f] [-p {local}] [-b BRANCH] [--no-neutralize] database backupNo aliases
| Argument | Description |
|---|---|
database |
The database to target. |
backup |
Path to the backup file to restore. |
| Argument | Description |
|---|---|
-v, --log-level |
Set logging verbosity for the execution of odev. |
-h, --help |
Show help for the current command. |
-f, --force |
Bypass confirmation prompts and assume a default value to all, use with caution! |
-p, --platform |
Force searching for the database on the specified platform, useful when different databases have the same name on different hosting (usually one local database being a copy of a remote one). One of local. |
-b, --branch |
The branch to target, only used with PaaS (Odoo SH) databases to force using a specific branch after project detection. |
--no-neutralize |
Do not neutralize the database after the dump has been restored. Only used on local databases. |
odev restore --helpodev restore demo_new /path/to/backup.zipodev restore --no-neutralize demo_new /path/to/backup.zipodev restore -f demo_existing /path/to/backup.zip