freezer.engine.engine.
BackupEngine
(storage)¶Bases: object
The main part of making a backup and making a restore is the mechanism of implementing it. For a long time Freezer had only one mechanism of doing it - invoking gnutar and it was heavy hard-coded.
Currently we are going to support many different approaches. One of them is rsync. Having many different implementations requires to have an abstraction level
This class is an abstraction over all implementations.
Workflow:
backup
(backup_resource, hostname_backup_name, no_incremental, max_level, always_level, restart_always_level, queue_size=2)¶Here we now location of all interesting artifacts like metadata Should return stream for storing data. :return: stream
backup_data
(backup_path, manifest_path)¶Parameters: |
|
---|---|
Returns: |
backup_stream
(backup_resource, rich_queue, manifest_path)¶Parameters: |
|
---|---|
Returns: |
metadata
(backup_resource)¶name
¶Return type: | str |
---|---|
Returns: | Engine name |
read_blocks
(backup, write_pipe, read_pipe, except_queue)¶restore
(hostname_backup_name, restore_resource, overwrite, recent_to_date, backup_media=None)¶Parameters: |
|
---|
restore_level
(restore_path, read_pipe, backup, except_queue)¶Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.