feat: add support to backup nomad raft snapshot to s3 #25
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
If a `nomad_raft_backup_bucket` is defined, this adds a script that runs at midnight and 12PM to backup Nomad RAFT snapshot to the S3 bucket. The script will be present on all servers, but will only run on the leader. The cron is run using systemd-timer. The snapshot is timestamped and namespaced to a folder by `cluster_name`, so multiple snapshots from different clusters can use the same bucket. There was also an issue with the file limit check which got autocorrected by shellcheck, so a fix for that is included here as well. Signed-off-by: Chinmay D. Pai <[email protected]>
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.
If a
nomad_raft_backup_bucketis defined, this adds a script that runs at midnight and 12PM to backup Nomad RAFT snapshot to the S3 bucket. The script will be present on all servers, but will only run on the leader.cluster_name, so multiple snapshots from different clusters can use the same bucket.NOTE: There was also an issue with the file limit check which got autocorrected by shellcheck, so a fix for that is included here as well.