Cluster and Shared SCSI BUS
Host computer and three virtual machines are with the following configuration;
Host Machine:
NIC (Internet)--24.80.99.180 255.255.252.0 (gateway) 24.80.96.1
Memory: 2GB
HD:40GB
Complete the creation and installation of domain VIP.COM
VMachine3:
Public NIC--24.80.99.180 255.255.252.0 preferred DNS: 127.0.0.1
You must make sure that NIC is attached to the Public Network.
Virtual IDE HD:6GB
Memory: 256MB
Install Windows Server 2003 and Active Directory(VIP.COM domain)
Computer Name:DC
Create a user: ClusterAdministrator
Leave the DC on all the time
---
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.
---
complete the creation and installation of Node1
VMachine1:
Memory: 512MB
Hard Disks: 4 virtual hard disks installed
Virtual Hard Disk1: primary channel (0):vdisk1.vhd:6GB;
Virtual hard disk2:SCSI 0 ID 0:quorum.vhd:1GB;
Virtual hard disk3:SCSI 0 ID 1:data.vhd:1GB;
Virtual hard disk4:SCSI 0 ID 2:msdtc.vhd:200MB;
SCSI Adapters
Virtual SCSI Adapter1, virtual SCSI adapter2 and virtual SCSI adapter3 are attached a shared SCSI Bus;
Network Adapters
Virtual Network Adapter 1 is attached to External Network (can access physical adapter);
Virtual Network Adapter 2 is attached to Internal Network
Install Windows Server 2003 Enterprise Edition(Local IDE drive)
Computer Name:Node1
rename Virtual NIC 1 to public:24.80.99.175 255.255.252 Preferred DNS:24.80.99.180
rename Virtual NIC 2 to Private:10.237.0.19 255.255.0.0
Private NIC properties:
uncheck "client for Microsoft Network"
uncheck "File & Printer Sharing For Microsoft Network"
uncheck "Register this connection address in DNS"
uncheck "Enable LMHOSTS lookup"
Join it to VIP.COM domain;
Open Disk Management Console, follow the wizard to initialize the shared SCSI drives (3), 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: 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 off the vMachine1 machine;
Creating vMachine2 and Installing Windows Server 2003 Enterprise
Hardware configuration is same as vMachine1.
Memory: 512MB
Hard Disks: 4 virtual hard disks installed
Virtual Hard Disk1: primary channel (0):vdisk2.vhd:6GB;
Virtual hard disk2:SCSI 0 ID 0:quorum.vhd:1GB;
Virtual hard disk3:SCSI 0 ID 1:data.vhd:1GB;
Virtual hard disk4:SCSI 0 ID 2:msdtc.vhd:200MB;
SCSI Adapters
Virtual SCSI Adapter1, virtual SCSI adapter2 and virtual SCSI adapter3 are attached a shared SCSI Bus;
Network Adapters
Virtual Network Adapter 1 is attached to External Network (can access physical adapter);
Virtual Network Adapter 2 is attached to Internal NetworkInstall Windows Server 2003 Enterprise Edition(Local IDE drive)
Computer Name:Node2
rename Virtual NIC 1 to public:24.80.99.176 255.255.252 Preferred DNS:24.80.99.180
rename Virtual NIC 2 to Private:10.237.0.20 255.255.0.0
Private NIC properties:
uncheck "client for Microsoft Network"
uncheck "File & Printer Sharing For Microsoft Network"
uncheck "Register this connection address in DNS"
uncheck "Enable LMHOSTS lookup"
Join it to VIP.COM domain;
Add VIP\ClusterAdministrator to Local Administrators group;
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 off Node2;
Turn on Node1;
CLuster Administrator to create a new cluster:MyCluster
Cluster IP:24.80.99.200
Cluster Service Account: VIP\ClusterAdministrator
Quorum:drive X
Start Node2 (node1 is running);
Cluster Administrator--Add a new node (Node2) 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 for both Cluster Group, Group 0 and group 1.
Backup system states of both Node1 and Node2.Test the clustering
Stop the Cluster Service at Node1; you will find both Cluster Group and group o and group 1 are moved to Node2.
Group 0:Disk Y failed to move to the other node.
I delete the group 0 and create a new physical disk resource under Cluster Group for Disk Y. The failover to the other node works.
--------------
Microsoft Distributed Transaction Coordinator (MS DTC)
MS DTC must be added to a Cluster. Microsoft recommends that MS DTC use a disk different from the quorum disk or any disk used by SQL server or other applications.
