You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be a shame if something went wrong and we lost the record of applications. We should have a way to back up the DB.
I would consider using pg_dump to get the entire database (daily? weekly?), compress the database dump (it's text so it'll compress well), and store it in S3. We can keep all of the DB dumps on S3 with their dates in the file name so we have regular snapshots - that way if something went wrong several weeks ago and we caught it later, we can revert to the last good state.
The text was updated successfully, but these errors were encountered:
skorasaurus
changed the title
Create a backup process for database
Create a backup process for database submissions
Apr 7, 2018
You could create a cron job with the pg dump command and copy the contents of the output to s3.
You can run this cron job at what ever schedule you want.
It would be a shame if something went wrong and we lost the record of applications. We should have a way to back up the DB.
I would consider using pg_dump to get the entire database (daily? weekly?), compress the database dump (it's text so it'll compress well), and store it in S3. We can keep all of the DB dumps on S3 with their dates in the file name so we have regular snapshots - that way if something went wrong several weeks ago and we caught it later, we can revert to the last good state.
The text was updated successfully, but these errors were encountered: