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

Regularly test that backup works #494

Open
jonathan-s opened this issue Mar 8, 2019 · 3 comments
Open

Regularly test that backup works #494

jonathan-s opened this issue Mar 8, 2019 · 3 comments
Labels
chore Stuff that needs doing but doesn't cause any user-facing changes

Comments

@jonathan-s
Copy link
Collaborator

So we're making backups. Though we don't know for sure if these backups work :). So I'm suggesting that there would be some kind of cron job or similar that would pull the latest backup and restore that backup on staging.

We'd have an up to date staging and we'd know that backups work for sure.

@bfirsh
Copy link
Member

bfirsh commented Mar 8, 2019

yessss +100

@bfirsh bfirsh added the chore Stuff that needs doing but doesn't cause any user-facing changes label Mar 8, 2019
@bfirsh
Copy link
Member

bfirsh commented Mar 8, 2019

S3 bucket too.

@bfirsh
Copy link
Member

bfirsh commented Mar 8, 2019

This would be nice feature for https://github.com/bfirsh/heroku-tarsnap-backups in fact - a script to automatically regularly restore the backups to a staging app. The restore app could be attached as RESTORE_DATABASE and RESTORE_BUCKETEER or whatever.

Having as part of the sidecar app also means we don't have to add the tarsnap key to the main app's config (one of the reason I did a sidecar app in the first place).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Stuff that needs doing but doesn't cause any user-facing changes
Projects
None yet
Development

No branches or pull requests

2 participants