On Tue, Apr 10, 2001 at 09:02:13AM -0400, Kleynerman, Arthur wrote:
> Suad, did you specify force=yes (to override the options in the dsm.opt
> file)?
>
> For example:
>
> def clientopt opt_set 'Exclude ' seq=0 force=yes
Aaarrggghh ... found out what the story is.
When I actually demonst
>My understanding from documentation is that specifying force=yes on server
>side inclexcl options will process those includes/excludes *before* the
>ones in the client side dsm.opt file. And force=no will process them
>after. In effect, force=yes puts the server side rules at the "bottom" of
>t
-Original Message-
>From: Richard Sims [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, April 10, 2001 9:16 AM
>To: [EMAIL PROTECTED]
>Subject: Re: cloptset broken for Windows 4.1.2.X client
>
>
> >Suad, did you specify force=yes (to override the options in the dsm.opt
What if one has all of inclexcl statements defined in the client option set
and none in the dsm.opt file?
-Original Message-
From: Richard Sims [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 9:16 AM
To: [EMAIL PROTECTED]
Subject: Re: cloptset broken for Windows 4.1.2.X client
PROTECTED]
Subject: cloptset broken for Windows 4.1.2.X client
I have upgraded a few Windows (2Kpro) boxes from the 3.7.2 TSM client
to the 4.1.2.19 one.
The new client seems to ignore the Client-Option set assigned to these
clients?
In our case, it ignores all the EXCLUDE options and proceeds to
>Suad, did you specify force=yes (to override the options in the dsm.opt
>file)?
Note that INCLEXCL and DOMAIN are additive options such that
Force has no effect. That is, Force pertains only to
singular options.
I have upgraded a few Windows (2Kpro) boxes from the 3.7.2 TSM client
to the 4.1.2.19 one.
The new client seems to ignore the Client-Option set assigned to these
clients?
In our case, it ignores all the EXCLUDE options and proceeds to backup
the entire hard-drive.
Anyone aware of this one?
Che
