You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Write support for fuse data (mount support directly from backup)
Encryption
Compression
Encryption-version migration
Re-keying
Performance >350MB/s on recent CPUs with compression and encryption
Recommendation NOT to use sqlite anymore
Documentation update to reflect changes
Better tag handling on backup, esp. on continue.
Added minio s3 client library for better s3 performance than boto3
Added "continue" feature both for backup and restore
Show throughput in stats, not write performance.
Improved performance on s3. However, boto3 seems to be the bottleneck
here. We only get ~120MB/s to s3. Hints welcome.
Upgrade to boto3
Better stats
Nicer output for restore
Reducing memory on backup and restore at least by about -90%
Rewrote backup function
Backup is now skipping "preparing version" and thus WAY faster
Backy2 can now handle ~1.5GB throughput w/ backups on my notebook
Restore is way faster
Deduplication on/off can now be toggled in cfg (if performance is more
important than space).
null data backend and null io for testing performance (you can now backup
to a null target and restore from a null target).
IO writer (for restore) is now multithreaded, therefore there's now
simulatious_writes in the config for the IOs.
Way better output during backup, restore and scrub, also throttleded to
max 1/s, added ETA, added throughput and added the queuelengths for
better understanding the bottlenecks.
Using system rbd/rados python libs if available in the hope of better
performance and compatibility.
Added a warning when using the old backy2-builtin rbd and rados libs