Created new method to add a node to a cluster from a backup #271
Conversation
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
…rest backup Signed-off-by: Paul Rothrock <[email protected]>
|
Closing this PR - the idea was incorporated into the add-node command, which now supports the described workflow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds the command
add-node-from-backupto cluster.py. To use this, first create a pgBackrest backup on the source server and copy it to the same path on the destination server using scp or rsync or a homing pigeon.Then, add the node to the cluster with this command on the source node or a controller machine:
This has been tested with full and incremental backups. If there have been changes to the data during the restore you may need to increase WAL log retention so the new node can get caught up.