summaryrefslogtreecommitdiff
path: root/manual/en
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2014-08-07 08:48:04 +0100
committerLars Wirzenius <liw@liw.fi>2014-08-07 08:48:04 +0100
commit7adb3ca0efc77e77f6fe8786a4d4f44d02b7c914 (patch)
tree6ba47beed4b7db867b33fc6a32c83a3d396614e2 /manual/en
parentdb42f0646a7a49b6c86e85e70dc8b0e2ab16c0b6 (diff)
downloadobnam-7adb3ca0efc77e77f6fe8786a4d4f44d02b7c914.tar.gz
Improve wording on checkpoints and restarts
Thanks, Jan Niggemann.
Diffstat (limited to 'manual/en')
-rw-r--r--manual/en/060-backing-up.mdwn12
1 files changed, 6 insertions, 6 deletions
diff --git a/manual/en/060-backing-up.mdwn b/manual/en/060-backing-up.mdwn
index e04f5a89..d7611d98 100644
--- a/manual/en/060-backing-up.mdwn
+++ b/manual/en/060-backing-up.mdwn
@@ -182,12 +182,12 @@ for it to happen. See the `--checkpoint` setting for choosing how
often the checkpoints should happen.
Note that if Obnam doesn't get to finish, and you have to re-start it,
-it starts over from the beginning. The checkpoint generation does not
-contain enough state for Obnam to start backing up from the latest
-file in the checkpoint: it'd be very complicated state, and easily
-invalidated by filesystem changes. Instead, Obnam scans all files, but
-since the checkpoint was made, most files will hopefully not have
-changed since, so the scanning should be relatively fast.
+the scanning starts over from the beginning. The checkpoint generation
+does not contain enough state for Obnam to continue scanning from the
+latest file in the checkpoint: it'd be very complicated state, and
+easily invalidated by filesystem changes. Instead, Obnam scans all
+files, but most files will hopefully not have changed since the
+checkpoint was made, so the scanning should be relatively fast.
The only problem with the patient option is that your most precious
data doesn't get backed up while all your large, but less precious