Upgrade from 2.5.x¶
The following settings are now useless, you can remove them:
DBBACKUP_BACKUP_ENVIRONMENT: Must be set in
DBBACKUP_RESTORE_ENVIRONMENT: Same than
DBBACKUP_BACKUP_DIRECTORY: Was used by Filesystem storage, use
DBBACKUP_SQLITE_BACKUP_COMMANDS: Was used by SQLite database, use
DBBACKUP_SQLITE_RESTORE_COMMANDS: Same than
DBBACKUP_MYSQL_BACKUP_COMMANDS: Same than
SQLITE_BACKUP_COMMANDSbut for MySQL
DBBACKUP_MYSQL_RESTORE_COMMANDS: Same than
MYSQL_BACKUP_COMMANDSbut for PostgreSQL
DBBACKUP_POSTGRESQL_RESTORE_COMMANDS: Same than
DBBACKUP_POSTGRESQL_BACKUP_COMMANDS: Was used for activate PostGIS, use
PgDumpGisConnectorconnector for enable this option
DBBACKUP_POSTGRESQL_RESTORE_SINGLE_TRANSACTION: Must be set in
--backup-extension has been removed, DBBackup should automaticaly
know the appropriate file.
Listing from this command,
--list, has been removed in favor of
--no-compress option has been replaced by
for keep consistency with other commands.
Now this command can backup remote storage, not only filesystem’s
You are now able to restore your media files backups. Unfortunately you’ll not be able to restore old backup files.
We made a total refactoring of DBCommands system. It is now easier to use, configure and implement a custom one.
All database configuration for backups are defined in settings
DBBACKUP_CONNECTORS. By default, the
parameters are used but can be overrided in this new constant.
This dictionnary stores configuration about how backups are made,
what is the path of backup command (
/bin/mysqldump), add suffix or prefix
to the command line, environment variable, etc.
The system stay pretty simple and can detect alone how to backup your DB. If it can’t just submit us what is your Django DB Engine and we’ll try to fix it.
Previously backup was made by copy the database file, now you have the choice between make a raw snaphot or make a real SQL dump. It can be useful to exclude tables or don’t overwrite data.
If you want to restore your old backups choose
All storage engines has been removed from DBBackup except the basic. Now this object will use Django storages as driver.
settings.DBBACKUP_STORAGE must now be a full path to a Django storage, for
settings.DBBACKUP_STORAGE_OPTIONS hold its function of gather storage’s
If you was using a removed storage backend, don’t worry, we ensure you’ll have a solution by test and write equivalent in Django-Storages.