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

Feature: Backup and sync script #110

Open
NathanDeckinga opened this issue Mar 28, 2018 · 3 comments
Open

Feature: Backup and sync script #110

NathanDeckinga opened this issue Mar 28, 2018 · 3 comments
Assignees
Labels
DB Data or database assistance needed question Further information is requested

Comments

@NathanDeckinga
Copy link
Collaborator

We need a way to backup the production database and a way to migrate data from one environment to another.

Things to note:

  • Needs to allow migration outside of AWS/RDS
  • Will only be a full backup (no partials/single tables or incrementals)
  • Will backup a single database at a time (as opposed to the snapshot doing the entire server)
  • Will completely overwrite the destination DB (possible application version mismatch)
  • We should still utilize RDS specific tools for faster backup/restore and other things where it excels

Questions:

  • Does this need to run automatically or just on demand?
  • Do we have space locally on a server to store the backup or write it out to S3?
  • Do we need to store multiple versions or just the latest?
@NathanDeckinga NathanDeckinga added question Further information is requested DB Data or database assistance needed labels Mar 28, 2018
@NathanDeckinga NathanDeckinga self-assigned this Mar 28, 2018
@psineur
Copy link
Contributor

psineur commented Mar 28, 2018

Will only be a full backup (no partials/single tables or incrementals)

As long as it works within 1hr-2hr - it can be full backup.

Will backup a single database at a time (as opposed to the snapshot doing the entire server)

Yes, for manual I would like to be able to pick a DB to backup.

Will completely overwrite the destination DB (possible application version mismatch)

Restore should be a manual thing, with backup right before it to special name/place - just in case restore source is bad.

We should still utilize RDS specific tools for faster backup/restore and other things where it excels

Their snapshots come from the box, just let the thing work and while we're on AWS - let's use it as a first solution to DB management/restoration.

Does this need to run automatically or just on demand?

Both. I would like to see cron to S3 and cron on 2 trusted dev's local machines to their disks.

  • Do we have space locally on a server to store the backup or write it out to S3?

    Lets put it to S3, backing up to same server can cause downtime when it runs out of disk space.

  • Do we need to store multiple versions or just the latest?

    Last 7-14 days. I would prefer 14

@psineur
Copy link
Contributor

psineur commented Apr 5, 2018

I'm thinking about creating a cron script on my mac that will

 backup/dump prod DB to sql, download it to my computer and to some private s3  

and closing this. @NathanDeckinga anything else we need or you want to do? SInce we alrady have RDS backups

@psineur psineur added this to the v.1 - MVP - Public Release milestone Apr 5, 2018
@NathanDeckinga
Copy link
Collaborator Author

It's actually more expensive and slower to go DB -> local then local -> S3. But we should be talking about pennies difference over the month/year and gives us an offsite (your computer) immediately. Go for it.

@psineur psineur assigned psineur and unassigned NathanDeckinga Apr 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DB Data or database assistance needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants