• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
SQL Server Clustering and High Availability
 

SQL Server Clustering and High Availability

on

  • 2,507 views

End-to-End overview SQL Server High Availablity with Clustering SetUp

End-to-End overview SQL Server High Availablity with Clustering SetUp

Statistics

Views

Total Views
2,507
Views on SlideShare
2,507
Embed Views
0

Actions

Likes
1
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    SQL Server Clustering and High Availability SQL Server Clustering and High Availability Document Transcript

    • An Overview to SQL Server ClusteringAn overview to SQL Server Clustering and Deployment of SQL Server2008 multi site cluster on Windows 2003 R29/1/2011TATA CONSULTANCY SERVICES LTD.Supreme MandalSystems EngineerAssociate ID 473199Version 1.1SQL Server clustering uses Microsoft clustering services MSCS to perform set up and make functional awindows cluster which is required for high availability and perfect implementation of “Nines” in any mission TATA CONSULTANCY SERVICES Page 1
    • critical database/application support system. MSCS was introduced as a component of Windows NT server4.0Enterprise Edition to allow failover application if ones become unavailable.For Configuration of SQL Server clustered environment with an objective to employ a true hot-standbyserver facility (“Single Cluster / Dual Node” facility) the available failover options are below: Stand alone server User1 User2 User3 User4 User5 FIG, 1:- Conventional client-server environmentObjective of Clustering-- Zero Downtime Zero LossFrom Technical outlook it can be said that to achieve “Zero Downtime and zero loss” is practicallyimpractical which demands Cent percent dedication of each and every resource i.e. Hardware, Software,Networking , Power, Monitoring process and overall Technicians who are responsible for managingWindows datacenters. Thus in Real time Rules of Nines is applied to measure the accuracy of earlymentioned Technical Proverb “Zero Downtime and zero loss”The colloquial term nines is used in engineering to indicate reliability or purity (or similar quantitativedescriptor). It is preceded by a number indicating the degree of such reliability or purity. For example, 0.999 (or99.9 percent) pure silver would be 3 nines pure. Or, for example, electricity that is delivered without TATA CONSULTANCY SERVICES Page 2
    • interruptions (blackouts, brownouts or surges) 99.999 percent of the time would have 5 nines reliability.Reliability can be considered a time-based purity.SQL Server High Availability OptionsComparative Study of Cold /Warm/Hot Standby SolutionCOLD WARM HOT TATA CONSULTANCY SERVICES Page 3
    • Backup / Restore Replication and Log Shipping Failover clustering and Database MirroringDetach / Copy / Attach Manual detection and failover Automatic detectionManual detection and failover Replication – since SQL Server 6.0 Automatic, fast failoverPotential for data loss Primarily used where availability is Manual failover required in conjunction with scale out of read activity Failover requires custom solutionClients must be redirected Could define subset of source database Transparent client redirectionSlowest failover – most Latency between source and copy can Zero work lossdowntime be seconds Log ShippingBackup / Restore Basic idea: Backup, Copy, Restore Log Site redundancy will always be supportedLog backups allow point in Database scopetime restoreDetach / Copy / Attach Database accessible but read-onlyCopies entire files Users must exit for next log to be appliedNo rolling forward logs Peer-to-Peer Transactional Replication SQL Server 2005 introduced bi- directional transactional replication Enables scale-out and improved availabilityImprovements in SQL Server 2008 Version Conflict detection • Each row has a hidden column listing originating peer node ID for change • Distribution Agent on each node detects conflicts by comparing hidden column New Topology Wizard makes setup/ changes easier TATA CONSULTANCY SERVICES Page 4
    • RTO -Recovery Time ObjectivesRPO -Recovery Point ObjectivesActive/Passive Failover Configuration:SQL Server services are started on only one node of the cluster(primary node) while the other node( secondarynode) has the services configured to start manually In this case users will access the resources of only onemachine on the cluster for getting data available. The other one doesn’t serve user requests hence it is passive. In case of failure occurs in Primary Node, MSCS starts the SQL Server services on the Secondary nodeand bringing the DB online to make it available. Users will have to reconnect to access the data in the databasesrunning under SQL Server database engine, but the amount of time for the switch over will be considered only aminimal disruption of service Until Primary Node is coming back online, the secondary node will continue to provide users withaccess to SQL Server and its databases.Benefit: Because only one instance is being run on a server, no server will be required to assume two SQLServer instances in the event of a failover, so performance should not be degraded.Drawback: Because only one instance of SQL Server is being run on the virtual server, one server will alwaysbe in standby mode and idle. This means that you are not getting the most out of the money you used for thehardware. TATA CONSULTANCY SERVICES Page 5
    • User1 User2 User3FIG, 2:- Single Cluster Single Node (Active/Passive) Environment TATA CONSULTANCY SERVICES Page 6
    • Active/Active Failover Configuration: SQL Server is installed and started both nodes in the cluster. In this configuration two virtual servers areconfigured on the cluster to allow both SQL Server nodes to provide database access to their own respectivedata, to users. In a nutshell, both Windows servers in the cluster are operating as individual servers and can beaddressed individually for accessing SQL Server data.If one node fails other will grab Control of the shared databases and continue to provide services to users. Inthis case the single remaining node in the cluster will operate both virtual servers allowing each of SQL servernodes to access their data even though one is no longer available. Basically in Active/Active Configurationrequires that each SQL Server be configured as primary, specifying the other node of the cluster is secondary.Configuring an Active/Active failover scenario using MSCS requires a little more work than Active/Passive.But it allows for better utilization of server hardware because both machines are able to serve users and one ofthem takes the full load if something happens to its partner node.Remember one thing that MSCS has very stringent H/W requirements, so before proceed to set up withMicrosoft recommended HCL (hardware compatibility list) in line with Windows and SQL server version youare going to apply. But the best configuration is to use two identical servers with identical H/W peripherals,BIOS version etc.Benefit: With this configuration, you are fully using all of your hardware. Rather than having one server that isoperational and another that is in standby mode waiting for a failover, both servers are operational, whichallows you to get us out of the machines you have purchased.Drawbacks: If failover occurs and one server is running both SQL Server instances, performance can beadversely affected. However, this slower performance is probably better than the virtual server totally beingdown. An additional drawback is that this configuration requires more licenses to be purchased than with anActive/Passive cluster. Because the cluster is running two active instances of SQL Server, you will be requiredto purchase the licenses for two separate server machines, which depending on your situation, may be adeterrent. TATA CONSULTANCY SERVICES Page 7
    • Top 3 Challenges to implement a Cluster1.] CPUCPU resource usage is one of the top three areas you have to plan for when creating clustered environments.The old practice of sizing your CPUs so they are at a utilization rate of 60 percent to 80 percent still holds true,but this utilization rate now has to account for a failover. This means that if you keep your individual nodes at60 percent to 80 percent utilization they may not be able to handle the workload of failover instances. Whatdoes this mean?To truly size clustered servers for failover, you need to make sure that the total CPU utilization rate after worse-case failover scenarios never goes above 80 percent, even if your normal day-to-day CPU must remain below40% to account for possible failover scenarios.2.] MemoryAs with CPU resource usage, memory is very important to account for in failover clustering. Administratorsmust account for the memory usage of their applications after a failover. Memory intensive applications such asSQL Server 2008 will use as much memory on their own server as possible and often when failover occurs, theSQL Server 2008 instance that has failed over will have performance issues as it contends with the establishedinstance use of memory.Note: SQL Server 2008 has been improved over earlier versions of SQL Server and now has the ability toutilize dynamic memory in clustered environments.When configuring SQL Server on a clustered server in a multi-node environment, database administrators areadvised to set the max server memory configuration setting to leave memory free in case of failovers. It is alsorecommended that database administrators set the min server memory configuration setting to prevent the failedover instance from assuming all of the memory on the new node and affecting the performance of theestablished instance.3.] Disk DrivesOften, when creating multi-node clusters, administrators face the issue of not having enough disk drive letters.In a Windows environment, resource groups are given different drive letters on the clustered nodes. As thenumber of resource groups increases due to having multiple instances of SQL Server 2008 installed or due tothe design practice of using multiple file groups for a database, the 26-drive letter limit is severely restricted asthe number of nodes increase in a multi-node environment. Database administrators must work closely withserver administrators who often build the Windows clusters before SQL Server 2008 is installed to assure that TATA CONSULTANCY SERVICES Page 8
    • enough drive letters are available and that the sizes of the drives behind the drive letters are large enough toaccommodate their database size.Cluster Considerations:-It is advantageous to have a clustered SQL Server environment in terms of high availability; however, highavailability does come with certain tradeoffs. First, it is typically very expensive to create a clustered SQL Server environment. This is because the nodes in the clustering need to conform to the hardware compatibility list for clustered nodes. Second, complex network is required for setup, and the machines need to be close to identical, along with a required shared disk subsystem for the database files. A storage area network (SAN) is a decent choice for this subsystem, but a SAN is not required and is an expensive option. Third, if you are running an Active/Active cluster, you will need a SQL license for each processor for each machine running an instance of SQL Server in the cluster. Finally, local clustering is typically confined to the same geographic area; a natural disaster could potentially leave your cluster useless. In that event, you would need to convert to your disaster recovery site for continued operations. It is possible to set up geographically dispersed SQL Server clusters, but the setup is much more complex and expensive.Best Practices before setting up a Cluster:-Case IOperating Systems - Windows Server 2003 You should spend more time designing and planning your clustered environment than actually creating the clustered environment. All hardware used for the clustered environment must be on the Windows 2003 Clustering HCL as a unit and not as individual pieces. Each cluster node should have identical hardware If creating a clustered environment with more than 2 nodes, you should consider making one of the nodes a passive node and configure it as the primary failover node. Determine all virtual names and IP addresses during the planning phase Be sure to account for future additional space during the configurations of the drives and drive letters Use a standard drive letter for the local drives and quorum drives across all clustered nodes in your environment It is recommended that you utilize two separate (virtual or physical) networks in a clustered environment. One network for the public and one for the private. Be sure to use separate network cards for the Public and Private networks and not a single multi-port network card. Use static IP addresses for both the Public and Private networks with the Private network using a private class A, B, or C address. Make sure the shared disk array is configured properly, running, and can be seen by all nodes before installing your cluster. TATA CONSULTANCY SERVICES Page 9
    • Make sure your Quorum drive is fault tolerant. Create unique virtual server names of 15 characters or less. Be sure to disallow automatic fail-back to avoid the “ping-pong” effect resource bouncing back and forth when one node constantly fails and comes back up. Case II Database - SQL Server 2008 Microsoft recommends installing Analysis Services clustered installations in a single group with its own disk and IP resources and not on a resource group that has the database engine installed on it. While the Enterprise Edition of SQL Server 2005 supports 25 instances on a clustered node, Standard Edition only supports 16, you will need to understand that each instance needs its own resource group and you will need to utilize the Majority Node Set model. It is usually not best practice to install more than a few instances on a clustered node in order to achieve scalability and performance goals. SQL Server 2005 requires the .NET Framework on all nodes of the cluster and while the installation wizard will install the .NET Framework on all nodes, it is usually recommended that you install the .NET Framework on each node before attempting the actual installation process in order to speed up the install process. It is usually recommended that you create four different domain groups when creating a cluster. One for each of the following: SQL Server 2005 service, SQL Server 2005 Agent service, Full-Text Search service, and Analysis Services. Clustered SQL Server 2005 nodes should not have other applications installed on them Since you can only have one default instance in a clustered environment, it is better to simply name all instances in your environment for standardization purposes. Do not delete or rename the default cluster group, or remove any of the resources from this group and do not delete for rename any resources from the SQL Server 2005 resource group. If using replication in a clustered environment, place the snapshot folder on a network share that all nodes can read and write to. Be sure to test the failover of all nodes before going into productionOver and above Advantage and disadvantages of SQL server Cluster is like below:-Advantage of SQL Server Clustering:- The downtime during failover period is reduced to minimum. The response is automatic when the server fails and you don’t need to adjust anything manually. Upgrades can be performed without hampering the work of the client and forcing other users to logoff during that period. Enormous reduction in downtime is possible with clustered SQL server when compared with the other routines servers. No need to rename the servers while clustering because whenever the failover occurs, the users or client machines will not feel any change in the performance in spite of the system failure. Once the primary server is fixed you can quickly return back to it without wasting much time. TATA CONSULTANCY SERVICES Page 10
    • Disadvantage of SQL Server Clustering:- Expensive when compared to other alternatives of failover as stand-by servers and log shipping will cost you more. Setup time is more when compared to other options. Maintenance will be more when it is compared to other options. You need to hire experienced network administrators and database administrators to handle the clustering. Clustered Environment Health Checks Clustered Environment Health Checks Clustered Environment Health Checks TATA CONSULTANCY SERVICES Page 11
    • Significant Technical Jargons in Clustering:-1.] Cluster Node: Cluster node is the central head in clustering which uses MSCS Windows 2000datacenter edition can host 4 nodes at a time where as Advanced Server edition able to 2 nodes a time2.] Shared Disk Resources: where we can place SQL Server data files (.MDF) and log files (.LDF)so that in case of failure it will be shared by another node without interrupting (or slightest)3.] Private Disk Resources: SQL Server Executables (system files / DLL) will be installed there itwill also be shared by both node in case of failure4.] Heartbeat: Keep alive message generated by each node to its pair after every 5 seconds which in caseexecute a more deeper “IsAlive” check after every 60 seconds to verify whether it is there or not thus issuingselect @@servername, verifying the response .if it fails then failure will be recorded and another node will takecharge with slight interruption. Heartbeat message will be executed in private LAN. Failing to response theheart beat will cause cluster failover occurrence.5.] SQL Server Virtual IP Address: Frontend Applications i.e. web application (preferablyASP.NET) or Desktop application (preferably C#.NET) will connect this IP Address whenever they want toconnect the Database. This application will access the only database resource irrespective to which node theyare accessing in case of failure6.] SQL Server Virtual Network Name: Frontend application will connect this virtual networkname irrespective to specific SQL Server node over the Network.7.] SQL Server Resources: SQL Server resources like SQL Server database engine, SQL ServerAgent, SQL server Full text search is always shared by both nodes8.] Quorum Disk: reserved for the cluster services to keep track of cluster services and MSDTC alsoshared by both nodes, this disk is not for storing any data, log files it is denoted by Q disk.9.] Windows Network Name & IP Address: It is required in case of public LAN whereexternal or outsiders will access the data. It is also important if the server is connected to DHCP server to getthe IP Addresses.Schematic design in next page describing those above mentioned jargons in brief TATA CONSULTANCY SERVICES Page 12
    • UsersWhat is SANStorage Area Network (SAN), the network infrastructure is typically Fiber Channel (FC), although someorganizations use Gigabit Ethernet as well. The data transfer mechanism used by SANs is block SmallComputer Systems Interface (SCSI). This is well-suited to SQL Server, because the database applicationexpects block access to data, which is not easily supplied using NAS. Utilizing SAN software, multiple volumescan be created and “presented” to the servers, utilizing the storage space on the SAN, as shown in Figure TATA CONSULTANCY SERVICES Page 13
    • Server 1 DB 1 Server 2 DB 2SAN Disk Array SAN Controller DB 3 Server 3 Storage Area Networks TATA CONSULTANCY SERVICES Page 14
    • SQL Server 2008 multi-site cluster on WindowsServer 2003 R2 Undoubtedly, Failover Clustering is the best choice to reduce system downtime and provide higher applicationavailability for the whole instance of SQL Server within a site; however, a failover cluster does not protectagainst disk failure and requires a SAN.”What if you could have all of the benefits that Ross outlines and also protect against disk failure and eliminatethe need for a SAN? Well, the good news is that is exactly what you can do by implementing a Microsoft SQLServer 2008 multi-site cluster on Windows Server 2008. SQL Server 2008 multi-site cluster may be a little bitof a misnomer. It does not necessarily need to be deployed across geographically dispersed locations. Theservers could be located in the same rack, same room, same building or across continents; it really doesn’tmatter. The important thing is that you are eliminating your storage as a single point of failure and if you chooseto locate your cluster nodes in different physical locations then you also have built in site resiliency.One of the most common questions and points of confusion about SQL Server 2008 and Windows Server 2008failover clustering is support for failing across subnets. Yes, Windows Server 2008 Failover Clustering doessupport failing between subnets for most applications, however, SQL Server 2008 is not one of thoseapplications. As far as I know, SQL Server 2008 R2 will also not support failing between subnets when it isreleased. My understanding is that the SQL team is working on support for cross-subnet failover, but it will besupported sometime after SQL Server 2008 R2 is released. So, for the time being, you will have to span yoursubnet if you wish to separate your nodes geographically.Now that you have determined to deploy a multi-node SQL server cluster, here are the steps you will need tofollow. TATA CONSULTANCY SERVICES Page 15
    • Configured Failover Cluster Manager GUI on Windows 2008 R2 should look like this.Figure 1 – After adding the second DataKeeper resourceClustering MSDTCIMPORTANT NOTE – There is a hotfix that is required in order to support DTC with 3rd party disk resources.Please see the following KB article and apply the hotfix to all cluster nodes. SQL 2008 is very dependent uponMSDTC, so it is highly recommended that you cluster the MSDTC resource before you cluster your SQLresource. The following articles are provided for your reference for configuration and management of yourMSDTC resource.You will start by opening the Failover Cluster Manager GUI and then choose “Configure a Service orApplication”. TATA CONSULTANCY SERVICES Page 16
    • Figure 2– Creating a MSDTC resourceYou will then choose “Distributed Transaction Coordinator” and click next TATA CONSULTANCY SERVICES Page 17
    • Figure 3 – Choose your Service or ApplicationGive the MSDTC resource a name and unique IP address. These should be unique to MSDTC and not the sameas you will use later when you create your SQL resource. TATA CONSULTANCY SERVICES Page 18
    • Figure 4 – Choose a Name and IP addressChoose the volume where you will store the data for the MSDTC resource. In our case we are choosing thereplicated F drive. TATA CONSULTANCY SERVICES Page 19
    • Figure 5 – Choose a dedicated volume for the MSDTC resourceConfirm your information and click next to continue. TATA CONSULTANCY SERVICES Page 20
    • Figure 6 – Click next to configure the DTC resourceCongratulations, you have successfully configured the DTC resource. Click Finish. TATA CONSULTANCY SERVICES Page 21
    • Figure 7– A successfully configured DTC resourceWe are just about ready to begin the installation of the first node of the SQL Server Cluster, however, there isone thing we need to do in preparation – Slip Stream SQL 2008 SP1 onto the SQL Server 2008 RTM installmedia.Slip stream SQL SP1 onto your SQL 2008 install mediaWhat I have discovered is that SQL Server 2008 will not install on Windows Server 2008 R2 without firstslipstreaming SQL Server 2008 SP1 onto your SQL 2008 install media. Here is a great article that describeshow to slipstream SQL Server 2008 RTM and Service Pack 1. After I read that article and successfullyslipstream SP1 onto SQL 2008 RTM, I found the following Microsoft KB article that describes the sameprocedure. You may get an error that looks like the following if you try to install SQL without firstslipstreaming SP1 onto the media.There was an error setting private property ‘RequireKerberos’ to value ’1′ TATA CONSULTANCY SERVICES Page 22
    • Installing your first cluster nodeNow that you have your SQL Server 2008 SP1 installation media ready to go, you are ready to install your firstSQL node. There is one major “gotcha” when it comes to installing SQL on a multi-node cluster. In order foryou to install SQL on a multi-node cluster, you must first pass the Windows Server 2008 Failover Clustervalidate process. Unfortunately, a multi-site cluster is exempt from passing the storage related test, so you neverare able to actually “pass” the validation as far as SQL is concerned. It took a little investigation on my part, butwhat I have come to find is that there is a command line parameter that allows you to skip the validation test onthe SQL 2008 installation. Here is the command line.Setup /SkipRules=Cluster_VerifyForErrors /Action=InstallFailoverClusterTo launch the SQL setup, open a Command window, browse to your SQL 2008 with SP1 install directory andtype the command as shown below.Figure 7.1– If everything goes as planned, you should see the screen below. Click OK to continue. TATA CONSULTANCY SERVICES Page 23
    • Figure 7.2– Enter your product key and click Next TATA CONSULTANCY SERVICES Page 24
    • Figure 8 – Enter your product keyAccept the license agreement and click next TATA CONSULTANCY SERVICES Page 25
    • Figure 9 – Set up Wizard License Acceptance ScreenClick Install to install the Setup Support Files TATA CONSULTANCY SERVICES Page 26
    • At the end of the Setup for the Support Files you will receive a warning. Click on Show details and you will seethe message below. You can click Next, ignoring this message since it is expected in a multi-site or non-sharedstorage cluster. TATA CONSULTANCY SERVICES Page 27
    • Figure 10 – The warning is expected in a multi-site or non-shared storage clusterChoose the features you would like to install and click next. Leave the “Shared Feature” directory set to the Cdrive as the SQL binaries should not be installed on the replicated volume. TATA CONSULTANCY SERVICES Page 28
    • Figure 11 – Choose your features to be installed.On the next screen, you will choose a network name for your SQL Server. This will be the name that all of theclients will connect to. Assuming this is the default instance; leave the Instance ID and Instance root directoryset to the defaults. Do not move the instance root directory to the replicated volume. TATA CONSULTANCY SERVICES Page 29
    • Figure 12 – Choose your SQL Network NameIt is recommended that you have separate domain accounts for SQLServer and SQLAgent. You can take thetime to create these accounts now if you have not already done so. These accounts require no specialpermissions, as this install process will give them the permissions that they require. TATA CONSULTANCY SERVICES Page 30
    • Figure 13 – Confirm you have enough disk space and click next to continue. TATA CONSULTANCY SERVICES Page 31
    • Figure 14 – Choose the default settings to allow a new cluster resource group named “SQL Server(MSSQLSERVER)” to be created. TATA CONSULTANCY SERVICES Page 32
    • Figure 15 – Allow the wizard to create a new cluster resource group for youChoose a replicated volume that is still available, in our case the E: drive. Click Next to continue. TATA CONSULTANCY SERVICES Page 33
    • Figure 16 – Choose your replicated volumeNow you will choose the IP address you want associated with the SQL cluster resource. You could leave it setto use DHCP if you wish. TATA CONSULTANCY SERVICES Page 34
    • Figure 17 – Choose your SQL cluster IP addressChoose your security settings and click next TATA CONSULTANCY SERVICES Page 35
    • Figure 18 – Add any SQL Server administrators and choose your authentication mode and then click Next TATA CONSULTANCY SERVICES Page 36
    • Figure 19 – Choose your Error and Usage Reporting options and click Next TATA CONSULTANCY SERVICES Page 37
    • Figure 20 – You will once again see some warnings related to the validation process. You can ignore those messagesas they are to be expected in a multi-site SQL Server cluster. TATA CONSULTANCY SERVICES Page 38
    • Figure 21 – Click Install to begin the installation process TATA CONSULTANCY SERVICES Page 39
    • Figure 22 – If everything installs as expected, you should see the following screens. . TATA CONSULTANCY SERVICES Page 40
    • Figure 23 – Click next then Close to finish the installation TATA CONSULTANCY SERVICES Page 41
    • Figure 24 – Congratulations, you have successfully installed the first node of your multi-site SQL Server Cluster.Now we will install the second node of the cluster.Install the second cluster nodeInstalling the second cluster node is similar to installing the first node. We need to run SQL Setup once againfrom the command line so that we can skip the Validate process. So, from the 2nd node, open up your commandprompt and run the following command. 1. Install SQL 2008 SP1 (merged setup) on the 2nd node using the following command: Setup /SkipRules=Cluster_VerifyForErrors /Action=AddNode /INSTANCENAME=”MSSQLSERVER”*Note: This assumes you installed the default instance on the 1st node TATA CONSULTANCY SERVICES Page 42
    • Figure 25 – Command line cluster node managemaent TATA CONSULTANCY SERVICES Page 43
    • Figure 26 – That will launch the install wizard as shown below. Click OK to continue. TATA CONSULTANCY SERVICES Page 44
    • Figure 27 – Enter your product key and click next. TATA CONSULTANCY SERVICES Page 45
    • Figure 28 – Accept the license terms and click Next TATA CONSULTANCY SERVICES Page 46
    • Figure 29 – Click install to install the Setup Support files TATA CONSULTANCY SERVICES Page 47
    • Figure 30 – You can once again ignore the warning that some cluster validation tests have been skipped. This is tobe expected in a multi-site cluster and non-shared storage clusters.. TATA CONSULTANCY SERVICES Page 48
    • Figure 31 – Verify you are adding the node to the right instance and click Next TATA CONSULTANCY SERVICES Page 49
    • Figure 32 – Add the passwords to the service accounts and click Next TATA CONSULTANCY SERVICES Page 50
    • Figure 33 – Choose your Error and Usage Reporting options and click Next TATA CONSULTANCY SERVICES Page 51
    • Figure 34 – Once again, ignore the warning about the skipped operations. TATA CONSULTANCY SERVICES Page 52
    • Figure 35 – Click Install to begin the installation process.If everything goes as expected, you should see the following screen. TATA CONSULTANCY SERVICES Page 53
    • Figure 35 – Now that you have a fully functional two node cluster, TATA CONSULTANCY SERVICES Page 54
    • Figure 36 – you probably should testing things out by doing some manual switchovers. Right click on the resourceand choose “Move to node SECONDARY”. TATA CONSULTANCY SERVICES Page 55
    • Figure 37 – If everything is configured properly, your Failover Cluster GUI should look as follows.References:- TATA CONSULTANCY SERVICES Page 56
    • TechNet Library http://technet.microsoft.com/en-us/ms376608 http://technet.microsoft.com/en-us/library/cc770748(WS.10).aspx http://technet.microsoft.com/en-us/library/cc771540(WS.10).aspxMicrosoft Support Center http://support.microsoft.com/kb/978476 -:END:- TATA CONSULTANCY SERVICES Page 57