Wildcards in exclude-filelist for duplicity

Clash Royale CLAN TAG#URR8PPP
I am trying to exclude a "bulk" folder in each home directory from the backup. For this purpose, I have a line
- /data/home/*/bulk
in my exclude-filelist file.
However, this doesn't seem to be recognised:
Warning: file specification '/data/home/*/bulk' in filelist exclude-list-test.txt
doesn't start with correct prefix /data/home/kay/bulk. Ignoring.
Is there a way?
BTW: is the format in general compatible with rsync's exclude-from? I have a working exclude list for that, where this wildcard expression works.
backup rsync wildcards duplicity rdiff-backup
add a comment |
I am trying to exclude a "bulk" folder in each home directory from the backup. For this purpose, I have a line
- /data/home/*/bulk
in my exclude-filelist file.
However, this doesn't seem to be recognised:
Warning: file specification '/data/home/*/bulk' in filelist exclude-list-test.txt
doesn't start with correct prefix /data/home/kay/bulk. Ignoring.
Is there a way?
BTW: is the format in general compatible with rsync's exclude-from? I have a working exclude list for that, where this wildcard expression works.
backup rsync wildcards duplicity rdiff-backup
add a comment |
I am trying to exclude a "bulk" folder in each home directory from the backup. For this purpose, I have a line
- /data/home/*/bulk
in my exclude-filelist file.
However, this doesn't seem to be recognised:
Warning: file specification '/data/home/*/bulk' in filelist exclude-list-test.txt
doesn't start with correct prefix /data/home/kay/bulk. Ignoring.
Is there a way?
BTW: is the format in general compatible with rsync's exclude-from? I have a working exclude list for that, where this wildcard expression works.
backup rsync wildcards duplicity rdiff-backup
I am trying to exclude a "bulk" folder in each home directory from the backup. For this purpose, I have a line
- /data/home/*/bulk
in my exclude-filelist file.
However, this doesn't seem to be recognised:
Warning: file specification '/data/home/*/bulk' in filelist exclude-list-test.txt
doesn't start with correct prefix /data/home/kay/bulk. Ignoring.
Is there a way?
BTW: is the format in general compatible with rsync's exclude-from? I have a working exclude list for that, where this wildcard expression works.
backup rsync wildcards duplicity rdiff-backup
backup rsync wildcards duplicity rdiff-backup
asked Oct 6 '14 at 11:30
mcandrilmcandril
1237
1237
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It's possible the problem lies on an improper passing of the path with wildcard character by the duplicity to the rsync. Look at the example below. This is the real example of passing excludes to the rsync by an environment variable within a script:
EXCLUDES="--exclude=/etc/blkid.tab --exclude=/root/dir1 --exclude='*.sql'"
Notice that quotation marks '' are used to separate the entry containing asterisk to prevent a shell from expanding this wildcard character. Try to use quotation marks within the exclude-list-test.txt file.
I tried to use - '/data/home/**/bulk' Still gives me "Warning: file specification ''/data/home/**/bulk'' in filelist exclude-list-test.txt doesn't start with correct prefix /data/home/kay/bulk. Ignoring." I tried --exclude-globbing-filelist now with my original file. This does work in general, but results in an error when one of the lines is outside the source path.
– mcandril
Oct 6 '14 at 12:14
Sorry, for some reason line breaks with two spaces didn't seem to work.
– mcandril
Oct 6 '14 at 12:21
If your path has the pattern as above you should use --exclude-globbing-filelist and:
– Sebastian Piech
Oct 6 '14 at 13:29
If your path has the pattern as above you should use --exclude-globbing-filelist and /data/home/*/bulk inside an excludes file. Double asterisk matches subfolders and it's not your goal in this case I guess. I don't know if you're using any includes also -- it could take precedence and change exclude acting as well. See 'File Selction' chapter of the duplicity manual: duplicity.nongnu.org/duplicity.1.html
– Sebastian Piech
Oct 6 '14 at 13:37
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f159578%2fwildcards-in-exclude-filelist-for-duplicity%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It's possible the problem lies on an improper passing of the path with wildcard character by the duplicity to the rsync. Look at the example below. This is the real example of passing excludes to the rsync by an environment variable within a script:
EXCLUDES="--exclude=/etc/blkid.tab --exclude=/root/dir1 --exclude='*.sql'"
Notice that quotation marks '' are used to separate the entry containing asterisk to prevent a shell from expanding this wildcard character. Try to use quotation marks within the exclude-list-test.txt file.
I tried to use - '/data/home/**/bulk' Still gives me "Warning: file specification ''/data/home/**/bulk'' in filelist exclude-list-test.txt doesn't start with correct prefix /data/home/kay/bulk. Ignoring." I tried --exclude-globbing-filelist now with my original file. This does work in general, but results in an error when one of the lines is outside the source path.
– mcandril
Oct 6 '14 at 12:14
Sorry, for some reason line breaks with two spaces didn't seem to work.
– mcandril
Oct 6 '14 at 12:21
If your path has the pattern as above you should use --exclude-globbing-filelist and:
– Sebastian Piech
Oct 6 '14 at 13:29
If your path has the pattern as above you should use --exclude-globbing-filelist and /data/home/*/bulk inside an excludes file. Double asterisk matches subfolders and it's not your goal in this case I guess. I don't know if you're using any includes also -- it could take precedence and change exclude acting as well. See 'File Selction' chapter of the duplicity manual: duplicity.nongnu.org/duplicity.1.html
– Sebastian Piech
Oct 6 '14 at 13:37
add a comment |
It's possible the problem lies on an improper passing of the path with wildcard character by the duplicity to the rsync. Look at the example below. This is the real example of passing excludes to the rsync by an environment variable within a script:
EXCLUDES="--exclude=/etc/blkid.tab --exclude=/root/dir1 --exclude='*.sql'"
Notice that quotation marks '' are used to separate the entry containing asterisk to prevent a shell from expanding this wildcard character. Try to use quotation marks within the exclude-list-test.txt file.
I tried to use - '/data/home/**/bulk' Still gives me "Warning: file specification ''/data/home/**/bulk'' in filelist exclude-list-test.txt doesn't start with correct prefix /data/home/kay/bulk. Ignoring." I tried --exclude-globbing-filelist now with my original file. This does work in general, but results in an error when one of the lines is outside the source path.
– mcandril
Oct 6 '14 at 12:14
Sorry, for some reason line breaks with two spaces didn't seem to work.
– mcandril
Oct 6 '14 at 12:21
If your path has the pattern as above you should use --exclude-globbing-filelist and:
– Sebastian Piech
Oct 6 '14 at 13:29
If your path has the pattern as above you should use --exclude-globbing-filelist and /data/home/*/bulk inside an excludes file. Double asterisk matches subfolders and it's not your goal in this case I guess. I don't know if you're using any includes also -- it could take precedence and change exclude acting as well. See 'File Selction' chapter of the duplicity manual: duplicity.nongnu.org/duplicity.1.html
– Sebastian Piech
Oct 6 '14 at 13:37
add a comment |
It's possible the problem lies on an improper passing of the path with wildcard character by the duplicity to the rsync. Look at the example below. This is the real example of passing excludes to the rsync by an environment variable within a script:
EXCLUDES="--exclude=/etc/blkid.tab --exclude=/root/dir1 --exclude='*.sql'"
Notice that quotation marks '' are used to separate the entry containing asterisk to prevent a shell from expanding this wildcard character. Try to use quotation marks within the exclude-list-test.txt file.
It's possible the problem lies on an improper passing of the path with wildcard character by the duplicity to the rsync. Look at the example below. This is the real example of passing excludes to the rsync by an environment variable within a script:
EXCLUDES="--exclude=/etc/blkid.tab --exclude=/root/dir1 --exclude='*.sql'"
Notice that quotation marks '' are used to separate the entry containing asterisk to prevent a shell from expanding this wildcard character. Try to use quotation marks within the exclude-list-test.txt file.
answered Oct 6 '14 at 12:06
Sebastian PiechSebastian Piech
993
993
I tried to use - '/data/home/**/bulk' Still gives me "Warning: file specification ''/data/home/**/bulk'' in filelist exclude-list-test.txt doesn't start with correct prefix /data/home/kay/bulk. Ignoring." I tried --exclude-globbing-filelist now with my original file. This does work in general, but results in an error when one of the lines is outside the source path.
– mcandril
Oct 6 '14 at 12:14
Sorry, for some reason line breaks with two spaces didn't seem to work.
– mcandril
Oct 6 '14 at 12:21
If your path has the pattern as above you should use --exclude-globbing-filelist and:
– Sebastian Piech
Oct 6 '14 at 13:29
If your path has the pattern as above you should use --exclude-globbing-filelist and /data/home/*/bulk inside an excludes file. Double asterisk matches subfolders and it's not your goal in this case I guess. I don't know if you're using any includes also -- it could take precedence and change exclude acting as well. See 'File Selction' chapter of the duplicity manual: duplicity.nongnu.org/duplicity.1.html
– Sebastian Piech
Oct 6 '14 at 13:37
add a comment |
I tried to use - '/data/home/**/bulk' Still gives me "Warning: file specification ''/data/home/**/bulk'' in filelist exclude-list-test.txt doesn't start with correct prefix /data/home/kay/bulk. Ignoring." I tried --exclude-globbing-filelist now with my original file. This does work in general, but results in an error when one of the lines is outside the source path.
– mcandril
Oct 6 '14 at 12:14
Sorry, for some reason line breaks with two spaces didn't seem to work.
– mcandril
Oct 6 '14 at 12:21
If your path has the pattern as above you should use --exclude-globbing-filelist and:
– Sebastian Piech
Oct 6 '14 at 13:29
If your path has the pattern as above you should use --exclude-globbing-filelist and /data/home/*/bulk inside an excludes file. Double asterisk matches subfolders and it's not your goal in this case I guess. I don't know if you're using any includes also -- it could take precedence and change exclude acting as well. See 'File Selction' chapter of the duplicity manual: duplicity.nongnu.org/duplicity.1.html
– Sebastian Piech
Oct 6 '14 at 13:37
I tried to use - '/data/home/**/bulk' Still gives me "Warning: file specification ''/data/home/**/bulk'' in filelist exclude-list-test.txt doesn't start with correct prefix /data/home/kay/bulk. Ignoring." I tried --exclude-globbing-filelist now with my original file. This does work in general, but results in an error when one of the lines is outside the source path.
– mcandril
Oct 6 '14 at 12:14
I tried to use - '/data/home/**/bulk' Still gives me "Warning: file specification ''/data/home/**/bulk'' in filelist exclude-list-test.txt doesn't start with correct prefix /data/home/kay/bulk. Ignoring." I tried --exclude-globbing-filelist now with my original file. This does work in general, but results in an error when one of the lines is outside the source path.
– mcandril
Oct 6 '14 at 12:14
Sorry, for some reason line breaks with two spaces didn't seem to work.
– mcandril
Oct 6 '14 at 12:21
Sorry, for some reason line breaks with two spaces didn't seem to work.
– mcandril
Oct 6 '14 at 12:21
If your path has the pattern as above you should use --exclude-globbing-filelist and:
– Sebastian Piech
Oct 6 '14 at 13:29
If your path has the pattern as above you should use --exclude-globbing-filelist and:
– Sebastian Piech
Oct 6 '14 at 13:29
If your path has the pattern as above you should use --exclude-globbing-filelist and /data/home/*/bulk inside an excludes file. Double asterisk matches subfolders and it's not your goal in this case I guess. I don't know if you're using any includes also -- it could take precedence and change exclude acting as well. See 'File Selction' chapter of the duplicity manual: duplicity.nongnu.org/duplicity.1.html
– Sebastian Piech
Oct 6 '14 at 13:37
If your path has the pattern as above you should use --exclude-globbing-filelist and /data/home/*/bulk inside an excludes file. Double asterisk matches subfolders and it's not your goal in this case I guess. I don't know if you're using any includes also -- it could take precedence and change exclude acting as well. See 'File Selction' chapter of the duplicity manual: duplicity.nongnu.org/duplicity.1.html
– Sebastian Piech
Oct 6 '14 at 13:37
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f159578%2fwildcards-in-exclude-filelist-for-duplicity%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown