{"id":3910,"date":"2023-04-03T05:00:46","date_gmt":"2023-04-03T05:00:46","guid":{"rendered":"https:\/\/blog.osmosys.co\/?p=3910"},"modified":"2024-02-09T06:10:11","modified_gmt":"2024-02-09T06:10:11","slug":"backup-and-restore-of-docker-volumes-a-step-by-step-guide","status":"publish","type":"post","link":"https:\/\/osmosys.co\/uk\/backup-and-restore-of-docker-volumes-a-step-by-step-guide\/","title":{"rendered":"Backup and Restore of Docker Volumes: A Step-by-Step Guide"},"content":{"rendered":"
<\/div>\n

<\/p>\n\n\n\n

As more and more developers turn to Docker to streamline their development processes, it becomes increasingly important to understand how to take backup and restore a volume in Docker. In this article, we’ll explore the pain areas around volume backup and restoration, the reasons for doing it, and provide a comprehensive solution that will help you take backup and restore volumes with ease.<\/p>\n\n\n\n

<\/a><\/h2>\n\n\n\n

What?<\/strong><\/h2>\n\n\n\n

Docker has become an essential tool for many developers in recent years, allowing them to create and manage containerized applications with ease. One of the most significant advantages of Docker is its ability to manage data volumes, allowing you to store data that persists beyond the lifetime of a container.<\/p>\n\n\n\n

However, even with its many benefits, Docker’s volume management can sometimes be challenging. In particular, taking backups and restoring volumes can be a complex and error-prone process. In this article, we’ll explore why you might need to take backups of your volumes and how to do it correctly.<\/p>\n\n\n\n

<\/a><\/h2>\n\n\n\n

Why?<\/strong><\/h2>\n\n\n\n

There are many compelling reasons to do so. Here are a few reasons why you might need to take backups of your Docker volumes:<\/p>\n\n\n\n

<\/a><\/h3>\n\n\n\n

Disaster Recovery<\/strong><\/h3>\n\n\n\n

The most obvious reason to take backups of your Docker volumes is to protect against data loss in the event of a disaster. By taking regular backups of your volumes, you can ensure that your critical data is safe and recoverable in case of an emergency.<\/p>\n\n\n\n

<\/a><\/h3>\n\n\n\n

Testing and Development<\/strong><\/h3>\n\n\n\n

Another reason to take backups of your Docker volumes is for testing and development purposes. By creating backups of your volumes at different stages of the development process, you can easily roll back to a previous state if you encounter problems or need to test new features.<\/p>\n\n\n\n

<\/a><\/h3>\n\n\n\n

Replication<\/strong><\/h3>\n\n\n\n

Taking backups of your Docker volumes can also be useful for replicating data across multiple environments. By creating backups of your volumes and restoring them in other environments, you can ensure that your data is consistent across all of your development, staging, and production environments.<\/p>\n\n\n\n

<\/a><\/h2>\n\n\n\n

How?<\/strong><\/h2>\n\n\n\n

Now that we’ve explored the pain areas and reasons for taking backups and restoring volumes in Docker, let’s take a look at how to do it correctly. Here are the steps you should follow to take backups of your volumes:<\/p>\n\n\n\n

<\/a><\/h3>\n\n\n\n

Step 1: Identify the Volume<\/strong><\/h3>\n\n\n\n

The first step in taking a backup of a volume is to identify the volume that you want to back up. You can do this by running the following command:<\/p>\n\n\n\n

docker volume ls<\/code><\/pre>\n\n\n\n
This will show you a list of all the volumes that are currently available on your Docker host. Note down the name of the volume that you want to back up.<\/p>\n\n\n\n
<\/a><\/h3>\n\n\n\n
Step 2: Create a Backup<\/strong><\/h3>\n\n\n\n
To create a backup of the volume, you can use the docker run<\/code> command to start a container that mounts the volume you want to back up and a separate container that writes the backup data to a file.<\/p>\n\n\n\n
Here’s an example of how to do this:<\/p>\n\n\n\n
docker run --rm \\\n--mount source=<volume-name>,target=<target> \\\n-v $(pwd):\/backup \\\nbusybox \\\ntar -czvf \/backup\/<backup-filename>.tar.gz <target><\/code><\/pre>\n\n\n\n
In this command, replace <volume-name><\/code> with the name of the volume you want to back up, <target><\/code> with the mount point inside the docker container, and <backup-filename><\/code> with a name for the backup file.<\/p>\n\n\n\n
<\/a><\/h3>\n\n\n\n
Step 3: Move the Backup File to an External Server<\/strong><\/h3>\n\n\n\n
After you have created a backup file, it’s a good idea to move it to an external server or storage device to ensure that it’s safe and secure. Storing the backup file on a separate server or storage device can help to protect it in the event of a disaster, such as a server failure or a security breach.<\/p>\n\n\n\n
To move the backup file to an external server, you can use SCP.<\/p>\n\n\n\n
<\/p>\n\n\n\n
SCP<\/strong>: Secure Copy (SCP) is a secure file transfer protocol that allows you to transfer files between servers using SSH. To use SCP, you will need to have SSH access to both the source and destination servers. You can use the following command to copy the backup file to the external server:<\/p>\n\n\n\n
\nscp \/path\/to\/backupfile user@external-server:\/path\/to\/destination<\/code><\/pre>\n\n\n\n
<\/a><\/h3>\n\n\n\n
Step 4: Restore the Volume<\/strong><\/h3>\n\n\n\n
If you need to restore the volume from the backup, you can use the docker run<\/code> command to start a container that mounts the backup file and a separate container that writes the backup data to the volume.<\/p>\n\n\n\n
Here’s an example of how to do this:<\/p>\n\n\n\n
docker run --rm \\\n--mount source=<volume-name>,target=<target> \\\n-v $(pwd):\/backup \\\nbusybox \\\ntar -xzvf \/backup\/<backup-filename>.tar.gz -C \/<\/code><\/pre>\n\n\n\n
In this command, replace <volume-name><\/code> with the name of the volume you want to back up, <target><\/code> with the mount point inside the docker container, and <backup-filename><\/code> with a name for the backup file.<\/p>\n\n\n\n
<\/a><\/h2>\n\n\n\n
Example<\/strong><\/h2>\n\n\n\n
For the purpose of this blog, we will be setting up a basic Docker environment for MongoDB, along with an Express application to visualize the data.<\/p>\n\n\n\n
<\/a><\/h3>\n\n\n\n
Setup MongoDB Docker<\/strong><\/h3>\n\n\n\n
Create a docker-compose.yml<\/code> file.<\/p>\n\n\n\n
You can use the below example to setup MongoDB docker:<\/p>\n\n\n\n
# Use root\/example as user\/password credentials\nversion: '3.1'\nservices:\n  mongo:\n    image: mongo\n    container_name: mongo\n    restart: always\n    environment:\n      MONGO_INITDB_ROOT_USERNAME: root\n      MONGO_INITDB_ROOT_PASSWORD: example\n    volumes:\n      - mongodb:\/data\/db\n  mongo-express:\n    image: mongo-express\n    container_name: mongo-express\n    restart: always\n    ports:\n      - 8081:8081\n    environment:\n      ME_CONFIG_MONGODB_ADMINUSERNAME: root\n      ME_CONFIG_MONGODB_ADMINPASSWORD: example\n      ME_CONFIG_MONGODB_URL: mongodb:\/\/root:example@mongo:27017\/\nvolumes:\n  mongodb: ~<\/code><\/pre>\n\n\n\n
<\/p>\n\n\n\n
In the above example, I added a named volume mongodb<\/code>. Here we have configured docker to persist its data to a volume.<\/p>\n\n\n\n
docker-compose up<\/code><\/pre>\n\n\n\n
<\/p>\n\n\n\n
To check the running docker containers you can use the below command.<\/p>\n\n\n\n
docker ps<\/pre>\n\n\n\n
<\/p>\n\n\n\n
You should see 2 docker containers running i.e. mongo<\/code> and mongo-express<\/code>.<\/p>\n\n\n\n
CONTAINER ID   IMAGE           COMMAND                  CREATED          STATUS          PORTS                                       NAMES\n5f68eaf8184a   mongo-express   \"tini -- \/docker-ent\u2026\"   11 seconds ago   Up 9 seconds    0.0.0.0:8081->8081\/tcp, :::8081->8081\/tcp   mongo-express\n6789cf1e7bed   mongo           \"docker-entrypoint.s\u2026\"   11 seconds ago   Up 10 seconds   27017\/tcp                                   mongo<\/code><\/pre>\n\n\n\n
<\/p>\n\n\n\n
You can also view the volume which you created using the following command.<\/p>\n\n\n\n
docker volume ls<\/code><\/pre>\n\n\n\n
<\/p>\n\n\n\n
For me the output looks like this<\/p>\n\n\n\n
DRIVER    VOLUME NAME\nlocal     82fd19dfc5dc839a51b2afd59614474038cd0ce8b494739d883d9b503cd0c61e\nlocal     32582d9a00557c9229418062e6308515c4c4c7eb0bb14a8c43203cafffb675c5\nlocal     docker-test_mongodb<\/code><\/pre>\n\n\n\n
<\/p>\n\n\n\n
The volume name docker-test_mongodb<\/code> was automatically created when I placed my docker-composer.yml<\/code> file inside the docker-test folder<\/code>. This is the location where all of our MongoDB data will be stored.<\/p>\n\n\n\n
<\/a><\/h3>\n\n\n\n
Modify MongoDB Data<\/strong><\/h3>\n\n\n\n
To confirm that we have successfully restored the database from the volume, we need to make a minor modification to the database.<\/p>\n\n\n\n
Visit 0.0.0.0:8081<\/code> where the Mongo Express is running.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/p>\n\n\n\n
Create a new database here. I created my-new-db<\/code> as the new database.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
So now we need to ensure that this new database that is created is also restored.<\/p>\n\n\n\n
<\/a><\/h3>\n\n\n\n
Take Backup<\/strong><\/h3>\n\n\n\n
Let’s take the backup of the volume now.<\/p>\n\n\n\n
Please run the following command to take the backup.<\/p>\n\n\n\n
 docker run --rm \\\n  --mount source=docker-test_mongodb,target=\/data\/db \\\n  -v $(pwd):\/backup \\\n  busybox \\\n  tar -czvf \/backup\/docker-test_mongodb.tar.gz \/data\/db<\/code><\/pre>\n\n\n\n
\/data\/db<\/code> here is the path that is mounted inside the docker container for the volume.<\/p>\n\n\n\n
You should see a backup file created with docker-test_mongodb.tar.gz<\/code> as the file name.<\/p>\n\n\n\n
<\/a><\/h3>\n\n\n\n
Reset Docker<\/strong><\/h3>\n\n\n\n
As I will be performing the restore process on the same machine, I should delete both the container and the volume.<\/p>\n\n\n\n
docker rm -v mongo-express<\/code><\/pre>\n\n\n\n
docker rm -v mongo<\/code><\/pre>\n\n\n\n
docker volume rm docker-test_mongodb<\/code><\/pre>\n\n\n\n
<\/a><\/h3>\n\n\n\n
Restore Backup<\/strong><\/h3>\n\n\n\n
I will proceed to recreate the containers, and we can confirm that the volume has been deleted by checking the databases on Mongo Express.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/p>\n\n\n\n
Now we can run the below command to restore the backup.<\/p>\n\n\n\n
docker run --rm \\\n--mount source=docker-test_mongodb,target=\/data\/db \\\n-v $(pwd):\/backup \\\nbusybox \\\ntar -xzvf \/backup\/docker-test_mongodb.tar.gz -C \/<\/code><\/pre>\n\n\n\n
<\/p>\n\n\n\n
Go to Mongo Express and refresh the page.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
You will now be able to see that the database which we previously created has been successfully restored.<\/p>\n\n\n\n
<\/a><\/h2>\n\n\n\n
Conclusion<\/strong><\/h2>\n\n\n\n
Taking backups and restoring volumes in Docker can be a complex and error-prone process. However, with the right approach, it’s possible to ensure that your critical data is safe and recoverable in the event of a disaster. By following the steps outlined in this article, you can take backups of your volumes with ease and restore them when necessary.<\/p>\n","protected":false},"excerpt":{"rendered":"
As more and more developers turn to Docker to streamline their development processes, it becomes increasingly important to understand how to take backup and restore a volume in Docker. In this article, we’ll explore the pain areas around volume backup and restoration, the reasons for doing it, and provide a comprehensive solution that will help […]<\/p>\n","protected":false},"author":22,"featured_media":235099,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","_lmt_disableupdate":"","_lmt_disable":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[82,106],"tags":[83,84],"class_list":["post-3910","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops","category-technology","tag-devops","tag-dockers"],"modified_by":null,"jetpack_featured_media_url":"https:\/\/osmosys.co\/uk\/wp-content\/uploads\/sites\/6\/2023\/04\/featured-jpeg.webp","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts\/3910","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/users\/22"}],"replies":[{"embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/comments?post=3910"}],"version-history":[{"count":5,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts\/3910\/revisions"}],"predecessor-version":[{"id":235109,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts\/3910\/revisions\/235109"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/media\/235099"}],"wp:attachment":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/media?parent=3910"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/categories?post=3910"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/tags?post=3910"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}