Microsoft failover cluster testing in VMware virtual environments

VMware Microsoft's failover cluster testing under virtual environment

Host Configuration

two win2008 R2 Enterprise Edition Server

test01 public10.10.1.146 Private 172.16.0.1

test02 public10.10.1.147 Private 172.16.0.2

Store

in the EMC storage divides two LUNs, one for cluster quorum disks and one for storing data.

1. in the two LUNs created in EMC storage

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/59/BC/wKiom1Tdj8WwKicBAAKFbcA_C3Q365.jpg "title=" 1.jpg " alt= "Wkiom1tdj8wwkicbaakfbca_c3q365.jpg"/>

put the new LUNs joined in the storage group:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/59/B9/wKioL1TdkM_QhVnOAAJ18LOo7xE231.jpg "title=" 2.jpg " alt= "Wkiol1tdkm_qhvnoaaj18loo7xe231.jpg"/>

Install the steps above and build a LUNs.

2. Attach two LUNs to two servers

Test01 Mount data storage LUN

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/59/BC/wKiom1Tdj-WgxICKAAHO_dXOSZg732.jpg "title=" 3.jpg " alt= "Wkiom1tdj-wgxickaaho_dxoszg732.jpg"/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/59/B9/wKioL1TdkTqTHhr1AAEnhyYxQzk515.jpg "style=" float: none; "title=" 4.jpg "alt=" Wkiol1tdktqthhr1aaenhyyxqzk515.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/59/BD/wKiom1TdkEKwVWVnAAE2QPcJKRk517.jpg "style=" float: none; "title=" 5.jpg "alt=" Wkiom1tdkekwvwvnaae2qpcjkrk517.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/59/B9/wKioL1TdkTqjPXcYAAEsbIZYIek674.jpg "style=" float: none; "title=" 6.jpg "alt=" Wkiol1tdktqjpxcyaaesbizyiek674.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/59/BD/wKiom1TdkEPx5tf5AAIELJ-GsJY120.jpg "style=" float: none; "title=" 7.jpg "alt=" Wkiom1tdkepx5tf5aaielj-gsjy120.jpg "/>

the same operation Mounts " arbitration LUN "

Test02 Mounting " data LUN"

When you mount the " data LUN" and " quorum LUN" on the second machine , you cannot select " bare device " when adding the disk, but you should select " Existing disks " (Disk is found in the virtual machine directory where Test01 is mounted)

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/59/BD/wKiom1TdkHWzdshkAAH1D8uUe40865.jpg "style=" float: none; "title=" 8.jpg "alt=" Wkiom1tdkhwzdshkaah1d8uue40865.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/59/B9/wKioL1TdkW7iprspAAFFedcPcsY032.jpg "style=" float: none; "title=" 9.jpg "alt=" Wkiol1tdkw7iprspaaffedcpcsy032.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/59/BD/wKiom1TdkHbTribBAAIKvo3tG8s956.jpg "style=" float: none; "title=" 10.jpg "alt=" Wkiom1tdkhbtribbaaikvo3tg8s956.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/59/B9/wKioL1TdkW6DiM3xAAIKaGurUuQ987.jpg "style=" float: none; "title=" 11.jpg "alt=" Wkiol1tdkw6dim3xaaikaguruuq987.jpg "/>

Mount the quorum LUN for the same operation .

Precautions:

1. Configure the cluster nodes first:
test01 Public 10.10.1.146 Private 172.16.0.1
test02 Public 10.10.1.147 Private 172.16.0.2
and are joined to the same domain, each node has two network cards.
One used to do cluster heartbeat, one used to do normal network communication.
Two cluster nodes, at least two or more shared disks, one to do the quorum disk, one to do the data disk.
2. Create a new user on the domain controller for cluster configuration of two nodes, with sufficient domain administrative privileges.
If a new user is not built, the domain administrator account is used to manage the cluster configuration of the node.
3. Test the connectivity of the network.
4. Add failover clustering functionality to each node, respectively.
5. Configure the quorum disk and the shared disk separately on one of the nodes for failover cluster configuration
The primary function of configuring the quorum disk is to detect the state between nodes for failover.
The shared disk, which is primarily used to store data, configures the disk to enable cluster shared volumes.

