I have another question (sorry for asking too much).
In my scenery, I received a TSM solution (that has many different clients) where for some strange reason they created too many Policies domain for one same client. I’m trying to arrange this consolidating one client by one policy domain.

In the case of this particular client (called it ABC) we have the following:
* We have one TSM instance
* ABC has like 5 policies domain
* Some nodes of ABC in different domains use the same stgpool
* Others domains of ABC have exclusive stgpool

So here are my doubts:
1) Just like Jonathan asked you, it is possible to just define the all the MC of the different policies domain with the same retentions and version they have and then move the nodes in one ABC policy domain, OR
2) I have to create a no limit MC, make it default and then move the nodes.
3) And regarding the issue of the move nodedata, it is necessary even though my stgpool are going to we define in the new MC and belong to the same DEVCLASS

I hope, I’m not asking too many questions.

Thanks in advanced,
SAE.

Sorry, I guess I miss understood your original question as it was not obvious.

Though as step 3 said “update node” is the command it self. You can use “help update node” to find out all the options of that command, though below is the command with the basic parameters to change your node to a new domain.

update node nodename -domain=domainname

I hope that answer your question, & good luck.

I think, I just express myself wrong. My doubt was regarding step 4.

In this step 4, which command and parameter do I have to use to move my node to the new domain.

Thanks.

6. Run a move nodedata specifying from=old_sequential_stgpool to=the_new_one

You will have basically to use the move command as shown above. Please though make sure you follow the other steps in the article to make sure you don’t miss any step. Furthermore, I would recommend you practice this move on a test environment before carrying it out on your production.

I hope that help.

Thanks.

I would not put my company or my customer data into that situation, would you? I would recommend you follow up the move data procedure stated .

Enjoy,
TSMGuru

I am sorry for the bit late reply, but I was busy with my dad being hospitalized. I am worried that your planned method won’t work. If you are to move the nodes to a new policy domain, I would highly recommend you follow the method I explained above. In simple word the order of doing so is:

1- Create a new policy domain with all the needed configuration and the expiry required. Make sure you activate it and you set the expiry information correctly before you move the node to it. Else you can hit a disaster, if the expiry in the new policy was too soon when the node is moved to it.
2- Change the configuration of the client to point to the new Policy domain.
3- Run a move nodedata specifying from=old_sequential_stgpool to=the_new_one <== Please note this is a very important step. As most people forget this, and their data does not get moved or pointed to the new storage pool, and does not get managed by the new policy. So make sure you handle this correctly.

Please read the post carefully, and follow all the instructions in doing your move, don’t take any short cuts with your data, as that can lead to disaster when you try to restore later.

I hope that help, and let me know if you need any further help.