| Home | Kaiming |
SCC -- Single Copy Cluster
Shared Resources are owned by only one server at any time.
Domain Layout
Both Geek and Dove have Windows 2003 Server Enterprise edition installed.
Geek is promoted as DC.
Domain user: clusterAdministrator is created.
Create two virtual servers in member server: dove;
Install Windows 2003 server on both server1 and server2.
Member server: Dove
Virtual Server: Server1
Virtual Server: Server2
Internal NICs: Internal 10.0.0.1, Internal 10.0.0.2, and Internal 10.0.0.3
uncheck "client for Microsoft Network"
uncheck "File & Printer Sharing For Microsoft Network"
uncheck "Register this connection address in DNS"
uncheck "Enable LMHOSTS lookup
Join Dove, server1, and server2 to domain 1ASK2.COM.
Create 4 more virtual disks: 1GBdisk2.vhd, 1GBdisk3.vhd, 1GBdisk4.vhd, 1GBdisk4.vhd
Both server1 and server2 will have access and control of all four disks, as shown below.
Server1 and server2:attach virtual hard disks to virtual SCSI adapters
For two-node cluster creation, you must follow the Turn On/Off sequence. If both nodes run at same time before the cluster is created, the shared disks will be corrupted.
Turn on Server1
Open Disk Management Console, follow the wizard to initialize the shared SCSI drives (4), don't convert them to dynamic (Cluster supports only basic disks), create one primary partition for each disk with the whole disk space, and format them as NTFS. I use the drive letters: W, X, Y, Z (Microsoft recommends the higher drive letters should be used).
Users and Computers console and add the VIP\ClusterAdministrator to Local Administrators group;
Backup SystemState; When you configure and test clustering, it is possible that you cannot open the existing cluster and cannot create a new cluster.
Turn down server1
Turn on server2
Open Disk Management console to initialize the SCSI drives; this time, you don't need to create partitions and format them. Even though there are no drive letters for the drives, they are in SCSI drives.
Turn down server2
Turn on Server1
CLuster Administrator to create a new cluster:MyCluster
Cluster IP:192.168.1.200
Cluster Service Account: VIP\ClusterAdministrator
Quorum:drive X
After the cluster: myCluster is created, turn on server2.
Cluster Administrator--Add a new node (Server2) to MyCluster
The warning message does not matter. This is because all the shared disks are currently owned by Node1. Microsoft Cluster uses the share-nothing architecture. Node2 does not have access to the shared storage at the moment.
Set the preferred Owner to server1 and server2 for Cluster Group, Group 0, group 1, and group 2.
At server1:
Move resources in Group 1 and Group 2 to Group 0;
Rename the resource names according the labels of physical disks in My Computer.
Delete Group 1 and Group 2;
Create MSDTS resource
The MSDTC resource depends upon Network Name resource and physical disk resource. Microsoft recommends that a independent disk should be used. Group 0 does not have Network Name resource. In this scenario, msdts resource can only be created in Cluster Group.
Test the failover of resources in a cluster
Test 1:
Resources: msdts Y:, data1 X:, and data2 W: are owned by SERVER2.
Test 2:
Shutdown server1
The owner of all resources is SERVER2.