That is correct Tom! So, you are going to define another Policy Domain,
policy set, mgmtclass, and copy group for this new node, correct? This new
domain will be looked at from the ADSM/TSM server as a different entity, so
you can have only one ACTIVE policy set in a policy domain. Other than that
it should be very straight forward if this is only a temporary setup.
Demetrius A. Malbrough
ADSM/TSM Consultant
Texas Instruments
6550 Chase Oaks Blvd.
Plano, TX 75023
(972) 927-9869 Office
(214) 314-3350 Pager
[EMAIL PROTECTED]
-----Original Message-----
From: Tom Bebee [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 02, 2001 2:36 PM
To: [EMAIL PROTECTED]
Subject: Same client - two nodes
We would like to take a Novell client that is part of our one Domain, and
develop another node definition for it. The reason for this is that we want
to run Selective backups against all the volumes (this is a band-aid for a
broken archive process that is being looked at by TSM L2).
My thinking is that the normal node definition can continue to run our daily
incrementals (which are working fine) and the alternate node definition for
the same machine can be used to run selective backups against.
The selective backups will probably run several hours for each Novell
volume, and in the same window our 100+ other nodes are running their own
daily incrementals.
I am thinking that I need to establish another Domain, with a Policy Set and
Management Class for this alternate Novell node definition.
My question - is it possible to have two Policy Sets active as long as they
are in different Domains?
More importantly also does anyone see any problems with setting this up?
TIA
Tom Bebee
Welch Allyn
