Well, IMHO:

Just because you CAN have lots of different domains does NOT mean that you
SHOULD.
For simplicity's sake, many sites can have ONE domain and ONE schedule that
will work OK for most nodes.

I don't think you need to be concerned about NT users accidentally restoring
AIX stuff - they have to try pretty hard (using VIRTUALNODENAME, etc) to
have one machine recover another machine's files.

If you want to separate includes and excludes by OS, you should use client
option sets for that, not domains.

Where you MIGHT want to start breaking stuff into different domains is when
you have legal or technical retention policies: like, 7-year-legal
requirement here, keep-many-versions for the developers there, etc.  This is
because the most important thing you get by putting a client node into a
domain is a default POLICY, ie how many versions and how many days to retain
files.  (You can overide the default policy, of course, by using a different
management class for the node, or even a directory or filename pattern on
the node, in the include-exclude list.)

So you could have:
Node            OS              Dept            Domain  Cloptset
ordinary        NT              Acct            STANDARD        NTOPTS
acctarchive     WinXP           Acct            7YEAR           XPOPTS
newsystem       AIX             Acct            DEVEL           AIXOPTS
oldspecs        NT              Engineering     7YEAR           NTOPTS
joespc  WinXP           Engineering     STANDARD        XPOPTS
geniuspc        Solaris Engineering     DEVEL           SOLOPTS

and so on.


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Robert L. Rippy
> Sent: Monday, December 09, 2002 12:34 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: What is the game plan for mixing clients on the same
> server?
>
>
> True.
>
>
>
>
>
> From: "Hagopian, George" <GHagopian AT ICTGROUP DOT COM> on 12/09/2002 12:22 
> PM
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject:  Re: What is the game plan for mixing clients on the same server?
>
> I guess the same would be for the users so the Win restore people wouldn't
> touch the AIX stuff?
>
> -----Original Message-----
> From: Robert L. Rippy [mailto:robert_rippy AT KINDREDHEALTHCARE DOT COM]
> Sent: Monday, December 09, 2002 12:10 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: What is the game plan for mixing clients on the same
> server?
>
>
> There is no problem. I have NT,W2K, 95/98 MAC AIX all going to
> once server.
> Just plan correctly so that its managable. I would suggest seperate
> domains.
>
> Thanks,
> Robert Rippy.
>
>
>
>
> From: "Hagopian, George" <GHagopian AT ICTGROUP DOT COM> on 12/09/2002 12:04 
> PM
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject:  What is the game plan for mixing clients on the same server?
>
> I have been running TSM for all my AIX boxes...now I will be moving all
> Windows boxes to TSM as well...excited about doing this (yeah yeah yeah)
> but
> after thinking about it, would it be better to put all the Win boxes
> (2k,NT)
> to their own TSM server?
> What are the issues...if any...for having 40 or so Win boxes sharing the
> same TSM db and server with 15 large AIX boxes...
>
> TIA
> George Hagopian
>
> PS I also posted this message online forum...not sure what kind of hits it
> is getting
>