On Fri, May 22, 2015 at 12:45:11AM -0700, Alan Murrell wrote:
> Hi Jon,
>
> Thanks for the reply :-) You seem to the the only one who does :-)
>
> On 21/05/2015 7:49 PM, Jon LaBadie wrote:
> >and is optional. Spindle number is later defined as:
>
>
> OK, I think that makes sense. So if I had another backup of files on the
> "F:" drive of the same host, I might specify a different spindle number for
> those files, then, correct?
spindles != drives
spindles != filesystems
A physical hard disk (one spindle) could contain multiple filesystems
or windows drives.
>
> >1. E:/SERVER_DATA/./a is the "diskname", it is not a path. I'm
> >not used to seeing slashes in the diskname unless it is also the
> >device name. So something like SERVER_DATA_a or E_ServerData_a
> >could be used.
>
> Whether or not slashes are illegal (they don't seem to be), thinks like
> spaces and weird characters in file and path names (other than underscores
> and/or dashes) have always made me uneasy. I think I like the idea of using
> something like E_ServerData_a better :-)
>
> >Depending on the naming consistency of your SERVER_DATA
> >directory, perhaps your include could be an exclude:
> >
> > exclude "[A-Zb-z]*"
>
> I am going to try the following:
>
> exclude "./[b-z]*"
> exclude "./[0-9]*"
>
Two things. [b-z0-9]* should allow you to combine them.
Be aware of "exclude" vs "exclude append". I think "exclude" says
throw away the current exclude list and start a fresh one. I typically
use "exclude append" for all. A global dumptype (eg zwc-compress) may
have already started an exclude list (ex *.tmp) and I don't wish to
discard it. An "exclude append" on an empty list is the same as an
"exclude".
> and will see what happens. Regarding the use of double-slash, if I enter
> the actual directory path to be backed up, like this:
See below regarding slashes.
>
> E:/SERVER_DATA/accounting
>
> that works no problem (of course I realise it's not an exclude statement)
I think I mentioned I saw the double slash comment only in the
description of exclude with ZWC.
To exclude files:
Please use \\ (two back slashes) in the exclude pattern.
For example:
exclude "D:\\Documents\\Images"
To exclude files by extension type, do it like this
(Notice: *No* slashes.):
exclude "*.foo" "*.bar"
Note the lack of "./" or ".\\" in the last example.
?important? probably not.
>
> In all honesty, the folders in the department SERVER_DATA folder don;t
> really change much (occasionally a new one might get added here and there),
> but it is the users' home folder directory that I really want to do this
> pattern matching for, since that *does* change with more regularlity.
>
> >A potential problem might be files or directorys starting
> >with non-alphabetic characters.
>
> They are few and far between, but I would imagine *should* be covered by
> something like:
>
> exclude "./[a-z]*"
>
> which should match directories that start with numbers.
You do not phrase it accurately. It will include all dirs
(and files) in the starting directory that do not begin with
a lower case letter from a to z. That is not only starting
with numbers, but also upper case letters, punctuation,
control chars, and if your character set includes them,
accented lower and upper case letters.
>
> I will advise how the above goes.
>
> -Alan
>>> End of included message <<<
--
Jon H. LaBadie [email protected]
11226 South Shore Rd. (703) 787-0688 (H)
Reston, VA 20190 (703) 935-6720 (C)
