Wildcards in FileSet questions

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Wildcards in FileSet questions

Ivan Adzhubey
Hi,

Documentation is a bit vague regarding wildcard support in the FileSet
resource:

1. It states repeatedly that wildcards are not supported in the file lists
inside Include {...} directive. Does this mean that they *are* supported
inside Exclude {...} file lists? Note, I do not mean Options {...} clause, I
am talking about the file lists itself.

2.
---from p. 160 of main.pdf---
5. When using wild-cards or regular expressions, directory names are always
terminated with a slash (/) and filenames have no trailing slash.
---quote ends---

The above description is not clear and examples included in the documentation
do not follow this rule. For instance:

---from p. 173 of main.pdf---
FileSet {
Name = "Full Set"
Include {
Options {
wilddir = "/home/a*"
wilddir = "/home/b*"
}
Options {
RegexDir = ".*"
exclude = yes
}
File = /home
}
}
---quote ends---

3. Someone please translate into plain English for me the following paragraph.
Unfortunately, I cannot understand what the author wanted to tell us here:

---from p. 160 of main.pdf---
The Options resource is optional, but when specified, it will contain a list
of keyword=value options to be applied to the file-list. See below for the
definition of file-list. Multiple Options resources may be specified one after
another. As the files are found in the specified directories, the Options will
applied to the filenames to determine if and how the file should be backed up.
The wildcard and regular expression pattern matching parts of the Options
resources are checked in the order they are specified in the FileSet until the
first one that matches. Once one matches, the compression and other flags
within the Options specification will apply to the pattern matched. A key
point is that in the absence of an Option or no other Option is matched, every
file is accepted for backing up. This means that if you want to exclude
something, you must explicitly specify an Option with an exclude = yes and
some pattern matching.
---quote ends---

Does this mean that "the compression and other flags within the Options
specification" will apply *only* "to the pattern matched"? This is not how it
works, as far as I know. Options apply to all files in the file lists as well.

"A key point is that in the absence of an Option or no other Option is
matched, every file is accepted for backing up."

This apparently talks about wildcard options (only) but there are other types
of options, for which this statement will not be true. Very confusing.

Thanks,
Ivan





The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users
Reply | Threaded
Open this post in threaded view
|

Re: Wildcards in FileSet questions

Ivan Adzhubey
Hi,

I have found a somewhat relevant discussion on the list archive, which dates
back to 2005:

https://sourceforge.net/p/bacula/mailman/message/14923506/

This clarified some of the questions about priority in the pattern matching
process but still for majority of my questions it does not provide answers.

Thanks,
Ivan

On Sunday, June 11, 2017 03:17:02 PM Ivan Adzhubey wrote:

> Hi,
>
> Documentation is a bit vague regarding wildcard support in the FileSet
> resource:
>
> 1. It states repeatedly that wildcards are not supported in the file lists
> inside Include {...} directive. Does this mean that they *are* supported
> inside Exclude {...} file lists? Note, I do not mean Options {...} clause, I
> am talking about the file lists itself.
>
> 2.
> ---from p. 160 of main.pdf---
> 5. When using wild-cards or regular expressions, directory names are always
> terminated with a slash (/) and filenames have no trailing slash.
> ---quote ends---
>
> The above description is not clear and examples included in the
> documentation do not follow this rule. For instance:
>
> ---from p. 173 of main.pdf---
> FileSet {
> Name = "Full Set"
> Include {
> Options {
> wilddir = "/home/a*"
> wilddir = "/home/b*"
> }
> Options {
> RegexDir = ".*"
> exclude = yes
> }
> File = /home
> }
> }
> ---quote ends---
>
> 3. Someone please translate into plain English for me the following
> paragraph. Unfortunately, I cannot understand what the author wanted to
> tell us here:
>
> ---from p. 160 of main.pdf---
> The Options resource is optional, but when specified, it will contain a list
> of keyword=value options to be applied to the file-list. See below for the
> definition of file-list. Multiple Options resources may be specified one
> after another. As the files are found in the specified directories, the
> Options will applied to the filenames to determine if and how the file
> should be backed up. The wildcard and regular expression pattern matching
> parts of the Options resources are checked in the order they are specified
> in the FileSet until the first one that matches. Once one matches, the
> compression and other flags within the Options specification will apply to
> the pattern matched. A key point is that in the absence of an Option or no
> other Option is matched, every file is accepted for backing up. This means
> that if you want to exclude something, you must explicitly specify an
> Option with an exclude = yes and some pattern matching.
> ---quote ends---
>
> Does this mean that "the compression and other flags within the Options
> specification" will apply *only* "to the pattern matched"? This is not how
> it works, as far as I know. Options apply to all files in the file lists as
> well.
>
> "A key point is that in the absence of an Option or no other Option is
> matched, every file is accepted for backing up."
>
> This apparently talks about wildcard options (only) but there are other
> types of options, for which this statement will not be true. Very
> confusing.
>
> Thanks,
> Ivan

--
Ivan Adzhubey, Ph.D.
Instructor
Division of Genetics, Dept of Medicine
Brigham & Women's Hospital
Harvard Medical School
New Research Building, Room 0464C
77 Avenue Louis Pasteur
Boston, MA 02115
tel.: (617) 525-4728
fax:  (617) 525-4705
web: http://genetics.bwh.harvard.edu/wiki/sunyaevlab/



The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users