Network configuration for the failover cluster:

For each network that is actually connected to a server (node) in the failover cluster, you can specify whether the network is used by the cluster, and if used by the cluster, the network is used only by nodes or by clients. Note that in this case, the client contains not only the client computers that access the Cluster service and applications, but also the remote computers that are used to administer the cluster.
If you use a network for ISCSI (storage devices), do not use it for network traffic in the cluster.
Modify network settings for a failover cluster
1. If the cluster that you want to configure is not displayed in the Failover Cluster Management snap-in, right-click Failover Cluster Management in the console tree, click Manage Clusters, and then select or specify the cluster that you want.
2. If the console tree is collapsed, expand the tree below the cluster you want to configure.
3. Expand Network.
4. Right-click the network for which you want to modify settings, and then click Properties.
5. If necessary, change the name of your network.
6. Select one of the following options:
-Allow the cluster to use this network
If you select this option and you want the network to be used only by the node (not the client), clear allow clients to connect over this network. Otherwise, make sure that you select it.
-the cluster is not allowed to use this network
Select this option if your network is used only for ISCSI (communicating with storage devices) or for backup only. (These are the most common reasons to choose this option.) )
Attached: Adding storage to the failover cluster step
1. If the cluster that you want to configure is not displayed in the Failover Cluster Management snap-in, right-click Failover Cluster Management in the console tree, click Manage Clusters, and then select or specify the cluster that you want.
2. If the console tree is collapsed, expand the tree below the cluster you want to configure.
3. Right-click Storage, and then click Add Disk.
4. Select the disks you want to add.

Problem:

Change the cluster problem caused by the password?

When building the cluster, the password is set to 123 for convenience because the server is always restarted. After the completion of the construction, of course, can not use such a simple password, changed to a complex password. Unexpectedly, the This look problem came. Cluster Server also fails: The phenomenon is that all partitions on the array are visible to two servers, but none of them can be opened. The workaround for this problem is "My Computer" right-click on "Properties", "Services and Applications"-"services", find "cluster serives" service right-click on "Properties", select "Login" tab, modify the password of the user with the cluster login to make it the same as the new password.

Delete Cluster method?

You cannot delete the Cluster service, but you can restore it to a status that is not configured:
1. Start Cluster Administrator (CluAdmin.exe).
2. Right-click the node, and then select Stop Cluster service.
Note: Do not perform this step if this server is the last node in the cluster.
3. Right-click the node, and then tap exit nodes.
This step returns the cluster to its original, not configured state. Later, you can rejoin it to the same cluster or other cluster.
If you cannot start the Cluster service, or if you have difficulty removing the node, you can manually cancel the configuration of the Cluster service:
Run the Cmd.exe program to open the command prompt type:
Cluster node name/forcecleanup, and then press ENTER. (This command is available for non-normal removal of the cluster)

Summary: The Windows high Availability scenario supports the Failover Clustering feature only for WINDOWS2008R2 Enterprise editions.
This feature can be combined with Microsoft Hyper-V to build virtual machines for dynamic migrations and rapid migrations, providing high
Performance of the virtual machine. The quorum disk and the data disk in the cluster can only be used by the node that is currently active, and the other
Inactive nodes, the quorum disk and the data disk are offline. First, the cluster is built, and then the corresponding
Application server configuration. Applications that are installed independently are installed in the shared storage.

Common scenarios for Windows high availability:

1.windows server, you can use the failover cluster role to achieve a variety of server and application hot standby capabilities.
2. Improve performance by using Network load capabilities for Web server traffic load
3. Disk-based RAID technology for high performance storage disks
4. High performance for file servers via DFS

This article is from the "Banging blog" blog, please be sure to keep this source http://weadyweady.blog.51cto.com/3012956/1614279

Microsoft failover cluster testing in VMware virtual environments