On Mon, 26 May 1997, Peter Thomas wrote:
> From: Peter Thomas on 05/26/97 01:44 PM
>
> In the creation of an Exclude statement under Windows/NT, is the "case" of
> the directory names coded important?
>
> Checking the outputs from my scheduled backups, I see that slthough I do
> have coded an
> EXCLUDE *:\...\PAGEFILE.SYS
> EXCLUDE *:\...\SYSTEM32\CONFIG\*.*
> EXCLUDE *:\...\SYSTEM32\CONFIG\...\*.*
According to what I found out experimentally, the problem is with the
wildcards in your example. Your EXCLUDEs should read
EXCLUDE *:\...\SYSTEM32\CONFIG\*
EXCLUDE *:\...\SYSTEM32\CONFIG\...\*
Contrary to DOS wildcard behaviour, *.* matches only files whose name
contains a period, whereas * matches all files.
If you look at the DSM.OPT distributed with the WIN32 client,
it appears that even the people who prepared the original
INCL/EXCL-List were uncertain about ADSM's wildcard semantics,
since the original file reads similar to
EXCLUDE *:\...\SYSTEM32\CONFIG\*
EXCLUDE *:\...\SYSTEM32\CONFIG\*.*
EXCLUDE *:\...\SYSTEM32\CONFIG\...\*
EXCLUDE *:\...\SYSTEM32\CONFIG\...\*.*
This has created some confusion with our users.
Sincerely, M.F.
>
> there are errors in the DSMSCHED.LOG saying
> ANS4228E Sending of object 'C:\WINNT35\system32\config\admin000' failed
> ANS4090E Access to the specified file or directory is denied
> ...
> ANS4638E Incremental backup of 'C:' finished with 6 failure
Dr. Michael Fink +-----------------------------+------------------------
EDV-Zentrum | Universitaet Innsbruck | Tel: +43(512)507-2311
Computing Services | Technikerstrasse 13 | FAX: +43(512)507-2944
--------------------+ A - 6020 Innsbruck, Austria | Michael.Fink AT uibk.ac DOT
at
=========================================================================
|