Learn how to understand create a Windows Server 2016 failover cluster. This involves installing roles and utilizing available storage. Once the cluster is created, high availability between two or more nodes can be achieved.
- [Voiceover] There's many different high availability options in Windows Server 2016, and one of the best ones is the failover cluster manager feature. So, let's go ahead and add that feature by clicking on the "Add roles and features", and click "Next", and we'll continue to click "Next" until we get to where we need to be, and that is at the failover clustering feature. Go ahead and choose to add the features that go along with it, and click "Next". And we'll just make sure we have what we want and click "Install".
It may take several minutes to complete the feature installation, and when we're done, we'll be able to get started by creating our first cluster. Once the cluster role is installed, we're going to create our first cluster, but then in upcoming videos, we're going to also configure cluster networking, quorums, and storage, as well as other cluster type things, such as the cluster events and troubleshooting. And we'll be adding various different cluster roles, such as file sharing, hyper-v, and others.
Failover cluster is very flexible in what it can do, and with all the different roles that we can add. Now, we've gone ahead and finished. The installation has succeeded. We'll click "Close", and now when we go to our tools menu, we'll see a new option, and that's the failover cluster manager. We'll open up the manager, and we see the cluster manager on the left, where we configure our first cluster. Let's go ahead and right-click and choose "create cluster". We get a new cluster wizard that pops up.
Let's go ahead and choose "Next", and now we're going to enter the server name for our first cluster. Let's go ahead and put in our local server name, and it has found the server, so we can go ahead and click "Next". Now, we can also run configuration validation tests, and I definitely recommend that we do that, although it does take some time to do it, and it does generally generate a lot of errors, but that's okay, because the errors can help us keep problems from happening before they start. So, let's go ahead and allow the validation test, but if you're in a hurry, I can suggest that you can run the tests after you're all done, rather than doing it during the cluster creation.
Let's go ahead and choose "Next", and there's the run all tests or just specific tests. Let's go ahead and choose to run all of them, and we'll click "Next". These tests vary. Mostly, they're hardware tests, such as do we have the right processor? Does it have virtualization turned on? Does it have all the memory that we need, the storage that we need, and once it's all done, it'll tell us any tests we may not have passed, and then we can troubleshoot those. We received a "test passed", which is fantastic, but we do have some other things, other than success, in parts of this, such as "List Disks To Be Validated".
It's not applicable, because we have not added any disks yet, and if we scroll down, we have a warning under the network configuration. If we click on "View Report", we can get more details on that. And this what the report looks like. Let's go ahead and click on "Network", and take us to that area where there's a problem, and we'll click on "Validate Cluster Network Configuration", and it says, in yellow, which is very easy to find, that Ethernet 2 does not have an address with a subnet prefix, so it's looking for IP version six on our Ethernet 2 network card, so that's pretty easy to fix.
All we have to do is right-click and go to network and sharing center. Change adapter settings. Go to our Ethernet 2, and click on IP version six. Looks like it's been disabled, so if we enable it, it will end up with an IP address automatically, and that should result in that error going away. Let's go ahead and close, and just confirm that we don't have any other warning messages. Looks like we have a few. Test requires one more node. Okay, so we've only added one node, up until now.
We need to add a second node in order to actually have a redundant cluster, so we're going to add our other VM host here shortly, and it looks like that same message is just coming up over and over. Yep, same thing again. All right, let's go ahead and close this, and we'll choose "Finish", and now we'll give it a cluster name. Let's go ahead and call it "Cluster 1", and we need to give an IP address. This is the IP address just for the cluster. It's not for a physical server. It's for all of the servers that will respond to a single IP address.
So, let's choose an IP address that's not being used currently, and we'll put that in, and choose "Next". Says we are ready to create the cluster. Click "Next", and this could take several minutes. It just depends on the speed of your server, so just be patient. You may also get a message saying that it's taking longer than it expected, but usually it still will complete without issues. If it does have issues, you can click on view the report, and you can see how to resolve those issues.
We have one warning about the appropriate disk was not found, and that's because we have not added the storage yet. Let's go ahead and click "Finish", and now our cluster shows up in the upper left-hand corner, and we are able to add our roles. We can add nodes, which is just a fancy way of saying add more servers. We can add storage, and networks, as well. Preparing and creating the cluster allows the administrator to create a high-availability server operation for their server network.
- Configuring network load balancing
- Configuring failover clustering
- Managing clusters
- Interacting with Hyper-V
- Managing failover cluster roles
- Configuring role-specific settings
- Configuring virtual machine monitoring
- Managing cluster movement