Skip to content

Commit

Permalink
docs: corrected some wording
Browse files Browse the repository at this point in the history
  • Loading branch information
Zephyr82 authored and fbergkemper committed Apr 27, 2021
1 parent cce3267 commit c5f6165
Showing 1 changed file with 3 additions and 3 deletions.
Expand Up @@ -297,7 +297,7 @@ The basic always incremental scheme

The basic always incremental scheme does an incremental backup from the client daily which is relatively small and as such is very good.

During the consolidation, each day the full backup is consolidated with the oldest incremental backup, which means that more or less the full amount of data being stored on the client is moved. Although this consolidation only is performed locally on the storage daemon without client interaction, it is still an enormous amount of data being touched and can take an considerable amount of time.
During the consolidation, each day the full backup is consolidated with the oldest incremental backup, which means that more or less the full amount of data being stored on the client is moved. Although this consolidation only is performed locally on the storage daemon without client interaction, it is still an enormous amount of data being touched and can take a considerable amount of time.

If all clients use the "always incremental" backup scheme, this means that the complete data being stored in the backup system needs to be moved every day!

Expand All @@ -307,7 +307,7 @@ The following figure shows the Data Volume being moved during the normal always

- The red bar shows the amount of the first full backup being copied from the client.

- The blue bars show the amount of the daily incremental backups. They are so little that the can be barely seen.
- The blue bars show the amount of the daily incremental backups. They are so little that the can barely be seen.

- The green bars show the amount of data being moved every day during the consolidation jobs.

Expand Down Expand Up @@ -403,7 +403,7 @@ What is missing in the always incremental backup scheme in comparison to the tra

When using always incremental, the usual maximum age of data stored during the backup cycle is :config:option:`dir/job/AlwaysIncrementalJobRetention`\ .

Usually, it is desired to be able to store a certain backup for a longer time, e.g. monthly a backup should be kept for half a year.
Usually, it is desired to be able to store a certain backup for a longer time, e.g. a monthly backup should be kept for half a year.

There are two options to achieve this goal.

Expand Down

0 comments on commit c5f6165

Please sign in to comment.