Exclude arbitrary directories from backup #7352
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replace hardcoded .noaiobackup path checks with borg's native --exclude-if-present option, allowing users to exclude any directory from backup by placing a .noaiobackup marker file in it. Changes: - Backup: Use --exclude-if-present=.noaiobackup --keep-exclude-tags - Restore: Dynamically detect .noaiobackup markers from backup archive (not local filesystem) and build exclude patterns accordingly - Keep RESTORE_EXCLUDE_PREVIEWS as standalone feature
- Update section title to be more general - Explain that .noaiobackup can be placed in any directory - Document that marker files are kept in backup for restore detection - Clarify restore behavior with excluded directories
Collaborator
szaimen
added
2. developing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
referring back to #4751 (reply in thread) I could use some help. I've been unable to create a local testing setup successfully unfortunately so would like to hear if this PR works or what the issues are. Specifically I've been unable to get the master container to run my custom built borg container - could you have a testrun of this or help me set this up better?