Docker backup allows saving a configuration, status and data from a Docker container. To allow Docker backup data from container, users may implement a special utility that manages “cold” Docker backup and makes an archive containing a consistent Docker backup image.
The utility for Docker backup is a part of Docker software. To run a backup procedure, you must commit a current state of a particular Docked container using its internal commands.
# docker commit -p [container_id] [container_file]
Here container_id is an alphanumeric code of a particular container (which you can obtain by running the docker ps operation), and a container_name is a name for a storage where Docker will save a snapshot of your container in its current state.
To restore Docker, just run a command
# docker load -i [container_file]
Here container_file is a name of an archive that contains Docker auto backup.
It is not a simple and straight task to make Docker backup externally. For example, with Handy Backup you can only operate with a Docker backup script and a resulting container image, to provide such things as Docker backup to S3, joint Docker and MySQL backup and so on.
Caveat: As Docker backup is a complex task, you cannot just take a snapshot for it, as for OpenVZ backup use case!
If you are interested at implementing Docker backup best practices into Handy Backup, do not hesitate to write us a letter into sales@handybackup.net to describe your needs and opinions. We will be glad to make a Docker backup system for you, much like VMware or Hyper-V backup!
Learn more: