Our general rule here is  each node gets its own policy domain, that way I 
rarely have to deal with any includes for management classes.

>>> Wanda Prather <wprather AT JASI DOT COM> 6/6/2008 11:18 AM >>>
I think "best practice" is whatever gives you the most control and
consistent results, and it will vary depending on your site conditions.

It is extremely difficult to figure out after the fact (say 2 years from
now), what data is bound to what management classes, if you have a lot of
them, and if you don't have direct access to the clients.

I have customers where the TSM admins have direct access to the clients,
there are a small number of clients, and using a management class to control
retention works just fine.

I have another customer where the number of management classes has turned
into a nightmare.   Nobody knows exactly which of the 180 clients (split
across 8 subsidiary departments) are currently using which management
classes.  My recommendation was to divide the clients into more domains,
where the default mgmt class would control retention and the target
stgpool.  That way it will be more transparently obvious how the clients are
being managed, and harder for Junior TSM admins to do it wrong.    For that
site, more domains is going to work better.

YMMV.




On 6/5/08, Shannon Bach <SBach AT mge DOT com> wrote:
>
> By using the Policy Domain as a retention bucket the TSM Admins are able
> to have a better control of what each clients data actually is retained
> for.  By using the management classes we can only find out on the actual
> clients...which we do not always (and in some cases due to the nature of
> the data... never have access to).  That would be the biggest pro for
> us...higher level control.
>
>
>
> EVILUTION <tsm-forum AT BACKUPCENTRAL DOT COM>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 06/05/2008 02:53 PM
> Please respond to
> ADSM-L AT VM.MARIST DOT EDU 
>
>
> To
> ADSM-L AT VM.MARIST DOT EDU 
> cc
>
> Subject
> Best practice for Policy Domains
>
>
>
>
>
>
> Why not use the managment class to set retention?
>
> +----------------------------------------------------------------------
> |This was sent by jeff.jeske AT sentry DOT com via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> +----------------------------------------------------------------------
>