Moving resource groups to another node

These options include:

• Resource groups remain on the nodes to which they are moved.

  You can move resource groups that have the Never Fallback policy to another node. When you do so, you can tell PowerHA SystemMirror to leave the resource group on the destination node until you decide to move the group again.

• When you move a resource group with the RG_move command, it remains on the node to which it was moved either indefinitely (until you tell PowerHA SystemMirror to move it to another node) or until you reboot the cluster.

  If you do stop the cluster services, which rarely has to be done, and you want to permanently change the resource group's node list and highest priority node, change the resource group's attributes and restart the cluster.

• If you take the resource group online or offline on any of the nodes, it remains online or offline either until the next cluster reboot, or until you manually bring the group online elsewhere in the cluster.
• If your resource group has the fallback to highest priority node policy, the group falls back to its destination node, after you move it.

  For instance, if the group has node A configured as its highest priority node and you move it to node B, then this group will remain on node B and will treat this node now as its highest priority node. You can always choose to move the group again to node A. When you use SMIT to do so, PowerHA SystemMirror informs you as to whether the original highest priority node (node A) is now available to host the group.

  You can keep track of all resource groups that were manually moved by using the clRGinfo command.