Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

Review and document backup policies #470

Closed
chadwhitacre opened this issue Jan 14, 2016 · 6 comments
Closed

Review and document backup policies #470

chadwhitacre opened this issue Jan 14, 2016 · 6 comments

Comments

@chadwhitacre
Copy link
Contributor

Reticketed from #468.

My current practice is to store the backups taken during payday on an external hard drive.

What else do we have going on? What should we do?

@chadwhitacre
Copy link
Contributor Author

We are getting daily backups in Heroku (docs).

$ heroku pg:backups schedules
=== Backup Schedules
DATABASE_URL: daily at 4:00 (UTC)
$

@chadwhitacre
Copy link
Contributor Author

Morgan Stanley To Pay $1M SEC Fine For Security Lapse: A Morgan Stanley employee copied customer data to his personal laptop, which was subsequently hacked, resulting in the SEC fine for failing to protect customer data.

https://summitroute.com/blog/2016/06/12/downclimb/

@kaguillera
Copy link
Contributor

😱

@chadwhitacre
Copy link
Contributor Author

Folding in from #932:

We take a nightly backup at Heroku. I do think we should have an offsite backup, at least at a different provider. I don't think we want backups on three different personal laptops, though. That is sloppy.

What should we do, @clone1018 @rohitpaulk?


I think me and @rohitpaulk 's backups are on DigitalOcean (that's where I run payday). I'm used to storing backups on S3 with the file encrypted. Not sure if that would be easy for us or not


Heroku wraps AWS so that wouldn't do much for us. DO could work but we should be more intentional about it.

@chadwhitacre chadwhitacre mentioned this issue Dec 1, 2016
15 tasks
@chadwhitacre chadwhitacre changed the title review and document backup policies Review and document backup policies Dec 2, 2016
@chadwhitacre
Copy link
Contributor Author

Slack re: db size after removing readmes: still big, but ...

@chadwhitacre
Copy link
Contributor Author

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants