1 00:00:01,140 --> 00:00:01,540 Hello there. 2 00:00:01,540 --> 00:00:03,870 Welcome to Pluralsight. Welcome to the module, Manage 3 00:00:03,870 --> 00:00:06,020 a Windows Server Failover Cluster. 4 00:00:06,020 --> 00:00:10,260 My name's Tim Warner. In this module, we continue our work 5 00:00:10,260 --> 00:00:13,170 with failover clustering. Here we're going to get more 6 00:00:13,170 --> 00:00:15,790 deeply into clustered roles. 7 00:00:15,790 --> 00:00:19,100 You're going to learn about Scale‑Out File Server. We'll formally 8 00:00:19,100 --> 00:00:22,990 treat the witness. We're going to use an Azure cloud witness. We'll 9 00:00:22,990 --> 00:00:26,090 learn how to configure floating IP addresses for the cluster both 10 00:00:26,090 --> 00:00:29,970 on‑prem and in the cloud. And you'll also understand load balancing 11 00:00:29,970 --> 00:00:32,140 options for failover clustering. 12 00:00:32,140 --> 00:00:35,480 I like this module especially well because we are in fact 13 00:00:35,480 --> 00:00:38,590 going to be working both with local Windows Server, as well 14 00:00:38,590 --> 00:00:41,060 as Windows Server running in Azure. 15 00:00:41,060 --> 00:00:44,720 Let's get started. We're about midway through our Implement and 16 00:00:44,720 --> 00:00:47,980 Manage Windows Server High Availability course. There are five 17 00:00:47,980 --> 00:00:53,610 modules, and all of them support Microsoft exam AZ‑801. First module 18 00:00:53,610 --> 00:00:55,800 is on installing failover clustering. 19 00:00:55,800 --> 00:01:00,430 Next, we started our cluster configuration looking a bit at storage. 20 00:01:00,430 --> 00:01:04,310 Now we're getting more into cluster roles, as I mentioned. That 21 00:01:04,310 --> 00:01:08,260 will continue in the fourth lesson on managing failover clustering 22 00:01:08,260 --> 00:01:12,400 in which we do failover/failback operations. And lastly, we circle 23 00:01:12,400 --> 00:01:14,440 back on Storage Spaces Direct. 24 00:01:14,440 --> 00:01:21,000 This is the preferred storage layer and failover clustering at least from the perspective of the exam.