Although our iSCSI virtual disks and partitions created on these disks have names, the Failover Cluster Manager will not display them.
To simplify your life, don't hesitate to rename them.
To do this, right-click "Properties" on each cluster disk.
Change their names at the top and click OK.
Now, we see directly which disk is assigned to what.
Besides, you also see that the witness disk was automatically assigned to : Disk Witness in Quorum.
Same for the networks available on the servers of the cluster.
Feel free to rename them by right-clicking "Properties" on them.
As mentioned before, we have 4 network cards on the servers of our cluster :
For the Heartbeat NIC, you will only need to allow cluster network communication on this network.
This also means that the heartbeat will pass on this network and will allow the cluster servers to know if the others are still available or are currently down.
For iSCSI 1 and iSCSI 2 network adapters, don't allow cluster network communication on this network.
Indeed, these 2 network cards should only be used for iSCSI traffic. Which allows to benefit from the best possible performances.
For the network adapter connected to the LAN of the company named LAN, you will need to :
This means that the heartbeat will also be able to pass on the local network (if the Heartbeat network doesn't work any more) to allow the servers of the cluster to continue to know if the other servers of the cluster are still available or are currently down.
Once you have successfully renamed and configured your different networks, you should get this (under Windows Server 2012) :
On Windows Server 2012 R2, the displayed result will be slightly different :
Because a server in a cluster might fail at any time, you probably will not manage your cluster from one of these servers, but rather from outside the cluster.
This way, you will connect to the cluster (not directly to one of the servers in the cluster) and manage it remotely in a completely transparent way.
Indeed, it's Windows Server that will make the necessary to connect seamlessly to an available server in your cluster.
In short, to manage this cluster remotely (from the local network of the company), you will first have to install the associated administration tools.
For that :
In both cases, you will find the "Failover Clustering Tools" in : Remote Server Administration Tools -> Feature Administration Tools.
Next, open the Failover Cluster Manager and click "Connect to Cluster" (in the "Actions" menu on the right).
Enter the full name of your cluster : iw-cluster.informatiweb.lan
You now have access to managing your cluster from outside of the cluster.
Creating a cluster, it's good, but using it is better.
Indeed, for the moment, we have a cluster, but it doesn't provide any services.
For your cluster to be useful, you need to add a role to it. For example : a file server.
But, you will quickly see that adding a role to a cluster will also imply that the associated role is installed locally on each server of the cluster.
Install the "File Server" role (located in "File and Storage Services -> File and iSCSI Services") on each server of your cluster.
Then, right click on your cluster and click on "Configure Role".
The High Availability wizard is displayed.
Select the "File Server" role and click Next.
Select "File Server for general use".
Provide a name and an IP address for your "File Server" cluster.
Select the iSCSI virtual disk to assign to this cluster role.
The High Availability wizard displays a summary of the configuration.
Wait while configuring the cluster role.
The high availability of the "File Server" role has been configured.
Now, our cluster has 1 clustered role with 2 nodes (2 servers).
In the "Roles" section, you will see that our cluster "iw-file-server" appears as a file server and is currently hosted by server 2 (clust-s2).
In addition, in the "Summary" tab at the bottom, you will see that this role can be accessed using the "iw-file-server" name (or its FQDN : iw-file-server.informatiweb.lan) or its address IP: 10.0.0.111.
At the bottom, you will also see what resources this role has.
Which means that this role depends on this or that resource.
In our case, this clustered role depends on :
Currently, this role only offers a hidden network share : F$.
If you look at the server 2 informations, you will see that it actually hosts our clustered role : iw-file-server.
If you view the different disks associated with your cluster, you will see that :
Note that clustering this "File Server" role has also resulted in the creation of a DNS record associated with the information specified when clustering this role :
An additional computer account has also been created on your Active Directory server.
Windows Server 8/4/2019
Windows Server 7/12/2019
Windows Server 7/26/2019
® InformatiWeb-Pro.net - InformatiWeb.net 2008-2020 - © Lionel Eppe - All rights reserved.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.