Installing and Configuring a Multi Subnet SQL Server (2012 and higher) Failover Clustered Instance

this is the second demo that accompanies the lesson on failover clustering fundamentals in this demo I'm gonna show you how you can provision a sequel server 2012 multi subnet cluster or commonly known as geographically dispersed clusters this demo is based on an article that I wrote on MSE cool tips com last year on how to work with sequel server 2012 multi subnet cluster and while the article uses Windows Server 2008 for its underlying operating system the concepts are the same in the article I've outlined the network diagram that I used for this particular environment I've got the main controllers DNS servers that are getting replicated cluster nodes that I will use for the cluster are in different data centers and I used I scuzzy storage now storage will be anything as long as it does support block level replication and failover clustering so this will be the basis of the demo that I'm gonna do again I strongly recommend it you go through the article to understand the concepts even better this is no different from what I've done in the previous demo on building a sequel server failover clustering instance the only difference is that now I'm dealing with sequel server nodes or cluster nodes that are in different geographical locations or in different network subnets I've repurposed WS cluster 3 n WS cluster 4 for this specific demo nothing in here yet I've provisioned cluster storage for WS cluster 3 in WS cluster 4 that are configured to do block level replication between datacenter number 1 and data center numbers to prove that point notice that I have different IP addresses for these - this is my IP address for WS cluster 3 once I do that 16 that 0.2 1 3 and this is my IP address for the BS cluster 4 they are in two different Network subnets this will be the basis of creating a multi subnet cluster just like before I've already turned on the failover clustering feature on both servers so the vailable clustering feature is already turned on again save on time and this in the storage have been attached to these two servers of course the dotnet framework 3.5 is already installed because this is a prerequisite for sequel server 2012 I already have failover cluster manager and I strongly strongly recommend running the filter cluster validation wizard for the specific configuration primarily because you want to make sure that the storage you're using is supported click on next and just like in previous demo I'm gonna add both WS cluster 3 and ws cluster 4 in my cluster next and I'll just I'll just walk through the entire process if you've already seen this in the previous demo and I am going to run all of the tests I want to make sure that my storage is configured because this highlights a very important concept sequel server relies on the underlying storage subsystem when you're dealing with failure clustered instances a couple of things to consider number one unlike a failover cluster where the nodes are in the same data center both machines are connected to the same disk subsystem in a multi subnet or geographically dispersed cluster the nodes that you will join in the window server failover cluster don't necessarily have to be connected to the same disk subsystem I mean come to think of it if you're if one node is in the United States and the other node is in Canada there's really no way for them to be connected to the same disk subsystem the approach is to make sure that your storage subsystem supports block level replication which means a block of storage on one of your data center is getting replicated to the other data center that fools the operating system to think that it's looking at the same disk subsystem but in reality the blocks are getting replicated from the day between the data centers and that's what I'm using here the reason I want to make sure that my failure of a cluster of allocation wizard succeeds is based on my experience a lot of storage are not properly configured especially when dealing with multi subnet clusters and this is important you wouldn't want to create the cluster if there are issues with a storage and just like in a previous iteration of the fill of cluster validation wizard in my standard failover cluster this will take time depending on the number of nodes the sizes of the storage that you want to use for this cluster and in this case since the server's aren't two different network subnets the traffic between network subnet number one and network subnet number two so my favorite fellow foreclosure validation wizard is complete let's take a look at the report to see what we have here looks like everything is doing well inventory network storage system configuration based on my experience I almost always have issues - its storage depending on how its configured so I strongly recommended you fine-tune your storage configuration to make sure that they support multi subnet or geographically dispersed clusters close this and I will create my cluster based on those two nodes if you look closely I now have two IP addresses one for my production data center which is the one 7 2016 7 8 and my dr data center which is the 197 at 160 Network subnet this is how Windows now sees your cluster you're working with nodes on different data centers and it's providing you with an option to provide IP addresses for both network subnets keep in mind that if you will be dealing with cluster nodes on more than two network subnets the number of virtual IP addresses will be the number of the network subnets in this case I only have two you would have 3 Network subnets you would have 3 virtual IP addresses and because I'm not gonna guess the values for this I will go back to my cluster preparation checklist when cluster 2 I'll use these two virtual IP addresses 16.0 at 2 1 1 and 1 i 2.16 a dancer that 2 1 1 when the cluster 2 I'll use 2 1 1 and I can ignore some of these it's detecting some of the some of the IP addresses that I have now I use the one 97.1 6/0 subnet for my heartbeat so I'm not gonna use that I'm only gonna use one seven 2.16 and 192.168 next based on a virtual IP address that I provide it will create the cluster in this case the Windows Server failover cluster with winning cluster 2 as the name of my virtual server and these two IP addresses going back to our lesson on failover clustering fundamentals it will create its corresponding active directory object and the DNS entry in this case it's not just going to be 1 DNS entry but rather two DNS entries I'll click Next to create a cluster and again as I mentioned this will go out to Active Directory checks if this object is already there if it is it's gonna throw an error if it isn't it will create the virtual computer object and its corresponding DNS entry with those two virtual IP addresses this will form the foundation of where you would want your sequel server instance to run on top of Windows Server 2008 has supported running clusters that span geographical locations or multiple Network subnets but sequel server 2012 was the first version of sequel server that natively supports multiple Network subnets and this is why you've probably seen in the article that I was using Windows Server 2008 would sequence Server 2012 so the cluster is created there were a couple of errors this number 1 could not be brought online I'm ok with that this one in disc 5 go ahead and finish and the cluster is created so now I have a window server failover cluster with storage so two of the disks I've got like three disks in there cluster disk one two three four and five if I look at plus or disc one and go back to my disk management disk 1 is reserved well this is supposed to be a local disk this is where temp TB it's supposed to be right so I am going to exclude that this is one thing about using geographically dispersed clusters with sequel server you can choose to store temp TB in the sand drive or in the shared storage but in this case I wouldn't want to be replicating temp TB so I will exclude this yes I don't want this to be included in my cluster and cluster disc 5 which in my case hmm I don't have closer disquiet so I'm good going back I'm gonna bring this disc online and notice this is actually a local Drive so let me just mark this drive as Drive say Drive t for tab DB let's just rescan this ah it already has a drive drive II remember the demo that I did on a traditional fail of a cluster this drive if you intend to use local drives for temp TB has to exist on the other cluster nodes and the file format which means file structure the folder structure and the permissions have to be exactly the same refresh my disks so this is the local Drive disc two three and four our cluster drives disc two three and four our local drives I can remove dish number five there we go this two would be my data drive so let me change the properties of this disc make it even more many meaningful I'll call it f theta this one is for my backups so I'll call this H my black best practice has always been to rename cluster resources who has to not get confused when you're doing your cluster configuration or even managing your servers so let's call this G blog and if you notice I'm now starting to implement best practices in my storage configuration where I have a dedicated drive for data dedicated Drive for log of course local Drive for my temp TB and dedicated drive for my backups for my network I've got a couple of network here so I'll rename all of them this is for my production network adapter on one of the networks and this is for my dr same thing with this i'll call us heartbeat this one is for my production and this everyone I believe is for my heartbeat notice you have this option to configure this particular network adapter if you want it to be dedicated for heartbeat communication while I have a dedicated network for heartbeat I still kept the production network adapters to allow heartbeat communication in this case I've got multiple network communications on my cluster via my production network adapter and my heartbeat network adapter I've got no roles yet my nodes are prepared for I've got the disks configured I've got my network adapters configured I'm ready to go and install sequel server on top of this multi subnet Windows Server failed or cluster it's going to move into my sequel server installation Center and just like in the traditional way of installing a sequel server failover clustered instance I'll spin off a new sequel server failover cluster installation verifying some of the rules all the initial rules have passed I won't include the sequel server product updates because my service pack 1 is already a part of my media something that I didn't do in the previous demo because I want to show you how patching works in this case my installation media already contains service pack 1 besides I don't have connectivity to the internet so I'm gonna skip past this running the second roll check again I am prompted for the MS dtc clustered resource which is not available again i know that i'm not going to use cluster dtc for the sequel server instance so I'm okay with that warning microsoft.net application security windows firewall I'm okay with those warnings and I can go ahead again just like out what I mentioned in the previous demo if you are you if you are going to use the MS DTC or the clustered MS DDC for your instance make sure you configure that record next I'm using evaluation edition for this particular demo this just want to show you my product key click Next accept the license terms click next feature installation and just like in a previous demo I only need the database engine services for this particular installation so one be adding anything else I only want the class of the database engine for this particular cluster what else documentation and management tools click on next another rule check next it asks me for the sequel server network name again this will be the virtual computer object that this instance will represent in your network I'm not gonna guess the network name so I'll go back to my cluster preparation checklist in this case equal 2012 plus 2 and I'll use the virtual IP address 1 7 2.16 answer that to 1 & 7 I'm going to using a default instance for this particular database instance that I'm installing click Next on the disk space requirements dialog box similar to what we've done in the previous demo it's still going to ask you for the sequel server cluster resource group name I'll keep it as it is for the disk selection when I use G and H I wonder why my F drive is not available ah because my F Drive is use as my data as my corn drive now I want to pause for a minute here and give you some of the insights here it made sense for a traditional cluster you use a quorum disk that is because the disk is just in one data center it wouldn't make sense for the cluster to have a corm disk for corn witness because now you're dealing with two different nodes on different data centers which means you have to replicate that disk on both data centers so from production to dr i'll get back to this window and configure my window sort of fell of a cluster I'll click on my top-level node if I expand my cluster quorum resource note that my F Drive was used as my disk resource now I want to change this as I mentioned I don't wanna be using an expensive clustered storage for my disk witness this is where the file share witness option comes in very handy so I'm gonna change this similar to what we did before more actions configure cluster quorum settings I am going to change my cluster corn settings to not use a clustered disk but instead use a file share witness I'll select the advanced corm configuration in witness selection next I'll choose both nodes I'll allow the cluster to dynamically manage the assignment of node votes I will walk you through the process and explain further how this thing works when we go to do demo on geographically dispersed nodes that you will use for always-on availability groups in this case I'll keep the defaults I will select the second option configure a file share witness this adds a quorum vote or the file share witness now the reason I'm doing this is as I mentioned you only need one gigabyte of quorum or actually it's 512 megabytes for your quorum disk not an issue if both of your cluster nodes are in the same data center but now you're spanning geographical locations in different data centers I wouldn't Bonnie I wouldn't want to be replicating 1 gigabytes or 512 megabytes of clustered disk stored between data centers it's expensive I'd rather say that clustered storage for something that's more to me and that's why I'm gonna use the file server witness for this purpose file share path I'll use a file share path that's accessible to all of the nodes in my cluster and I want to make sure that this file share is hosted on the highly available file share maybe a clustered file share if you way if you may I'll click on next and next and configure so now I've changed my cluster corn setting from a quorum disk the traditional quorum disk that we've used in the past to a node in file share majority click finish and this would change my quorum configuration to note in file share majority quick hit refresh here for storage I don't need the storage for this cluster since I already have my file share witness so I'll take this drive offline and in my disk I'll bring this disk online because it's it's no longer being used as a file share with this so I will move this disc to my available storage so I right click on my drive and say remove from cluster group this makes the cluster drive available to my sequel server instance I really want that F drive to be used by my sequel server instance so I switch back to my installation click refresh and that will take quite a while in some cases I have to restart my installation process for that particular drive to be available so I had to restart my whole installation process for the changes to be taken effect click on yes so now my data drive is now available in my failover cluster installation we're going to select all three so these cluster drives will be dedicated for that particular cluster resource group be careful with this because if you intend to use multiple cluster drives you can't just remove them out of the cluster resource group especially if you have system databases and user databases on those cluster drives I'll click Mac's IP addresses I already have provided the IP address for this I want you to pay close attention to the list of IP addresses in the traditional failover clustered influence installation that we did in the previous demo you didn't see a lot of these options you're only provided with one network adapter and that will be used for this particular installation in this case I am only going to use my land vc-1 and reason that I'm getting to is because of my network adapter configuration I want to fix that so I'll go back here heartbeat I don't want to allow clients to connect to this network click on apply because again this is my heartbeat Network same thing with the other heartbeat network I don't want to allow clients to connect through to snapper so I've only left my public network adapters for mine yeah my public network adapters with that option to allow clients to connect to this network you want to make sure that you fix this before moving on with the installation go back to the insulation refresh note that I am now just provided two options the first one being is my domain controller one or my my data center one rather and it's corresponding network adapter next is my data center to with its corresponding network adapter I can't modify this at this point because the note that I'm working on the BS cluster 3 is in my primary data center that's the only network adapter I'm provided with I'll use one 7 2.16 for my virtual IP address for this instance I'll click on next the database engine and the agent service accounts are requested and again reminding me of the fact that when you go back to the previous demo that I did the order of the database engine and the sequel server agent service accounts are reversed when you're adding nodes be very careful especially if you're using different service accounts for the agent and the database engine correspondingly in my case I'm only using the same service account so that I don't have to worry about this like next and the database engine configuration dialog box I want to make sure that I am allowed I'm adding myself and this is admins role in this particular instance data directories I now have different folders provided for me the first thing that I need to do in this case is go back to my II drive I'll make sure that this is online my temp TB drive so I want to go back to my II drive create a folder because I want to store my temp TB in my local drive I want to make sure that I grant permissions to my sequel server service account so at my sequel server service account granite for control permissions on this particular folder it's the same thing that I will do in the other node when I initiate the installation process on that node so for temp TV I'm going to use the local drive EMS equal for my data directory probably using the F drive and I'll follow the structure that I had earlier FMS equal my log drive will be G and my backup drive will be H I'm highlighting a couple of best practices here where you're provisioning physical drives for your data file your log file your temp TB database and your backup files similar to what we encountered in the previous demo you you will be prompted with this message telling you that MTB database is being stored on a local directory we've already taken care of that we have temp TB being stored in the local drive and I want to make sure that when I add node ws cluster 4 to the sequel server instance I will have the drive letter in the folder and the path and the permissions the same way that I did with this particular node 1 yes click Next last rule check the Flex and run the installation as I mentioned I've already used the sequel server 2012 wood Service Pack 1 installation media for this particular demo so I don't have to patch my nodes in and install service pack 1 I may have to install cumulative updates or security patches but again going back to the previous demo you start with the node that's not running the resource group patch that failover and patch the other node I'll pause the video and come back when this installation complete so the installation is complete everything is looking good so now I have a working sequel server clustered instance not highly available because I only have one no gloves if I go back to my cluster and I have the MS sequel server resource group and in that resource group I've got all my cluster drives my virtual IP address in my virtual server name I could call a clustered resource group and this will show me all of my resources in that group again this is nothing different from the traditional sequel server failover clustered instance where you have your virtual server name virtual IP address right now I only have one virtual IP address when I add the other node I will be presented with two virtual IP addresses I got my storage my sequel server clustered resource and sequel server agent cluster resource again you can look at the dependency report or in this case I want to look at the sequel server dependency report as a reference one thing you've seen in the previous demo on a traditional sequence or failed or clustered instance is that everything uses the and logic condition the and logic condition simply means that all of the resources have to be online before one resource that's dependent on them go online when I add the other node you would start seeing or logic condition which means one or another resource can go online in order for this particular resource to go online so I'm done with WS cluster three I'm going to WS cluster four and add this particular node called installation and again similar to the previous demo I'm going to add a node do we see what sort of failover cluster I'm just going to go through all of the pages because they're exactly the same pages that we've seen in the previous demo what I would like to focus on for this particular adding of node is when you're presented with an extra page where it asks you for the virtual IP address of this particular network subnet okay and again skipping past the page where it asks from my product key accept the license terms I'm not going to include sequel server product updates because my again my nodes are not connected to the Internet and just for me not to get confused so I've connected to WS cluster four so I'm using my WS cluster three session to connect to W so closer four because it's on a different network subnet my main workstation does not have access to that particular network subnet and running the setup support rules check I still see the distributed transaction coordinator warning Oh click Next not in this case it already sees the sequel server instance name it sees the clustered network name that's already installed on this window server available cluster so we're just gonna add this specific node this was what I was mentioning about the cluster network configuration in the traditional sequel server failover clustered instance where the nodes are in the same data center in the same network subnet you won't even see this page but in this case since this node that I'm adding WS cluster for is on a different network subnet it's asking me for a virtual IP address for this specific subnet so I'm going to select ipv4 and I'll use 192.168 the 0.217 for this particular network subnet click Next and you will be prompted with this particular message the sequel server detected that there are multiple subnets now one major consideration when you're dealing with multiple subnets or a clustered spans geographical locations or multiple subnets is making sure that your networking stack is well defined and well-configured so you want to talk to your network administrators on how this is properly configured it also tells you the resource dependency using an or relationship I'm gonna show you that later when we go back to the failover cluster manager and see the dependency report I'll just click on yes the sequel server service accounts as I was mentioning the database engine comes first before agent so be very careful with that I'm just going to provide passwords for my service accounts go to the error reporting page click next find a rule check before the note is added summary of all the changes for adding the specific node and install again this is gonna take quite a while so what I'll do is I'll switch back to WS cluster 3 and show you some of the network properties that we need to tweak as far as the cluster resources are concerned so you're seeing a PowerShell command that I'm gonna use to take a look at a different cluster resources I'll start with the Colet get cluster resource and I want to take a look at the different resources in my cluster so this is a list of the different resources in my cluster I've got my cluster IP my IP address cluster name my IP address - for sequel I haven't I don't have my other IP address or my cluster virtual IP address yet it's gonna come into the cluster once the node has been added successfully but what I'm really concerned and what I want to pay attention to is this particular network name in a multi subnet or geographically dispersed clusters since you're gonna be dealing with two IP addresses one for your production data center and one for your dr data center you have to modify how your network would respond in this case the network name will be registered to my dns so I have to modify the properties of this specific network resource I'm gonna get grab this command I want to list all the cluster parameters for that specific network name resource I'll paste that I don't want to make sure that I copy this there we go so I'm running the get cluster resource parish of command let passing the name of my cluster resource in this case I'm interested with the sequel network name which is sequel 2012 cluster and I want to list all of the parameters for that specific cluster resource couple of things to focus on here first off register all providers IP with sequel server 2012 the default value is 1 what this parameter means is all the virtual IP addresses that I've configured for the sequel failover cluster will be automatically registered in my DNS why is that a constraint well if this property is set to 0 the only time that the virtual IP address gets registered in DNS is when that virtual IP address is brought online on that specific network subnet take a bit this way once i'm 2.16 that 0.217 is my virtual IP address for my production data center my 192.168.0.1 7 virtual IP is not gonna get registered on my dns server until i fail over my entire cost a resource group or even just the resource name again the resource group is gonna get failed over that is going to affect how your client or applications connect to the cluster resource name let me think about it the default DNS client cache is 20 minutes if I don't register my virtual IP addresses or all of the virtual IP addresses in the DNS my client might not have that DNS value with its corresponding virtual IP address in its cache again the default is 1 so no need to modify that the next property that I am concerned with is host record TTL this is in seconds so 60 seconds one minute 1200 seconds 20 minutes why is this of concerned again imagine your client applications caching the DNS entries if it takes 20 minutes for my client to flush the DNS cache and request DNS increase my DNS server that will affect my application failover time it also means that even though my databases have failed over in less than a minute my client applications still won't be able to connect to my databases and that would affect your service level agreement and your recovery objective that is really not a database issue it's a DNS and networking issue but since it's running on the cluster and sequel server depends on that your application may think that because it can't connect to the database server because of the DNS caching it will think that the database is down so we need to change this value to something that's relevant for this specific DNS entry or just network resource name I'm going to change that value to something like 300 or 5 minutes so I'm gonna set the parameter value and notice that I have a PowerShell script in here changes the register all providers IP parameter value to one just in case just in case I haven't had the value set the one but in this case I already have it to set the one and I'm gonna change the host record TTL value from 1200 to 300 so I'm gonna copy this command and run it on my cluster now you can run this powershell commandlets on any of the nodes in your cluster in my case I just feel like running this on my ws clusters 3 node since the other node is still finishing up the add node configuration for my sequel server favorite clustered instance paste that so initially I have 1200 I'm gonna change it to 300 says the properties were stored but not all changes will take effect until the network name is taken offline and then online again we're gonna do this as part of the failover test where we will take the sequel server resource offline move it to WS cluster for that we'll take the cluster race to a network resource named offline and bring it back online we can rerun same query or PowerShell script know that my host record TTL is now 300 which was changed from 1200 you might want to talk to your DNS administrators on this specific value what this means is that all your applications will have to request DNS records from your DNS server every 5 minutes if that's something that you think is very aggressive again talk to your dns administrators about the right value for this without blowing up your recovery objectives and your service level agreements let's get back and check WS cluster for still running I'm gonna pause the video and come back to this when the whole process completes and then we'll do two failover and failback tests so the ad failover clustering mode process is complete everything's looking good here now that's done let's go back to our favorite cluster manager and do a failover test but before we do a failover test I want to focus on the virtual IP address note my clustered resource name or a clustered Network resource name initially I only have or I only had one IP address in this list now I have two IP address one for my once m2 dot 16 network subnet and one for one my 192.168 network subnet note that only one virtual IP is online at any given point in time you can't bring both virtual IP addresses online at the same time again talking about how DNS client works if both IP addresses are stored in cache and decline requests for that specific IP address if one of the IP address or if both of the IP addresses are online the first one that responds gets to be the first one at my application connects to now what if that particular virtual IP address does not have the resource in the resource group my correct my request would fail that's why the virtual IP address for the other network subnet is not gonna be online only one virtual IP address will be online at any given point in time and this is where I want to point out the or logic condition on Magnus II not the sequel server cluster resource but my network name resource one showed its dependency report for that this is where the or logic condition now appears in the past it was just the and logic condition see here it says the ampersand represents and and the whatever that symbol is represents or and what this graphic simply means is any of this IP address or this IP address any of these two can be online before the network name goes online that's the or logic condition contrast that would end where both have to be online before my network name can go online let's take a look at the dependency report for sequel server and see a combination of the and and the or logic condition the sequel server service or sequel server clustered resource still has the and logic condition notice all the drives tribe G F and H they all have to be online prior to sequel server going online which means if any of these four is not online your sequel server resource will not come online unlike the network name resource I've explained earlier any of these through virtual IP addresses can go online for the sequel a sequel sort of network name resource to go online this concept is very important when you're dealing with troubleshooting failing over and failing back and why one of the resource is not going online the dependency report will give you that insight as I mentioned in previous demo copy this dependence report on a word document print it out attach it to your run book so that any anybody on your DBA team can have a look at the dependency report to a system in an understanding how this whole thing works now that's done what we're gonna do is we will failover now before I do the failover remember temp TB is stored in my local drive which means on WS cluster for or on all of the nodes in my cluster I need to make sure that that folder exists I'm going to go back to the BSC cluster for I'm going back to my temp DB drive and again this is a local drive I'm gonna create a folder named mssql grant the sequel server service account full control permissions on this particular folder again add a sequel server service account and grant it full control permissions if I don't do that failover will fail I won't be able to move my sequel server resource group from WS cluster three two WS cluster four because my temp DB database can't be created going back to the lesson on protecting your seat system databases if you don't have to temp DB database your sequel server instance is down so that's one thing to really keep in mind I want to move this to node 4 or node 2 which is WS cluster 4 well that there and looking at how the failover process works the dependency depended affined how the failover process works sequel server agent goes offline first and then the sequel server service goes offline then all the other resources that don't have any dependencies look closely at the IP address the 192.168.0.1 seven IP address goes online and that's when the sequel 2012 cost to virtual computer name or the net network resource name went online so now if I go back to my PowerShell script and rerun the exact same parameter or a query earlier I now have two IP addresses for my sequel server virtual server name these IP addresses pertain to the 192.168.0.1 7 and the 1:7 2.16 that sir that 2 1 7 IP addresses earlier this wasn't there because my ad node process is not done yet and it wasn't able to register the new virtual IP address going back to my favorite cluster manager I can then go back and move this to WS cluster 3 it's interesting watching how the resources are being turned off line or being brought offline and back online it explains how the dependency report works so in this demo you've seen me how you've seen how I configured a window server failover cluster that spans multiple subnets or commonly known as geographically dispersed clusters you've seen me installed a sequel server failover clustered instance on top of a geographically dispersed cluster destined to failover and failback I know we're not done yet here because there's still a lot of things that I need to configure like for example making sure that my preferred owners are properly set and that my priority is set to high but I know that my failover and failback test works once this is is configured I can go back to Active Directory look at the Active Directory objects I want to open up Active Directory users and computers and check the servers if the virtual server name or the virtual computer object has been created in my Active Directory so I now have when a sequel 2012 cluster to the foil failover clustering network name account has been created and if I look at my DNS server the DNS entries for both IP addresses are now configured sequel class a sequel 2012 + to have two entries one for the one seven two that's sixteen that 0.217 virtual IP address and the 192.168.0 that to one seven IP address this is how it affects your DNS and your Active Directory so I strongly recommend that you take a look at the article that I wrote on MSE cool tips comm it walks you through the exact same process that I did the only difference is now I'm working with Windows Server 2012 for this demo whereas the article watches the process of using Windows Server 2008 r2

Channel: Edwin M Sarmiento

Views: 12,467

Rating: 4.8518519 out of 5

Keywords: Microsoft SQL Server (Software), SQL Server 2012, SQL Server 2014, failover clustering

Id: bEp0rmy1314

Length: 57min 1sec (3421 seconds)

Published: Mon Jul 06 2015