OpenStack Swift incremental backup and restore automation tool for file system, MongoDB, MySQL. LVM snapshot and encryption support.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Hervé Beraud caa84f1218 Stop to use the __future__ module.
The __future__ module [1] was used in this context to ensure compatibility
between python 2 and python 3.

We previously dropped the support of python 2.7 [2] and now we only support
python 3 so we don't need to continue to use this module and the imports
listed below.

Imports commonly used and their related PEPs:
- `division` is related to PEP 238 [3]
- `print_function` is related to PEP 3105 [4]
- `unicode_literals` is related to PEP 3112 [5]
- `with_statement` is related to PEP 343 [6]
- `absolute_import` is related to PEP 328 [7]


Change-Id: Ib9d49da612dc2b5601cff15b1457f71fdbb8669c
3 years ago
devstack Update devstack doc 4 years ago
doc tox: Keeping going with docs 3 years ago
etc Correct errors about freezer-api supporting for V1 and V2 api 5 years ago
freezer Stop to use the __future__ module. 3 years ago
playbooks/legacy/freezer OpenDev Migration Patch 4 years ago
releasenotes Update master for stable/ussuri 3 years ago
.coveragerc Fix freezer for py3 compatibility 7 years ago
.gitignore Update .gitignore 5 years ago
.gitreview OpenDev Migration Patch 4 years ago
.pylintrc Upgrade pylint to a new version that works with python3.7 4 years ago
.stestr.conf Switch to stestr 5 years ago
.zuul.yaml Add Python3 victoria unit tests 3 years ago
CREDITS.rst Adding the freezer logo to the README 7 years ago
FAQ.rst Fix description for backup management 6 years ago
HACKING.rst Clean up docs and specs directories 5 years ago
LICENSE Import pep3134daemon as local module 8 years ago
README.rst Update api-ref location 4 years ago
bindep.txt Use bindep to define binary deps 6 years ago
freezer_logo.jpg Adding the freezer logo to the README 7 years ago
lower-constraints.txt Update to hacking 3.0 3 years ago
requirements.txt Remove six usage from freezer package 3 years ago
setup.cfg [ussuri][goal] Drop python 2.7 support and testing 4 years ago Updated from global requirements 6 years ago
test-requirements.txt Update to hacking 3.0 3 years ago
tox.ini Update to hacking 3.0 3 years ago


Team and repository tags


OpenStack Freezer


Freezer is a Backup Restore DR as a Service platform that helps you to automate the data backup and restore process.

The following features are available:

  • Backup file system using point-in-time snapshot
  • Strong encryption supported: AES-256-CFB
  • Backup file system tree directly (without volume snapshot)
  • Backup journalled MongoDB directory tree using lvm snapshot to Swift
  • Backup MySQL with lvm snapshot
  • Restore data from a specific date automatically to file system
  • Low storage consumption as the backup are uploaded as a stream
  • Flexible backup policy (incremental and differential)
  • Data is archived in GNU Tar format for file based incremental
  • Multiple compression algorithm support (zlib, bzip2, xz)
  • Remove old backup automatically according to the provided parameters
  • Multiple storage media support (Swift, local file system, or ssh)
  • Flush kernel buffered memory to disk
  • Multi-platform (Linux, Windows, *BSD, OSX)
  • Manage multiple jobs (I.e., multiple backups on the same node)
  • Synchronize backups and restore on multiple nodes
  • Web user interface integrated with OpenStack Horizon
  • Execute scripts/commands before or after a job execution
  • More ...

To learn how to use Freezer's API, consult the documentation available online at:

Freezer Disaster Recovery: - Freezer DR

Freezer Horizon plugin: - Freezer Web UI

For more information on OpenStack APIs, SDKs and CLIs in general, refer to:


To learn how to deploy and configure OpenStack Freezer, consult the documentation available online at:

In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:


When errors occure, these are good places to check:

  • freezer-api log: $HOME/log/freezer-api.log


  • freezer-agent log: $HOME/.freezer/freezer.log
  • freezer-scheduler log:/var/log/freezer/scheduler.log


Any new code must follow the development guidelines detailed in the HACKING.rst file and OpenStack general development guidelines, and pass all unit tests.

Further developer focused documentation is available at:

Contributors are encouraged to join IRC (#openstack-freezer on freenode):

Other Information

Release notes for the project can be found at:

During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for freezer can be found at: