This text does not claim to be a guide but is rather a reminder for me. Use at your own risk! Often has to move an existing Microsoft cluster to a new faster, bigger San. In the applications that's no problem. I am in the quorum but encountered problems and had to several hours looking for a solution. Also offered by the Microsoft ClusterRecovery.exe should perform exactly this function did not help. Basically, it is quite simple: make San connect all nodes of both the new and the old San.
All nodes to shut down the cluster on which the group runs. Add
In the cluster manager in the cluster group is a new disk resource which is on the lung of the new quorum drive. In the properties of the cluster can be in the Quorum tab change the quorum drive. Problem is now that of MSTDC a dependency to the old quorum drive has. So in the actual properties of the MSTDC what dependencies it look otherwise nor write and has. Delete from MSDTC cluster group. And create new MSTDC in the cluster group. In the dependencies now had to make the new quorum drive and the other settings of the old MSTDC.After a reboot should now start the cluster services automatically and access the new quorum drive.
0 comments:
Post a Comment