mirror
/
borg
mirror of https://github.com/borgbackup/borg.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Merge pull request #3341 from milkey-mouse/break-lock-interrupt-bp1.1 

Mention break-lock in checkpointing FAQ entry (1.1 backport)
This commit is contained in:
TW 2017-11-20 23:19:23 +01:00 committed by GitHub
parent 0f59e53554 fda9b7d5b9
commit 96b6033f29
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/faq.rst
View File

@ -132,10 +132,11 @@ completed is useful because it references all the transmitted chunks up
to the checkpoint. This means that in case of an interruption, you only need to to the checkpoint. This means that in case of an interruption, you only need to
retransfer the data since the last checkpoint. retransfer the data since the last checkpoint.
If a backup was interrupted, you do not need to do any special considerations, If a backup was interrupted, you normally do not need to do anything special,
just invoke ``borg create`` as you always do. You may use the same archive name just invoke ``borg create`` as you always do. If the repository is still locked,
as in previous attempt or a different one (e.g. if you always include the current you may need to run ``borg break-lock`` before the next backup. You may use the
datetime), it does not matter. same archive name as in previous attempt or a different one (e.g. if you always
include the current datetime), it does not matter.
|project_name| always does full single-pass backups, so it will start again |project_name| always does full single-pass backups, so it will start again
from the beginning - but it will be much faster, because some of the data was from the beginning - but it will be much faster, because some of the data was