ADSM-L

cloptsets ( include/exclude-options) with Netware Client

2015-10-04 17:42:39
Subject: cloptsets ( include/exclude-options) with Netware Client
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
To: ADSM-L AT VM.MARIST DOT EDU
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





<Prev in Thread] Current Thread [Next in Thread>
  • cloptsets ( include/exclude-options) with Netware Client, ADSM : Dist Stor Manager [mailto:ADSM-L <=