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

Automatic (and optional) backup for service/databases data #35

Open
pdonorio opened this issue Aug 4, 2016 · 2 comments
Open

Automatic (and optional) backup for service/databases data #35

pdonorio opened this issue Aug 4, 2016 · 2 comments

Comments

@pdonorio
Copy link
Owner

pdonorio commented Aug 4, 2016

We should provide for each service the command to backup and restore data, either it's the entire data dir or a specific tool provided by the service itself.

We should discuss here how to make this possible.

@pdonorio
Copy link
Owner Author

pdonorio commented Aug 4, 2016

For instance we can write a celery worker for each service backup command. The worker should be a container started with the right "volumes-from" option set.
Then the docker-compose command (or via do.py?) could be called inside the host cron, writing a few lines of documentation or providing examples (e.g. once a day).

The do.py is the most powerful option, which could also cycle on a list of workers that can make the backup (e.g. files inside a vanilla/backup_scripts) to execute them all.

One requirement for this drafted solution is that redis/celery should be running, and do.py can check that.

@pdonorio
Copy link
Owner Author

pdonorio commented Aug 4, 2016

We may keep also trace here of a list of instructions for backups to be implemented with workers:

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

No branches or pull requests

1 participant