Infrastructure should be boring, right? That doesn’t mean that developing tools for said infra can’t be exciting. In one area I believe there’s room for improvement: backing up (and restoring) critical infra service.
To provide some context: I’m talking about cloud native infrastructure, that is, distributed systems that typically manage containers of some sort. What all of those distributed systems have in common is some distributed infrastructure component we use to store state critical to its operation: configuration, metadata about leaders or workers, and so forth:
In any case, you might find yourself sometimes in a situation where you want to take a snapshot of the content of the infra service, be it to debug it or to keep a backup of a healthy state. This was the motivation to start work on a tool that I called burry, for BackUp & RecoveRY tool:
In a nutshell, burry lets you, at time of writing, take a snapshot of the content of ZooKeeper & etcd and then you can:
burry --endpoint localhost:2181
burry --endpoint etcd.mesos:1026 --isvc etcd --target local
--target s3--credentials play.minio.io:9000,AWS_ACCESS_KEY_ID=Q3AM3UQ867SPQQA43P2F,AWS_SECRET_ACCESS_KEY=zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG
Note: currently, you can use Amazon S3 and Minio as remote storage systems.
I’m currently working on Azure and Google storage support as well as restoring the state (that’s the recovery part ;).
What would you like to see, next? Please let me know, either here or by raising an issue on GitHub.
Create your free account to unlock your custom reading experience.