Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PBM-1450 Added a note how node priorities interfere with incrementalb… #233

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nastena1606
Copy link
Collaborator

…ackup scheduling

modified: docs/features/incremental-backup.md
modified: docs/usage/start-backup.md

…ackup scheduling

modified:   docs/features/incremental-backup.md
	modified:   docs/usage/start-backup.md
If the node with the base incremental backup is down or unavailable, you must start the incremental backup chain anew on another node.
If the node with the base incremental backup is down or unavailable, you must start the incremental backup chain anew on another node.

2. Adjusting node priorities for backup interferes with the default behaviour described above. If only a subset of nodes is listed for the priority, the remaining nodes receive the default priority 1 and it may happen that the incremental backup is taken not from the node where the base backup was taken.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would describe the possible solution how to overcome that. Something like:

Therefore, it is advisable to put the highest backup priority on each node, where it is preferable to take incremental backup. By doing that, Percona Backup for MongoDB will try to start the incremental backup always on the same node, and incremental backup chain will be preserved. In the case of a sharded cluster, it's necessary to do that for each replica set within the cluster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants