Join Ed Liberman for an in-depth discussion in this video What you should know, part of Windows Server 2012 R2: Implement Business Continuity and Disaster Recovery.
- [Narrator] Before watching this course, there's a couple of things I think you should know. First it will be really helpful if you have a general understanding of Windows Server operating systems as a whole. In addition, if you have a basic knowledge of Windows Server 2012 management, and be familiar with the interface and how to move around in that operating system, that will be very helpful as well. Beyond that, there's not much other knowledge you need coming in. I'll walk you through anything else that you need to know.
I do want to show you my lab environment, so that you can understand my demos and possibly even set up an environment on your own to try to follow along with me. So, my lab environment is actually fairly simple. I have a single computer running Windows 10 and it has the Hyper-V role installed. Then within Hyper-V, I have a number of virtual machines and that's what we're looking at here. Now I don't want you to get discouraged, because I have eight machines here, and I want you to know going in you don't need all eight.
First, just to explain what we're looking at, my fake enterprise environment involves a couple of domain controllers called DC1 and DC2. They are operating a domain called LandonHotel.local. In addition to that, I have four member servers, simply called member one, two, three, and four. They are all member servers of the LandonHotel.local domain. I also have a couple of Windows 10 clients.
They're called client one and client two, and also belong to the domain. This is a setup that I use in many of my courses, but we don't necessarily use every machine for every course. In this course, the only machines you will see me demonstrate on are the four member servers. So, member one, two, three, and four. If you want to set up an environment on you own to follow along, optimally, the six machines you would want to set up are DC1 and DC2 along with the four member servers.
But if resources are limited, I can tell you that you can get away with a single domain controller, which, again, you don't have to name it like I do, but I have DC1. You could use two member servers, member one and member two would do the job there. All you would have to keep in mind is when I go to member three or four, you would have to use your member one and two and if there was any demonstration that requires three machines, then you would need to use DC1 along with the two member servers.
That is pretty much it. That is all you need to know in order to get through this course.
Note: This course also maps to the Implement Business Continuity and Disaster Recovery domain for MCSA Exam 70-412 Configuring Advanced Windows Server 2012 Services.
- Understanding data protection
- Configuring NLB
- Configuring failover clustering
- Configuring Cluster-Aware Updating (CAU)
- Failover clustering with Hyper-V