Thanks to everyone for your suggestions/recommendations/war-stories/etc on
this topic. It has been really helpfull !





Bill Boyer <bill.boyer AT VERIZON DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/15/2003 02:43 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Moving a node to a different Policy Domain


Also, if the client is running in PROMPTED mode, you'll need to restart
the
scheduler or CAD service if running managedservices. Seems the TSM server
"forgets" the IP/Port information of the client when you put it in a
different domain.

Bill Boyer
DSS, Inc.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Joni Moyer
Sent: Tuesday, July 15, 2003 12:58 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Moving a node to a different Policy Domain


That's exactly what it will do.  My problem was I wasn't aware of a MC
being used by the node that was moved and I lost data.  If you just want
to
move the node to a new domain and let it get rebound to the default MC,
then you'll be fine.  Good luck!

Joni Moyer
Systems Programmer
joni.moyer AT highmark DOT com
(717)975-8338



                      Zoltan
                      Forray/AC/VCU            To:
ADSM-L AT VM.MARIST DOT EDU
                      <zforray AT VCU DOT EDU>        cc:
                      Sent by: "ADSM:          Subject:  Re: Moving a node
to a different Policy Domain
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>


                      07/15/2003 12:55
                      PM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






That doesn't sound very encouraging...................

By "same management class", you mean named the same ?

This is one of the reasons I want to move this and other nodes from this
PD/PS/MC to another, newly defined one. The MC that was assigned as
default really doesn't work for these nodes.

If I redefine the old MC in the new PD/PS, but NOT as the DEFAULT, would
that be enough to avoid loosing data ?

I thought the move would simply rebind existing backups/archives to the
new default MC ????





Joni Moyer <joni.moyer AT HIGHMARK DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/15/2003 12:26 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Moving a node to a different Policy Domain


Be very careful moving a node to a different domain.  You must make sure
that the new domain has the same management classes or else it will
receive
the default for that domain and most likely delete your files.  Trust me I
have done this and have lost important data and then I had to rollback to
a
previous database backup to get the data back...

Joni Moyer
Systems Programmer
joni.moyer AT highmark DOT com
(717)975-8338



                      Zoltan
                      Forray/AC/VCU            To: ADSM-L AT VM.MARIST DOT EDU
                      <zforray AT VCU DOT EDU>        cc:
                      Sent by: "ADSM:          Subject:  Moving a node to
a different Policy Domain
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>


                      07/15/2003 12:16
                      PM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






I am doing some reorganization and want to moving a node to a different
Policy Domain.

What are the ramifications of this ?   Any gotchas ?  Pitfalls ?