mirror of
https://github.com/rustic-rs/rustic.git
synced 2025-10-26 11:18:51 +00:00
rustic - fast, encrypted, and deduplicated backups powered by Rust
| .github/workflows | ||
| changelog | ||
| screenshots | ||
| src | ||
| Cargo.lock | ||
| Cargo.toml | ||
| FAQ.md | ||
| README.md | ||
rustic - fast, encrypted, deduplicated backups powered by pure Rust
Rustic is a backup tool that provides fast, encrypted, deduplicated backups. It reads and writes the restic repo format desribed in the design document and can therefore be used as a complete replacement for restic.
Note that rustic currently is in an beta release and misses tests. It is not yet considered to be ready for use in a production environment.
Have a question?
Look at the FAQ or open an issue!
Comparison with restic:
Improvements:
- Allows using cold storage (e.g. AWS Glacier) repos which are only read in the
restorecommand - Completely lock-free pruning; option
instant-deleteis available - Huge decrease in memory requirement
- pack size can be customized
- Already much faster than restic for most operations (but not yet fully speed optimized)
backupcommand can use.gitignorefiles- Snapshots save much more information
- Allows to save some options in the config file via the command
config - New command
repo-info snapshots latestcommand to show only the latest snapshot(s)checkcommand checks and uses cache; option--trust-cacheis available- option
prune --fast-repackfor faster repacking cat treecommand accepts a snapshot and path to cat the tree blob- compression is already supported in released versions ;-)
Current limitations:
- Backup source and restore destinations only on local file system
- Runs so far only on Linux and MacOS, Windows support is WIP
Open points:
- Add tests and benchmarks
- Add more backup-sources and restore-destinations
- Add missing commands: copy, dump, find, mount
- Improve error handling
- Parallelize the code even more and optimize for speed where useful
License
Licensed under either of:
at your option.
Contribution
Contributions in form of issues or PRs are very welcome.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.