>When we would archive,
>files were being managed under the mgt class we specified, but the
directories
>were getting backed up to the mgt class with the longest retension period.
With
>each mgt class having a different destination tape pool, many many tapes
were
>being mounted!  We don't worry about this now when there is only mgt class
per
>domain.


It seems to me that you're limiting your flexibility alot by doing it this
way.  Essentially, you're limiting each client to one mgmt class.  I would
personally find that unacceptable.  Why don't you try using a Directory Mgmt
Class?  If you set a DIRMC in a client options set, point it to a 100 MB
(even that is overkill) disk pool that migrates to it's own tape pool (I've
yet to ever go over one tape in the tape pool for any installation I've
done), you effectively send all extended directory information to one place,
simplifying your life.  Just make sure you give it a good long retention.

The way you're using Domains is not the way it was intended.  Domains were
intended to allow segregation of clients that have drastically different
needs/policies/etc, generally separating large departments that want
independant control over their storage.  It was not intended as a fix to
lots of tape mounts, and I don't think should be taken as such, you only
limit yourself in the long term....

Paul