Julie,
to backup the contents of winnt\system32\config ADSM uses OS
functionality to copy the registry into a directory structure below
c:\adsm.sys.
So, all registry hives will get backed up not from system32\config, but
from c:\adsm.sys\. When an application stores its config data into the
registry, ADSM will get the data and put it into adsm.sys, too.
I'm not sure what happens, when non-registry files reside in
system32\config. It's possible they don't get backed up. Then you only
have the chance of explicitly including thos files in dsm.opt.

Something like
Exclude c:\winnt\system32\config\...\*
Include c:\winnt\system32\config\file1.ini
...

Note that the exclude/include list gets "executed" bootom up, ADSM
detects the rule to backup file1.ini and the statements above are only
relevant for all leftup files.

Regards,
Michael
--
Michael H. Bartl
Michael H. Bartl
ADAC e.V. (Rechenzentrum, Produktionsplanung und Organisation)
Tel.: (089) 7676-4063, Fax: (089) 7676-8161
EMail: Michael.Bartl AT Zentrale.ADAC DOT de

>----------
>Von:   Julianna Walter[SMTP:julie.walter AT UALBERTA DOT CA]
>Gesendet:      Dienstag, 7. Oktober 1997 22:16
>An:    ADSM-L AT VM.MARIST DOT EDU
>Betreff:       Errors with NT registry
>
>I checked my dsmerror.log and found the same "FioGetOneDirEntry(): ***
>Access to NTFS file security information denied," error.  I am only the end
>user support here so I don't have access to the ADSM server.  I asked the
>support guys and they would like to know, "what permissions?"
>
>One more question if I may...
>I'm getting approached with a question about  the WinNT exclude list in the
>Client Backup options file, I'm using the default list from the Redbooks
>found online.  The main concern is the system32/config directory.  The
>Redbooks state if this directory is backed up it can cause damage to the OS
>when recovered.  Some of my clients are running Oracle and Cobol clients on
>their WinNT machines that save their environmental settings to the
>system32/config directory.  I found this out after a clients machine
>crashed, the restore went extremely well except for some of the Oracle and
>Cobol stuff.  Is there anything I can do about this in the future?
>
>Muchly Appreciated,
>Julie Walter
>
>
>>Have you checked to make sure that your ADSM server has the proper
>>permissions to access the files, every time that i've seen the message
>>"FioGetOneDirEntry(): *** Access to NTFS file security information
>>denied," it's because we didn't have the NT permissions set right.
>>
>>Andrea Bellinzaghi wrote:
>>>
>>> Hi all,
>>>
>>> I've foud in my dsmerror.log the following NT message :
>>>
>>> FioGetOneDirEntry(): *** Access to NTFS file security information denied,
>>> file/dir skipped ***
>>> TransWin32RC(): Win32 RC 33 from FileRead(): ReadFile
>>>
>>> What does it mean?? no registry backup performed??
>>>
>>> Then I've restarted adsm service with the parameter "log as" set to
>>> Administrator and I've received the following error message during the
>>> backup :
>>>
>>> 10/07/1997 09:57:19  fioGetAttrib():
>>> getFileSecuritySize(C:\adsm.sys\Registry\AISPC44\Machine) failed
>>> 10/07/1997 09:57:19  TransWin32RC(): Win32 RC 1314 from fioGetAttrib():
>>> getFileSecuritySize
>>> 10/07/1997 09:57:19  fioGetAttrib():
>>> getFileSecuritySize(C:\adsm.sys\Registry\AISPC44) failed
>>> 10/07/1997 09:57:19  TransWin32RC(): Win32 RC 1314 from fioGetAttrib():
>>> getFileSecuritySize
>>> 10/07/1997 09:57:19  fioGetAttrib():
>>> getFileSecuritySize(C:\adsm.sys\Registry) failed
>>> 10/07/1997 09:57:19  TransWin32RC(): Win32 RC 1314 from fioGetAttrib():
>>> getFileSecuritySize
>>> 10/07/1997 09:57:20  fioGetAttrib(): getFileSecuritySize(C:\adsm.sys)
>>> failed
>>> 10/07/1997 09:57:20  TransWin32RC(): Win32 RC 1314 from fioGetAttrib():
>>> getFileSecuritySize
>>> 10/07/1997 09:57:20  ANS4426E An error occurred creating the Backup
>>> Registry Directory structure
>>> 10/07/1997 09:57:20  ANS4847E Scheduled event 'AISPC44' failed.  Return
>>> code = 4.
>>>
>>> Any suggestions, there is something wrong??
>>
>>
>