Skip to content
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.

Implement backup strategy #3

Open
apertureless opened this issue Sep 15, 2017 · 2 comments
Open

Implement backup strategy #3

apertureless opened this issue Sep 15, 2017 · 2 comments

Comments

@apertureless
Copy link
Member

Need backups for production.
oLhqrwT7jwMtG

@apertureless
Copy link
Member Author

apertureless commented Sep 18, 2017

Backup

Docker Volumes

  • mailtrain-node-data:/app/public/grapejs/uploads
  • mailtrain-node-data:/app/public/mosaico/uploads
  • mailtrain-node-reports:/app/protected/reports
  • mailtrain-node-config:/app/config

https://stackoverflow.com/questions/38298645/how-should-i-backup-restore-docker-named-volumes

SQL

  • docker exec CONTAINER mysqldump -u root --password=root DATABASE > backup.sql

S3

Dump files into tar and upload to s3 automated. 🤖

@apertureless
Copy link
Member Author

Maybe switch the volume driver to s3 storage driver 🤔
https://docs.docker.com/registry/storage-drivers/s3/

@grihn @tpmo

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

No branches or pull requests

1 participant