Freezer rsync incremental engine
Bases: BackupEngine
Execute backup using rsync algorithm.
If an existing rsync meta data for file is available - the backup will be incremental, otherwise will be executed a level 0 backup.
backup_path – Path to backup
manifest_path – Path to backup metadata
Compute the file or fs tree path signatures.
Return blocks of changed data.
fs_path –
manifest_path –
write_queue –
str
Engine name
Restore the provided backup into restore_abs_path.
Decrypt backup content if encrypted. Freezer rsync header data structure:
[ {
'path': '' (path to file),
'inode': {
'mode': st_mode,
'dev': st_dev,
'uname': username,
'gname': groupname,
'atime': st_atime,
'mtime': st_mtime,
'size': st_size
} (optional if file removed),
'lname': 'link_name' (optional if symlink),
'prev_name': '' (optional if renamed),
'new_level': True (optional if incremental),
'deleted': True (optional if removed),
'deltas': len_of_blocks, [modified blocks] (if patch)
},
...
]
restore_path – Path where to restore file(s)
read_pipe – ackup data
backup – Backup info
except_queue – Queue for exceptions
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.