Installing a SQL Server Failover Clustered Instance

this is the demo that accompanies the lesson on sequel server failure clustering fundamentals what you're seeing here is the diagram of the basis of what I'm going to do in my demo so keep this diagram in mind as I move along standard to node Windows Server failover cluster and I'll be installing sequel Server 2012 on top of it what you're seeing here is the cluster preparation checklist that I've shown you in the lecture portion of this topic I strongly recommend that you prepare everything that you need prior to installing and configuring a sequel server failover clustering instance it makes the whole process a lot easier especially if you plan ahead I have the first tab here the list of servers that will act as nodes in my Windows Server failover cluster select the Windows Server and versions and editions the host names capacity for CPU and available memory and which domain these servers belong to in a Windows Server failover cluster than the server nodes have to be a member of the same Active Directory domain you see me using Windows Server 2012 datacenter Edition although with Windows Server 2012 you can use Standard Edition for your traditional Windows Server failover cluster this is unlike in previous versions of Windows 2008 2003 where you have to use the the Enterprise Edition for spinning up a Windows Server failover cluster in my network tab I have all the IP addresses tcp/ip configuration for my entire cluster I've got my public network IP addresses subnet Gateway for my public network I'm using I scuzzy for my shared storage and that's why you're seeing I scuzzy IP addresses when cluster two will have its own virtual IP address now imagine that these two machines are in the same data center in the same network segment and that is why you're seeing IP address in the same network subnet range in the next video I'm going to show you how you can provision geographically dispersed clusters where nodes are in different data centers but in this case since I'm only dealing with cluster nodes in the same network subnet I only need one virtual IP address this will be the virtual server name for my standard sequel server failover clustered in sense or a traditional failover clustered in sense and it will require its own virtual IP address as well for the shared storage tab I'll be provisioning a corm disk and my sequel server data disc these are shared storage and I'll be using local storage for temp DB something new in sequel Server 2012 unlike in previous versions of sequel server where everything has to be on a shared drive now this is not best practice the best practice is always provision independent Lunz for your data drive or your data files your log files your backups but again I'm just highlighting the fact that we need to have shared storage to install sequel server failover clustered instances on a cluster and services tab I have my clustered application in this case equal server failure cluster with its virtual server name and virtual IP address I'm using Enterprise Edition for my traditional failover clustered instance but you can use standard edition as well with a limit of two nodes for that failover clustering instance the reason I'm using Enterprise Edition for this purpose is later on I might introduce always-on availability groups for this instance and make this as a replica for that availability group but let's worry about that later for now I just want to spend up a two node sequel server failure clustered instance and then I have my service accounts these are the service accounts that I'll use for my sequel server service and sequel server agent service so I have access to WS cluster 3 and ws cluster 4 the first thing that you need to make sure of is enable the window server available clustering feature on all of the nodes of your favorite cluster now to do that you click on the add roles and features wizard click Next until you find the select features option note that I've already enabled the failover clustering feature and as I mentioned even before you create the Windows Server failover cluster this feature has to be turned on on all of the nodes I've also installed if you notice the dotnet framework 3.5 and the reason I already did this is it's a prerequisite for installing sequel server 2012 so I've already done this and I've already configured storage for both of my cluster nodes now this is not a course on how to configure your storage I just made sure that my nodes are already connected to my shared storage if you're a sand engineer as well there are different ways to connect to your shared storage and of course there will be different methods to connect to your shared storage depending on what type of shared storage you're using in this case since I'm using I scuzzy storage I'm using iSCSI initiator console to connect to my shared storage my shared storage is already provisioned and you can see it in my disk management console so drive queue and drive F will be my shared storage and these are also accessible to ws cluster 4 which is the other node in my cluster drive e is a local drive and like I said I'm going to show you how to install temp DB in a local drive as compared to previous versions of sequel where you can only put them DB on shared storage since I've already done that the next thing that I need to do is configure my window server failover cluster so we'll can be using the failover cluster manager for this purpose once my favorite cluster manager is is up and running I will be validating my cluster so this is where the validate configuration wizard comes into the picture you run validate configuration for new cluster preparation or if you're adding another node or replacing Hardware in your cluster just want to walk you through the process of running the failover clustering wizard so you see the splash screen it'll ask for the servers that you want to join as nodes in this cluster in this case ws+ there's three so I'm going to add both ws clusters three n WS cluster four in the validate a configuration wizard and this is one of the things that we talked about in the lesson portion we have to do this in order for your servers to be completely supported by Microsoft click Next by default all the option run all tests recommended is the one selected but I want to show you two different tests that this wizard will run so I'm going to click one only the tests I select part of the test will be inventory it's going to check your storage it will check your system for BIOS information system software it'll check your network for binding order the IP configuration it'll check your storage whether or not your storage are indeed supported for Windows Server failover cluster and then system configuration it'll validate Active Directory configuration some drivers software patches and so on and so on if you're building a new cluster I strongly recommend that you choose the first option run all tests the only reason I clicked on one only tests I select is just to show you what different tests are being run now if you add a node you can choose to run only the tests that you want and validate the cluster based on that but since this is a new cluster I'm going to run all the tests and this is where the validation testing will start so I'm going to click on next and the testing well run now this will take quite a while depending on the number of drives that you have your shared storage depending on the number of nodes that you have that you would provision for your cluster in this case I only have like two drives and two cluster nodes so I'm going to pause the video and return when this entire validation process completes so the validated configuration wizard is complete if you look closely at my summary icon it just tells me that everything ran successfully if there are issues with running the configuration wizard you'll see a warning or an error icon in the summary on the upper left-hand corner you can view the report or the detailed report of the different tasks and tests that the validation wizard ran and again this will show you a summary in some cases you might see under system configuration a warning telling you that the patches on one node is not exactly the same as the other node again if these are warnings that you understand you can skip them if you're seeing errors you can't create a Windows Server failover cluster you have to fix the errors first rerun the cluster validation and then move on use this as part of your documentation you can copy this off save it an award document put in your run book as a reference for failover cluster validation now when I click on the finish button notice that I have the create the cluster now using the validated nodes checkbox by default this is checked that when you click on finish it will now ask you to provision information about the window server failure cluster virtual computer object name or virtual IP address so let me click on finish and this will fire up the create closet wizard click Next on a splash screen it will ask you for the virtual computer object name of the window server failure cluster in this case we know it's windows will cluster to and want to refer back to my Excel spreadsheet I know that my one cluster two server will have a 90 address of 1 7 2 dot 16 add 0.21 1 notice that it also detected that you only have one network subnet and does asking for only one virtual IP address click on next to create the Windows Server failover cluster of course it's going to ask you for the other information like the cluster name the nodes that will be a part of this cluster and a virtual IP address notice that you have this check box add all eligible storage to the cluster by default it will add all of the shared storage into the new window server failover clustering you don't you might not want that but I would strongly recommend it you only present the storage that you want including your cluster on those notes that the cluster create class or wizard only considers those storage as part of the cluster click next and this will create the Windows Server failover clustering to my active directory machine here and show you that I only have one cluster one which is already there use it as an example in my Active Directory users and computers console under the computers folder once the Windows Server failover cluster is created you will see one cluster to end the list and I'm going to refresh this real quick and now you see when cluster 2 and the list of machines in my Active Directory domain as I mentioned in the lesson when you create a Windows Server failover cluster and even a sequel server failover clustered instance the virtual computer object will be created inside Active Directory same thing with DNS I don't have one cluster 2 yet here when I hit refresh of course this assumes that you have an Active Directory integrated DNS zone so now I have one cluster 2 in the list as well with the virtual IP address that I've specified in my Windows Server failover cluster most people ask what are different permissions that I need to create a Windows Server failover cluster and install a sequence or a failover clustered instance well for one you have to have a create computer object permission in your active directory so you have to talk to your Active Directory domain administrators for that let me go back to my when WS cluster 3 node and this is where the create cluster wizard has created a cluster with the corresponding virtual server name and a virtual IP address again you can click on view report to see the different tasks that the cluster has done for you and again similar to the failover clustering wizard report I strongly recommend that you take this and paste it in a Word document and include it in your run book for reference let's click on finish we now have a Windows Server failover cluster inside a failover cluster manager the cluster will now be managed via failure cluster management or she can also use Windows PowerShell for managing the cluster what you'll see in here is warm configuration you have a node in disk majority the traditional node in disk majority for a two node cluster and a shared drive acting as a quorum drive you can expand on the cluster core resources when cluster two is your virtual server name and your virtual IP address cluster storage that is used for for this particular cluster is cluster disk - it's not that intuitive it's just going to use the default name so cluster disk - cluster disk three after doing so I strongly recommend that you rename storage appropriately so that you don't get you don't get confused with these so disks I have cluster disk 1 and cluster disk 2 it's kind of hard to see what they are but in this case since I know that my 4 gigabyte will be my sequel server cluster drive cluster disk 2 is my quorum drive so why don't I change the properties of my cluster disk and rename them accordingly apply and this of course will be my sequel server drive the same thing with your network if you look at this closely clustered Network one cluster Network - not really really that intuitive but because I've renamed my network adapters from within my Windows Server nodes it's easy for me to identify with which networks these are so I'm going to rename them accordingly and say this is a heartbeat Network and notice that I have the option to either allow cluster Network communication this network I'll use it I'll use the default options this one is for my I scuzzy and notice that it did select that do not allow plus circuit network communications because it's smart enough to figure out this is not available on the network I'm using I scuzzy for this as well as my public network so I'll probably name this and and notice that I have the option to allow clients to connect through this network it's smart enough to see that this particular network adapter is connected to my public network connected to my Active Directory and this will be the network adapter that will be used for application connectivity to your cluster click ok going back to the cluster configuration I'm using node in this curity there are cases when when dos are available cluster will see this particular disc a list of disks and we'll just pick up the first disc that it's see so what if you don't like that you can go ahead and configure say more actions configure cluster Corum settings and you can change the disk that you want to use as the corm disk say add or change the corm witness configure a disk witness again the assumption here is you didn't really like the idea of the cluster using the other drive because what we only need like 512 megabytes for your Quorum drive but it picked the 20 gigabytes or the 400 gigabytes drive so you can change it by doing so and I can switch to the sequel drive or the other drive that you want to use for your quorum disk but in this case it's smart enough or let's just say I know that this is going to happen so I added quorum disk first before adding the data disk now that's done you can verify everything if they're working the storage this is what I was mentioning earlier about the different names rolls started out as resource groups in earlier versions of Windows change to services and applications in Windows Server 2008 and now they change it to roles currently we don't have anything yet in this particular cluster but I would strongly recommend it once everything has been configured because now you have a working Windows Server failover cluster you can now access this cluster by using one cluster - and start failing over and failing back maybe shutting down shutting down one of the nodes or unplugging network adapters and in validating that this cluster is indeed highly available before you even install sequel server once everything is done I can now go ahead and install sequel server notice I don't have my clustered drives here I only have my system partition my temp DB which is my local drive if you look at the disks they're owned by WS cluster for now I can move these say move this to or or one of the things that you can take a look at it show the dependency report we're going to dive deeper into the dependency report once I have everything up and running with sequel server installed as a cluster resource on this particular Windows Server failover cluster in this case I don't really have any dependency at all so I can try and show you later on how this entire dependency works so now let's go ahead and install sequel server in this particular cluster I'm using the RTM version of sequel server for this particular installation so that I can show you how to patch the nodes in a clustered sequel server instance you do have the option to download and install the sequel server 2012 installation media would Service Pack 1 included and you can also use the product updates feature that's new in sequel Server 2012 and again only reason I'm doing the RPM version of the installation media is I want to show you how you can configure patching or how it can perform patching in a clustered sequel server instance let me minimize this robot because I don't need them and wait until my installation media starts so on the installation window kicks in I'm going to take a look at the installation tab the usual option that we select when installing sequel server standalone instance is the first option but since we are going to install a sequel server available clustered insulation we have to choose the second option just be aware of the fact that you can't convert a standalone instance to a clustered instance and vice-versa so you have to be very careful when you're doing this insulation so select the new sequel server failure for cluster installation SOTA setup support rules window kicks in and checks for the different configuration making sure that everything is set and ok before moving on with installation process once that's complete click on OK and again you will be presented with different options and maybe different settings that you need to resolve prior to moving forward if for example dotnet 3.5 Service Pack 1 is not installed you will this will be reported as an error so you have to fix that first before you move for it's one of the reasons why I've added the dotnet framework 3.5 and I shown I've shown you that when I was adding the failover clustered clustering feature in Windows now this is a new option in sequel server 2012 as I was mentioning earlier if you are not using the latest installation media with sequel server 2012 Service Pack 1 this is a new option to choose now what this thing does is if your servers are connected to the internet it will go out to Windows Update Microsoft Update checks for corresponding service packs cumulative updates and security patches for this particular version of Windows and downloads them and installs them together with the installation process in this case I don't have my machines connected to the Internet so I'm skipping this portion click Next still running some checks now this this portion will check the other tasks that you need to fix as part of your setup you probably notice this warning over here on the distributed transaction coordinators I mentioned I know that I'm not going to be using the distributed transaction coordinator for the sequel server instance so I have not configured that Windows Firewall if you have a corporate policy to turn this thing on just make sure that you allow ports port 1433 traffic and 1434 for your cluster just scrolling through the different warnings and again similar to the previous set up support rules check you can't get past this until you fix some of the errors I'm only ignoring the warnings because I know what they are and I know that I don't need to resolve them so I can click on next now of course I did skip past the page where I provide my product key you wouldn't want to see my product key do click Next click Next in the sequel server feature installation for this clustered instance I only need a database engine so the first option is equal to the feature installation by default is selected and when I go to the next page I'm presented with the different options I like to keep my sequel server instance this lame and mean and with minimal services and components running so since I'm only going to be using this for the database engine I will select the database engine services by default it will select the replication and full text and somatic extractions search I'll also include documentation and management studio in my installation again one of those role checks it asks me for the sequel server failure clustered instance name this will be the virtual computer object virtual server name that will be created in Active Directory so I'm going to provide this network name and again since this is a default instance I'm only going to provide a virtual server name if it would be a named instance I can choose to select the named instance option provided instance name but again this is the first instance in this particular cluster I can choose a default instance click Next on the disk space requirement and the cluster resource group page it will ask you for the resource group name that you would see in the roles portion in your available cluster manager again resource group is what I prefer calling it but now it's called roles so you have by default provide are provided with the sequel server MS sequel server be intuitive good naming I choose to use a default name or the resource group name because this is the only sequel server instance that I will run in this cluster and don't get ticked off by the drop-down list you can actually edit this if you want to and use a different name this page displays the different disk resources that are visible on my windows are available cluster not the chorim disk is no longer a bit available because it's being used as my chorim drive but the sequel drive F Drive is still available and I can choose to select that now if there are other shared disks available in the cluster you would see them here as well and you can select those disks that you want to use or not use with a sequel server instance in the cluster network configuration page you'll be selected you'll be presented with this option and you can choose to type in the virtual IP address and this is the value that you see me include in my cluster preparation checklist spread shape now since again as I mentioned this is a cluster with nodes in the same data center in the same network subnet you'll only see one IP subnet range here if you have multiple nodes in different Network subnets you would see multiple IP addresses for the virtual virtual server name in this case I only have one network subnet so I only need one virtual IP address and the next video demo I'm going to show you where a cluster with multiple nodes in different network subnets will present you with a page with multiple options to fill in over a various virtual IP addresses for different network subnets in the server configuration tab or page this is where you provide a sequel server service account and I just want to make sure that I copy this I'm using the same service account for my agent service in my database engine the things I want to point out here is the sequence of the services that are presented to you in this window kind of annoying you'll see agent and database engine in that sequence but when you start adding nodes you'll see database engine first before agent why am i highlighting that because there may be cases where you want to use a different service account for the agent and the database engine in this case it doesn't really matter because I'm using the same service account but again in case you choose a different service account be very careful of what particular service account you use for that engine and you'll see that later when I start adding nodes not to make the startup type for both services they're configured as a manual and the reason for that is the window server failover cluster will take care of when the services will stop or start so I'm going to keep the dos as they are collation I'll keep it as it is depending on what type of collation that you want from the sequel server instance for example if you want to use this clustered instance for your SharePoint databases you might want to use the specific collation for this instance I'll click on next and the server configuration a tab I want to make sure that I can manage this instance and so I'm going to add my domain account my data directories tab I'm provided with a different directory now for the temp TB as I mentioned I want to store my temp TB in my drive and this is a local drive when I click Next and I want to make sure that everything is correct so my data directory is on the F Drive whereas my temp TB data case will be on my local Drive and as I mentioned you will be prompted with this message saying you have specified a local directory as the temp TV data or log directory now keep in mind in previous versions of sequel server you only have the option to store temp DB in the shared drive this is new in sequel server 2012 but I want to point you out to this specific message it says to avoid possible failures you make sure that the same directory exists on each cluster node and make sure that you grant read/write permissions to the sequel server service this is something to keep in mind and I'll show you that when we start adding the extra node into this cluster so I'll click yes click Next on the error reporting page again the last cluster installation rules page want to make sure that everything is fine click Next and the installation goes so I'm going to pause the video until this entire thing completes and I'll come back and install the extra node WS cluster 4 and add it to this particular sequence or instance so the installation is complete I could click on close and verify the installation notice that my roles tab in my window server failover cluster manager now has the cluster resource group that we configured as part of the installation I wanna take a look at some of the information on this specific cost resource group I got my summary my virtual IP address in my virtual server name resources and this is where I start explaining the concept of dependencies so I've got my virtual server name in my virtual IP address my storage my sequel server server service and my sequel server agent these are all clustered resources inside this clustered resource group and I want to quickly right click on sequel server agent and display or show the dependency report something to really understand how dependencies work and very helpful when you're doing troubleshooting for anything that's running on Windows Server failover cluster including but not limited to illusory fill a sequel server failover clustered instances so take a look at this graphic this graphic represents my dependency report I know that my sequel server agent is dependent on this equals server clustered resource so in order for me to start a sequel server agent I will have to start a sequel server service first in this case it's a cluster resource my sequel server clustered resource is dependent on my physical disk the sequel disk and my network name it's an end condition in this case which means I have to have both my network name and my cluster that disk online before my sequel server service goes online same thing with the network name which is dependent on the IP address I would strongly recommend that you copy this take this entire report again copied on Word document print it out and include it in your run book I do not have my second node configured yet so in this case if you look at my properties I don't have preferred owners yet I'm going to walk out work on the preferred owners at this point but since I don't have the BS cluster for ready I can't add it in my preferred owners list so I'm going to switch to WS cluster for and start the installation so I'm going to open up my installation media same process but this time I'm going to use the third option to install or add node to an existing sequel server available clustered instance now you'll see the same installation process here except this time we'll be choosing the third option to add a node to an existing sequel server failure cluster you're going to do this on all of the nodes that you want to be a part of your sequel server or clustered instance so I'm going to choose that there will be the same screenshots and same windows the same dialog boxes that you'll see in this process except that they all pertain to adding a node to an existing file or a clustered instance the same setup support rules again I just get past the page where it asks for my product key click Next again all not include sequel server product updates because this server also doesn't have any connection to the Internet besides I don't want to have one node on one version and another node on a different version I want to make sure they're all uniform as far as version numbers are concerned and I can ignore this because again it couldn't connect to the Internet same rule check that you've seen when I was installing available clustered instance on the first node same warnings I would presume distributed transaction coordinator Windows Firewall and my microsoft.net application security notice that it already sees the instance name it's running on my existing window server failover cluster the cluster network name is sequel 2012 plus 2 so all this is doing is simply adding WS cluster 4 to the existing cluster cluster network configuration page detects the virtual IP address that we've provided when we were installing the sequel server failover clustered instance we no longer have to do anything at this point but again if this machine is on a different network subject you'll be provided with another IP address line and you have to provide provide the virtual IP address for that network subject this case will just have to click Next this is what I was mentioning earlier I want you to pay attention to this notice the sequence of how these services are arranged in the previous node where we started instant and installing the sequel server failover clustered instance the sequel server agent came in first before the database engine if again you're using different service accounts for the database engine and this equals to root agent service be very careful of this in my case they're the same I'm just going to provide a password for the sequel server service accounts click Next click Next on the error reporting page last roll check again make sure that everything passes the rule check click Next and proceed with the installation this will also take quite a while so I'm going to pause the video and come back once this is done and the add a failover clustering ode process is complete successfully completed we can now verify the insulation now before I do that one thing that I need to do is to make sure that I have a new folder in here called MS equal remember we configured our temp DB database to use the local II drive since I have the same drive letter I want to make sure that I have same drive letter on both nodes I have to have the right folder the right path on which to create the temp TV database and I also need to grant a sequel server service account read/write permissions on this folder so I'm going to add the sequel server service account grant full control permission you can do modify if you want to the last time I did this modify it wasn't enough so I'm usually grabbing this granting this service account full control permissions and this is part of the failed process test thing which when you failover the temp DB database it's going to get created on this particular folder now I want to switch to WS cluster 3 which was the cluster node that I initially had the sequel server cluster instance run do a quick refresh now I can configure this resource group and make sure that I have the appropriate permissions and configuration for that resource group right-click on the resource group click on properties want to make sure that both nodes are my preferred owners I want to make sure that my priority is set to high this is useful when you're running hyper-v in this cluster but in this case it's the only resource that I'm running I want to make sure that it is configure your configured with high priority click apply now I want to point out how the dependency works by moving this resource currently being owned by AWS cluster 3 to cluster 4 and as I'm moving the resource group I want you to pay attention to the different resources and their dependencies and how they behave so when I click on ok the sequel server agent is first taken offline then the sequel server service is taken offline and then the sequel storage the F Drive is taken offline and then brought offline note that the virtual server name waited until the IP address or the virtual IP address went online before it became online and same thing with the sequel server service it waited for the virtual server name to come online of course this was already online before the virtual server name became online before it was brought online and so that's this is where the dependency comes in going back to the dependency report that we were looking at now my resource is owned by WS cluster 4 and you've seen how the behavior works as far as dependencies are concerned I want to go to WS cluster 4 and show you that now my temp DV database is now created on on the II drive on the MS sequel folder now I can do the exact same thing and failed back to WS cluster 3 so I've created my folder I granted permissions to the sequel server service I've managed to do a failover test and so my application or my sequel server clustered instance is now properly configured well as far as the cluster is concerned of course I'm going to move this back to WS cluster 3 again notice how to behavior with the agent the service the drive the virtual IP address and the virtual server name and how they behave the reason I'm highlighting this is it is very important to understand how the whole dependencies work and how the failover and failback works in a clustered environment because you will be using this information when you're doing troubleshooting let's verify if we can connect to this particular instance using sequel server management studio so I'm going to open up my management studio connect to my sequel server database engine verify that everything is working fine again part of your failover and failback test is making sure that your applications can connect your database engine notice my version number eleven point zero point two one zero zero this is the sequel server version that I'm currently running on RPM version so the next thing that we need to do after the cluster is done is to install service pack 1 but before I do that I want to go back to my Active Directory environment and show you the computer objects that have been created so when we created a cluster when cluster 2 was created and when we install the sequel server available clustered instance sequel 2012 plus 2 is now in my active directory computers list and of course my DNS is configured with Active Directory integrated zone this entry is also created in my DNS I'll do a quick refresh and now I have sequel 2012 + 2 with the IP address that I provided earlier this is how you see the integration between sequel server failover clustered instance running on Windows server failure cluster and Active Directory with DNS so as I mentioned the next thing to do is to install the service pack if you go back to the lesson the service pack installation has to be done on the node and is not running any of the clustered resource groups in this case if I look at my windows failover cluster manager the resource is currently running on WS cluster 3 so what I'll do is I'll install the service pack on WS cluster 4 and once that's patch I'm good I am going to move the cluster resource from WS cluster 3 2 WS cluster 2 so I'm going to switch to my WS cluster 4 node and run the service pack I just downloaded the service pack and and copied it on my WS cluster 4 node can run the installation bit this is going to extract the bits into a temporary folder now I want to highlight the reason why the process goes like this in previous versions of sequel Server 2005 2000 when you install a service pack on a clustered instance it will have to go through all of the nodes and cross your fingers everything works fine that sometimes introduces a lot of complexities especially if the installation turned out to be a failure downtime is inevitable in this case you install the service pack on the non active node patch that if something happens your sequel server failed or clustered instance is still working not affected that minimizes downtime although the challenge there is if you have multiple instances running on multiple nodes you would have to do an x times y times of installation as far as installing the binaries and installing service packs are concerned so you have to factor that into your operations in administrative overhead down the road click on next accept the license terms by default the database engine services are selected click Next and this will patch all the components that you've specified if you have management's to do in this case I didn't install management studio in this node but it is recommended to do so it's going to patch that I'm going to skip past this click on next it's just checking for locked files and click update this respect installation is on its way and again binaries will be upgraded the DLLs the exe s will be upgraded once this is done we'll switch back to WS clusters 3 failover the sequel server resource group on this node and then run the service pack on that note one thing that I didn't do which I should be doing is to remove this particular node from my preferred owners group in this case again right-click on my resource group properties remove my WS cluster 4 in my preferred owners so that I don't accidentally failover to that node once the service pack installation is done we're going to flip this back to WS cluster 4 as my preferred owner and remove WS cluster 3 until the service pack is done then put it back as it was before let's just wait until service pack has completed installation I'm going to pause the video again and come back when this is done so the service pack installation is complete on WS cluster 4 I'm going to switch to WS Lester 3 and install the service pack in that particular node but before I do so I'm going to move the sequel server resource group from WS cluster 3 to the WS class or 4 so I'm going to close this and I want to make sure that I have a copy of the service pack on WS cluster 3 so 1 make sure that I copy this in there copy that over and switch to WS cluster three similar to what we did earlier I would now change my preferred owners to only BW s cluster for failover the cluster resource from WS cluster three two WS cluster four and then remove this from the preferred owners list wondered properties remove this and make this as my preferred owner move that to WS cluster for now what's happening here is not just your usual failover where where the services are brought offline but in the process sequel server will now start upgrading the databases the master database the user databases in this case I don't have any user databases yet but part of the process here is when it fails over to WS cluster for it sees that the version is higher than this particular nodes version and upgrades the database and that's why it's taking a while to bring the clustered resource online keep this thing in mind especially when you're doing service pack upgrades or even installing cumulative updates or security patches because this will factor into how long it takes for your sequel server resource to be go online now again if you if you notice this is not the same amount of time that it took when I was doing a failover and failback this so I'll pause the video for a while and come back when the clustered resource is has come back online notice that the sequel server resource has is gone online and my sequel server agent has just gone online now I can install the service pack on this particular node let me close this run the exact same process on WS cluster 3 and once it's done we now have a fully patched 2 node sequel server failover clustered instance running on a Windows Server 2012 failover clustering instance you and click on next accept the license terms similar in similar pages as what you've seen in the other note where I installed this particular patch and click update again I'm going to come back to this once the service pack has been installed and reconfigure my cluster resource group to make sure I've got everything covered and service pack installation is complete now keep in mind at this point WS cluster 4 still owns the clustered resource group so we want to make sure that we bring WS cluster 3 back to the preferred owners list and if you prefer WS cluster 3 or this particular node to be the node that will constantly run a sequel server failure closer to instance you have to move it back to this particular node go back to properties make sure that WS cluster 3 is my preferred owner back and fail fail back my resource group from WS cluster 4 to WS cluster straight this wouldn't take that long as compared to what happened earlier when we move the cluster resource group tome WS cluster 3 2 WS cluster 4 primarily because the binaries have taken kid of upgrading the database on WS cluster 4 so this one's a lot quicker and notice that the sequel server service is now back on line so we've installed a two node sequel server failover clustered instance on Windows Server 2012 failover clustered instance from crack a scratch configured the clustered resource group and then installed service pack on top of it and the next video I'm going to show you how you can install a sequel server 2012 failover clustered instance that's configured to have nodes across different geographical locations commonly known as multi subnet clusters or geographically dispersed clusters

Channel: Edwin M Sarmiento

Views: 99,333

Keywords: failover clustering

Id: VWTDbsGsBpI

Length: 58min 28sec (3508 seconds)

Published: Tue Jun 02 2015