Closed Bug 1158643 Opened 10 years ago Closed 9 years ago

Create a backup / restore strategy for consul

Categories

(Socorro :: Infra, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jschneider, Unassigned)

References

Details

When we launched our new stage env, there's a bit of manual ssh-in process required to get the nodes to a functional state. We should minimize that as much as possible. Some ideas include 2 way syncs to S3 techops bucket, occasional AMI snapshots which update the consul sg.
Blocks: 1118288
I think the easy thing would be: 1) on a regular basis (hourly? nightly?) run "consulate kv backup backup-${DATE}.json" 2) copy to S3 - "aws s3 cp backup-${DATE}.json s3://some-backup-bucket/consul/" This would require allowing the consul servers to write to a backup bucket.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.