Thank you very much for update, but I need to match nodes (files and 
directories) and used management classes to control process, because there are 
a lot of servers and server admins, which are out of my control. I understand 
that it is possible to have many management classes per node and that they can 
be changed by server admins (just edit dsm.opt or include/exclude list). This 
fact makes this information very useful (just to have one point of control).





Grigori G. Solonovitch



Senior Technical Architect



Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com



Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: G.Solonovitch AT bkme 
DOT com



Please consider the environment before printing this Email



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Richard Sims
Sent: Sunday, November 15, 2009 3:37 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] How to match nodes and used management classes/copy 
groups?



This question keeps coming up...

Management classes are associated with individual file system objects, not 
nodes; and rebinding over time, as well as directory association rules, can 
make for a variety of MC utilizations for a single node.  Trying to report all 
utilizations is arduous, and not very useful.  It is better to sample key areas 
of the file systems, which can be done via 'dsmc query backup' from the client, 
or via -Virtualnodename from a comparable client.



   Richard Sims



Please consider the environment before printing this Email.

________________________________
"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses, any other defects, interception or unauthorized modification. The 
information, views, opinions and comments of this message are those of the 
individual and not necessarily endorsed by BKME."