-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Any way to backup the docker volumes as directory and not in archive? #148
Comments
Right now this is not supported. It should not be too hard to add the functionality though (I'm not entirely sure how the configuration would work right now, but it's very likely it's possible to figure this out). If anyone wants to add this, I am happy to discuss the implementation details, merge PRs and give support in any way that it's needed. |
Till then it can be added, I want to ask that is backing up the volumes
directly from /var/lib/docker/volume/(volume_name) a good approach?
Obviously, I'll stock the containers before that
…On 8/29/2022 12:05 PM, Frederik Ring wrote:
Right now this is not supported. It should not be too hard to add the
functionality though (I'm not entirely sure how the configuration
would work right now, but it's very likely it's possible to figure
this out).
If anyone wants to add this, I am happy to discuss the implementation
details, merge PRs and give support in any way that it's needed.
—
Reply to this email directly, view it on GitHub
<#148 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQWBM4FNGBEPY6R2XMDSW3V3RK23ANCNFSM572YAFTQ>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I have never tried that so I cannot give any advice. Another thing you could do is: use this image, and before using Kopia to upload to B2, untar the archive created (you could even do this in a labeled command). This should give you incremental backups as well, it's just not the most efficient way. |
Yup, that's a fantastic idea.
going to implement this kind of setup soon.
Thanks a lot :-)
…On 8/29/2022 6:15 PM, Frederik Ring wrote:
Till then it can be added, I want to ask that is backing up the
volumes directly from /var/lib/docker/volume/(volume_name) a good
approach? Obviously, I'll stock the containers before that
I have never tried that so I cannot give any advice.
Another thing you could do is: use this image, and before using Kopia
to upload to B2, untar the archive created. This should give you
incremental backups as well.
—
Reply to this email directly, view it on GitHub
<#148 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQWBM2L62V37P5XD2FZFWLV3SWHFANCNFSM572YAFTQ>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi, is incremental backup something that is as of today in scope or will be anytime soon? Thank you |
Incremental backups would be nice, yes. That being said, I don't know which storage backends would even support this? As a workaround for now, you can do something like described here https://offen.github.io/docker-volume-backup/how-tos/handle-file-uploads-using-third-party-tools.html |
Actually I'm using this image since some months now and I must say that it is fantastic!
The only thing which I miss is the incremental backups.
I use Backblaze B2 and hence I require incremental backups a lot.
I'm thinking to pair this image with Kopia because it can make incremental backups.
But I'm unable to identify that how to configure this image so that it doesn't generate the tar archive.
Instead of it it generates the directory and that same directory will be backed up with Kopia because it provides incremental backups.
Any help please?
The text was updated successfully, but these errors were encountered: