Feature Request: Add support for "borg import-tar" #825
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'd like to do and why
I'm running Borgmatic on an Unraid server. On this Unraid server, I use unraid-appdata.backup (https://github.com/Commifreak/unraid-appdata.backup) to stop my Docker containers and back them up into .tar.gz archives.
Currently, borgmatic backs up the directory in which these .tar.gz archives are stored, and, as a result, backs up the archives. Because the archives are different at each backup, Borg does not deduplicate the data within them, increasing storage utilization in my backup repo. By adding support for import-tar (https://borgbackup.readthedocs.io/en/stable/usage/tar.html), Borg should handle deduplication and reduce repo storage utilization in this use-case.
Other notes / implementation ideas
No response
Thanks for filing this one!
import-tar
seems like a reasonable borgmatic addition to me. As a work-around though, you might consider playing around with the tarball format to see if you can get better deduplication behavior from Borg. For instance, what if you make an uncompressed .tar file instead of a .tar.gz? Borg deduplicates at the block level (not the file level), so that may actually deduplicate pretty nicely.You may also be interested in #685, which would add borgmatic "native" backup support for Docker containers.