mirrors/rustic
2
0
Fork 0
mirror of https://github.com/rustic-rs/rustic.git synced 2025-10-26 11:18:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #109 from rustic-rs/docu-prune

Browse Source 
Add more info about two-phase pruning
This commit is contained in:
aawsome 2022-08-07 20:43:16 +02:00 committed by GitHub
commit f25f168b91
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
FAQ.md
View File

@ -30,6 +30,17 @@ Packs which are marked for removal are checked if they are really not needed and
long enough ago. Depending on these checks they are either finally removed, recovered or kept in the
state of being marked for removal.
This two-phase deletion is needed for rustic to work lock-free: If a `backup` runs parallel to a `prune`
run (or `forget --prune`), it could be that prune decides that some blobs can be removed, but the parallel
backup uses these blobs for the newly generated snapshot.
The time to hold marked packs should be long enough to guarantee that a possibly parallel backup run has
finished in between. It can be set by the `--keep-delete` option and defaults to 23 hours. In any case, packs
will be kept marked and only deleted by the next prune run.
Note that there is the option `--instant-delete` which circumvents this two-phase deletion. Only use this
option, if you **REALLY KNOW** that there is no parallel access to your repo, else you risk loosing data!
## You said "rustic uses less resources than restic" but I'm observing the opposite...
In general rustic uses less resources, but there may be some exceptions. For instance the crypto libraries
of Rust and golang both have optimizations for some CPUs. But it might be that your CPU benefits from a