Efim is correct, both about the force and about processing order. I got ahead of myself. We built our client option sets to be as inclusive as possible, within minimal include and exclude statements, so that clients could override the behavior with includes and excludes that got processed because there were no conflicting server side options. Resulted in a blind spot in my thinking - we haven’t had a customer need to override the management classes provided.
A possible alternative solution: create a separate domain with the same management classes, but with different retention and storage characteristics defined by those classes as needed. Then, assign the nodes as needed to that domain. That is, get to the same destination - system state information handled in a different manner - by changing the underlying behavior of the assigned management class, not the name FWIW, Bob (And thanks, Efim, for catching my error!) Robert Talda EZ-Backup Systems Engineer Cornell University +1 607-255-8280 [email protected] > On Jun 13, 2018, at 2:26 PM, Efim <[email protected]> wrote: > > 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 <[email protected]> написал(а): >> >> 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 <[email protected]> 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 >>> [email protected] >>> >>> >>>> On Jun 13, 2018, at 8:56 AM, Genet Begashaw <[email protected]> wrote: >>>> >>>> Thank you >>>> >>>> Genet Begashaw >>>
