thread1733-1634387
Being new to clustering specifically in an exchange 2010 environment I was unsure how to fail the cluster group back to the primary node after the database and cluster failed over, without rebooting the secondary server after the primary came back on line.
The DAG is fairly easy using the Exchange 2010 interface.
The cluster took me awhile, after reading several blogs on the subject I found what I was looking for.
In 2008 the failback was taken out of the GUI and can be done by the command line.
“Cluster group” will list the available groups and their status.
“cluster "Cluster Group" /move” will move the cluster group to the available node. I have a two node cluster so I did not have to specify the node to move it to.
There are other option available to cluster.exe command to find out what they are use the /? to list them.
I hope this help anyone looking for this information.
Being new to clustering specifically in an exchange 2010 environment I was unsure how to fail the cluster group back to the primary node after the database and cluster failed over, without rebooting the secondary server after the primary came back on line.
The DAG is fairly easy using the Exchange 2010 interface.
The cluster took me awhile, after reading several blogs on the subject I found what I was looking for.
In 2008 the failback was taken out of the GUI and can be done by the command line.
“Cluster group” will list the available groups and their status.
“cluster "Cluster Group" /move” will move the cluster group to the available node. I have a two node cluster so I did not have to specify the node to move it to.
There are other option available to cluster.exe command to find out what they are use the /? to list them.
I hope this help anyone looking for this information.
