Hi, parametr Force has no affect to include/exclude in cloptset. use q inclexcl client command to check resulting (cloptset+dsm.opt) include/exclude in normal order (from top to bottom). You will find that server include/exclude processed first. Efim
> 13 июня 2018 г., в 16:43, Genet Begashaw <gbega...@umd.edu> написал(а): > > Thanks for your response, on the server side it was included by Optionset > with force=no, i tried to overwrite in the client side in dsm.opt file with > different mgmt class like shown below > > include.systemstate ALL MC-mgmt-name > > still did not work > > Thank you > > > > > > On Wed, Jun 13, 2018 at 9:37 AM Robert Talda <r...@cornell.edu> wrote: > >> Genet: >> >> For us it is simple: create a client option set with the list of >> include/exclude rules with FORCE=NO. Complexity comes from number of >> client options sets needed to support different platforms (Win 7, Win 10, >> OS X, macOS, various Linux destroys) and determining which client option >> set to assign a given node >> >> YMMV, >> Bob >> >> Robert Talda >> EZ-Backup Systems Engineer >> Cornell University >> +1 607-255-8280 >> r...@cornell.edu >> >> >>> On Jun 13, 2018, at 8:56 AM, Genet Begashaw <gbega...@umd.edu> wrote: >>> >>> Thank you >>> >>> Genet Begashaw >>
