|
Matthias,
In
your definition of the option you must provide a sequence number and also ensure
that the clopset option overrides the options file options:
define
clientopt optsetname inclexcl 'exclude *\*:\apps\...\*.*' sequence=0
force=yes
I'll
admit to struggling with this for awhile mydarnself. Persistence usually
pays off.
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box
51313
Colorado Springs CO
80949
719-531-5926
www.storsol.com
lipp AT storsol DOT com
Hi adsm'ers,
I'm just trying to have all my exlude/include-options
for Netware-serves defined at a central-point.
As I understood the way to do this is to use cloptsets wich are
defined
on the adsm-server and associated to
an client node.
As far as good ... but that
seems to be only theory...
I can define an
exclude option with the following command :
define clientopt novopt inclexcl 'exclude
*\*:\apps\...\*.*'
This option is defined and when running an
incremental backup I hoped
to have all files
in 'apps' excluded ... but it worked different, the files are
backed up an became the default-mc assigned.
The association between the node and the cloptset is
defined.
Putting the following line into the option-file,
which is stored
on the Netware-server,
everything works as I thought..
The statement
is :
exclude *\*:\apps\...\*.*
Is there anything I'm thinking wrong of ?
Or is there an limitation with centralized excludes
??
I hope that someone of you has an idea an would be
happy to hear something of your experience
with 'clopsets' ...
best regards,
Matthias Brasch
HEW-Hamburg, Germany
------=_NextPart_000_001E_01BEC20D.CAA61D00--
=======================================================================
| 