docs: add warning about job-intermixing#506
Merged
arogge merged 1 commit intobareos:masterfrom May 8, 2020
Merged
Conversation
franku
approved these changes
May 7, 2020
Contributor
franku
left a comment
There was a problem hiding this comment.
I have some rewording suggestions. Otherwise looks good. Thanks! :-)
| .. warning:: | ||
|
|
||
| Bareos uses only :config:option:`dir/job/Client` and :config:option:`dir/job/Fileset` to determine which jobids belong together. | ||
| If job A and B have the same client and fileset defined, the resulting jobids will be intermixed: |
Contributor
There was a problem hiding this comment.
Suggested change
| If job A and B have the same client and fileset defined, the resulting jobids will be intermixed: | |
| If job A and B have the same client and fileset defined, the resulting jobids will be intermixed as follows: |
|
|
||
| Bareos uses only :config:option:`dir/job/Client` and :config:option:`dir/job/Fileset` to determine which jobids belong together. | ||
| If job A and B have the same client and fileset defined, the resulting jobids will be intermixed: | ||
| When a job determines its predecessor to determine its required level and since-time, it will consider all jobs with the same client and fileset. |
Contributor
There was a problem hiding this comment.
Suggested change
| When a job determines its predecessor to determine its required level and since-time, it will consider all jobs with the same client and fileset. | |
| I) When a job determines its predecessor to determine its required level and since-time, it will consider all jobs with the same client and fileset. |
Member
Author
There was a problem hiding this comment.
I'm not sure this will be formatted in a way I like, but I'll try it.
| Bareos uses only :config:option:`dir/job/Client` and :config:option:`dir/job/Fileset` to determine which jobids belong together. | ||
| If job A and B have the same client and fileset defined, the resulting jobids will be intermixed: | ||
| When a job determines its predecessor to determine its required level and since-time, it will consider all jobs with the same client and fileset. | ||
| Likewise when restoring a client you select the fileset and all jobs that used that fileset will be considered. |
Contributor
There was a problem hiding this comment.
Suggested change
| Likewise when restoring a client you select the fileset and all jobs that used that fileset will be considered. | |
| II) When restoring a client you have to select the fileset and all jobs that used the regarding fileset will be considered. |
| If job A and B have the same client and fileset defined, the resulting jobids will be intermixed: | ||
| When a job determines its predecessor to determine its required level and since-time, it will consider all jobs with the same client and fileset. | ||
| Likewise when restoring a client you select the fileset and all jobs that used that fileset will be considered. | ||
| If you want separate backups, you have to duplicate your filesets with a different name and the same content. |
Contributor
There was a problem hiding this comment.
Suggested change
| If you want separate backups, you have to duplicate your filesets with a different name and the same content. | |
| As a matter of fact, if you want separate backups, you have to duplicate your filesets with a different name and the same content. |
frb121
reviewed
May 8, 2020
frb121
reviewed
May 8, 2020
The intermixing of jobs with the same client and fileset is considered counter-intuitive by some users. This patch adds a warning to the documentation that clarifies the situation.
a6dd386 to
60042d6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The intermixing of jobs with the same client and fileset is considered counter-intuitive by some users.
This patch adds a warning to the documentation that clarifies the situation.
(User-Story 3403)