You just do:

update node nnnnnnn  domain=yy

Works fine, you don't lose data.

HOWEVER, what actually happens is that the files are rebound to the new
management class the next time a backup is run on the  client.  You may see
some messages in the scheduler log about files rebinding; it's harmless.

Before you do it, take a look at the management classes in domain xx and
domain yy.  If the management class names are not the same, any files that
were backed up to the "missing" management classes other than the default
management class, will be governed by the "grace retention period" defined
for the new domain.   That might cause you some unexpected results if you
have management management classes defined.

Hope that helps, it's a bit confusing.
You might want to create a "test" client, backup up some files, then switch
domains, then back the client up again to experience this for yourself.

************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************




> -----Original Message-----
> From: Alessio Prodon [SMTP:aprodon AT CENTROGESTIONE.G-NET DOT IT]
> Sent: Wednesday, July 05, 2000 5:35 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      move a node under a XX policy to YY policy
>
> Hello !!!
>
> Scenario: Server : ADSM 3.1.2.50 on AIX  -----  Client : Wndows NT Server
> / NT
> Workstation with ADSM 3.1.0.6
>
> How can I move one or more node from a policy (XX) to policy (YY) whithout
> lost
> data???
> Anyone experience this??
>
> Thanks in advantage.
>
>
>           Alessio Prodon
> (Proud to use ADSM on AIX)