Creating a Virtual Cluster – Part 2 – The Windows Cluster
Join the DZone community and get the full member experience.Join For Free
as part of this ongoing series in creating a virtual cluster, this post will cover the creation of the windows cluster, using the shared storage created in part 1.
as can be seen in the proposed architecture diagram to the left, we have a shared storage device, and next we’ll be setting up the windows servers, then adding the two sql server boxes together to create a cluster.
part 3 of this series will be to create a sql server cluster.
step 1 – creating the windows servers
i’m going to assume that you can install windows server 2008 r2.
we’ll be needing three instances of windows server 2008 r2. one running as a domain controller, and two member servers.
so, go ahead and create those three vm’s, set one up as a domain controller, and add the two member servers to the domain.
note that each of the network cards in each server should have static ip addresses.
for the specification of the servers, i’ve gone with this for the domain controller, since it doesn’t require a huge amount of resources.
the two member server’s need an additional network card for the heartbeat connection. to achieve this, both these server’s have an additional network adapter, configured on a private network.
once the two member servers are up and running, go to server manager, right click on features and tick the failover clustering option. click through the wizard to install it. do this on both member servers.
step 2 – adding the iscsi targets on member server 1
next, we need to add the iscsi target created previously, to the windows server. do this by going to start -> administrative tools and iscsi initiator. in here, go to the discovery tab, and click add portal
then, you’ll be able to click on the targets tab, and you should see the drives hosted on the freenas vm.
highlight each disk (starting with the quorum disk) and click the log on button. tick the ‘automatically restore this connection when the computer starts’ tickbox, and click ok. repeat this step for each disk.
next, you’ll be able to go to disk management, and you’ll see the disks you’ve just created. for each disk, you need to bring them online, initialise them, create a simple volume on them using ntfs, and then take them offline again.
step 3 – setting up member server 2
next, we need to add the iscsi drives to the 2nd member server. so go to start -> administrative tools and launch iscsi initiator. if you are prompted to start the service, say yes. as before, go to the discovery tab, click add portal, enter the ip address of the freenas vm, and click ok.
go to the targets tab, and log on to each of the drives, and ensure you tick the automatically log on tickbox.
next, go to disk management in server manager, and you should see the drives, offline, and with blue lines, indicating the drives are configured.
step 4 – validating the cluster
one of the really helpful features of windows server 2008 r2 is the ability to validate your cluster configuration, prior to creating it. it runs a whole long list of tests, and tells you how it got on. tests include the disk subsystem (can both members connect to the drives), networking (is there a heartbeat card in both, that communicates, ip address checks, etc) and checking all the services are configured appropriately.
to validate your cluster, go to start -> administrative tools and failover cluster management. then click validate a configuration…
the wizard will start, and page 2 will prompt you for your server names. enter these, or browse for them
click next, click next to choose to run all the tests, and click next to run them. it takes a little while to run them all. all being well, you’ll get a list of green, followed by a screen similar to this:
“if the light is green, the trap is clean” - link
note: if your validation fails due to an ip address conflict, and you can’t see a network card that is causing it (since all your servers have static ip addresses), there may be an issue with the ‘teredo tunneling pseudo interface’. this can be resolved by going to device manager, go to view and click show hidden devices. right click on the teredo tunneling pseudo-interface and choose disable. then revalidate your cluster configuration.
step 5 – creating the cluster
once we’ve successfully validated the cluster, we can create the cluster. this can be done by clicking ‘create a cluster…’.
you’ll be presented with a wizard. click next, and enter the names of the two member servers and click next. enter the name of the cluster, and if you have dhcp, the ip address will be configured. if you aren’t using dhcp, it’ll need to be specified. click next, and the information will be confirmed. click next and your cluster will be created.
if everything is successful, you’ll get a confirmation screen, and confirmation of the quorum type configured.
you’ll then be able to see the details in failover cluster management, showing the various disks, and the drives will appear in windows explorer, showing the clustered disks.
so that’s part 2 completed, we now have a shared storage device, and a windows cluster running off it, using 4 vm’s. next we need to install sql server on the cluster to get it doing something.
Published at DZone with permission of Nick Haslam, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
A Data-Driven Approach to Application Modernization
The Role of AI and Programming in the Gaming Industry: A Look Beyond the Tables
Five Java Books Beginners and Professionals Should Read
How Web3 Is Driving Social and Financial Empowerment