Starting with the 4.2 client, it is immaterial whether you include or
exclude adsm.sys, as it gets backed up anyway as part of the system object
backup. This is in the README file that accompanies the client:

    - The System Objects will no longer be affected by INCLUDE and EXCLUDE
      statements; e.g., the user will no longer have to explicitly include
      the registry staging directory for backup, INCLUDE
C:\ADSM.SYS\...\*,
      to ensure that the registry is backed-up properly. Also, if the
      user were to accidently exclude a directory that was critical to
      a system object backup, the system object backup will not be
affected.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Gill, Geoffrey L." <GEOFFREY.L.GILL AT SAIC DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/22/2002 10:28
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: inclexcl help for windoze box



>Exclude *:\...\pagefile.sys
>Exclude *:\...\SYSTEM32\CONFIG\*.*
>Exclude *:\...\SYSTEM32\CONFIG\...\*
>Exclude *:\...\UMS\*
>Exclude *:\...\PROFILES\*
>Exclude *:\...\adsm.sys
>Exclude *:\...\NETWORK ASSOCIATES\*
>Exclude *:\...\dsmsched.log
>Exclude *:\...\NTEVT.log
>Exclude *:\...\NORTON GHOST 6.0\*
>Exclude *:\LOGS\*
>Exclude *:\...\SYSTEM32\WBEM\*

With so many things to do besides TSM it's very possible things changed
again on me and I haven't caught up yet. But I thought we should have the
following (INCLUDE) not exclude.
Include *:\adsm.sys\...\*

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   gillg AT saic DOT com <mailto:gillg AT saic DOT com>
Phone:  (858) 826-4062
Pager:   (888) 997-9614