You will also need to re-define the schedule association with a schedule in the 
new domain and if you're running in PROMPTED
schedmode you need to stop/start the TSM service(s) on the client before 
PROMPTED scheduling will work again to that node.


Bill Boyer
"Some days you're the bug, some days you're the windshield" - ??

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Prather, Wanda
Sent: Thursday, November 17, 2005 11:45 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Moving a node from one domain to another

If the new domain has the same management classes as the old domain, all you do 
is :  update node blah domain=newname.

If the old domain has no management classes other than DEFAULT, that's also no 
problem.

If the new domain does NOT have the same management classes as the old domain, 
think hard about what you want to happen.
If TSm can't map a file to a management class in a new domain, it will use the 
grace period, I think, to control versions.

If the new domain/management class points the files to a new storage pool.... 
nothing at all happens.
Changing domains does NOT cause the movement of any data.
If you want to relocate the data, use MOVE NODEDATA after you change the domain.

Hope that helps.

Wanda Prather
"I/O, I/O, It's all about I/O"  -(me)


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Dennis Melburn W IT743
Sent: Thursday, November 17, 2005 11:29 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Moving a node from one domain to another


Is there a safe way to move one node (and all the corresponding archive and 
backup data) from one policy domain to another?


Mel Dennis