-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature Request: Back up into folders instead of Tar archives #15
Comments
This is actually on the ToDo list for the same reason as yours :) https://forums.unraid.net/topic/132721-plugin-ca-appdata-backup-restore-v25/page/18/#comment-1251220 |
Ah, that's what I get for not looking deep enough. Thank you! |
The recent forum activity revealed, that dedup software like Duplicacy is able to use non-compressed If Borg is able (and Duplicacy is), I dont see any advantage of implementing this. At least not now. Could you check if Borg is capable of this? |
It looks like Borg's import-tar feature (https://borgbackup.readthedocs.io/en/stable/usage/tar.html) may offer similar functionality. But, it looks like Borgmatic (https://projects.torsion.org/borgmatic-collective/borgmatic) does not expose this functionality. I'm beginning to feel like it may be more appropriate to ask the Borgmatic developers to expose the Borg's built-in tar-handling feature. |
+1 for this. (also thanks for the great unraid plugin) I use urbackup with its cross-platform support and btrf snapshotting for very quick backup times. It does file de-duplication out of the box but not block dedupe. An rsync-like option instead of tar would be great. |
I like to export my backups to an external backup repository using Borg Backup. However, because the backups generated by unraid-appdata.backup are in tar archives, I cannot take advantage of Borg Backup's deduplication features.
I'd like to have the option to back up my appdata as folders, instead of as tar archives. I'd like the result of using this option to be seeing each application's data saved in a folder in the specified backup destination, as opposed to the tar archives that are standard now.
Perhaps rsync could be used for this? Perhaps the main backup routine could resemble something like this?
The text was updated successfully, but these errors were encountered: