SQL 2008 Failover cluster Installation

Transcription

1 SQL 2008 Failover cluster Installation Designed By

2 1 INTRODUCTION This document demonstrates the installation and configuration of a 2 node SQL Database Cluster 2008.These tasks can be done on physical hardware or a virtual environment. 2 PREREQUISITIES For installation of Windows cluster we should have 1. One Domain controller (DC) 2. 2 Nodes for Server cluster (Windows 2008 machines) 3. Nodes should have 2 NIC s on it (1 private and 1 public) 4. Shared drivers (SAN) for Server cluster for Quorum and Data base of SQL server. 5. Both nodes should have dotnet 3.5 framework and windows installer 4.5 installed. In Server cluster both the server are connected with each other with cross cable which work as Heart beat of cluster. Other NIC will provide Network connectivity with the Network. Provide a Private IP address on the Heart beat NIC and LAN ip address on the other NIC. Without Domain controller we cannot create Cluster as we need to have central Authentication but in Windows 2008 domain in required one time at the time of installation if DC fails it will not impact the Cluster services.

3 3 CREATE SHARED DISKS AND ADD TO THE CLUSTER NODES 3.1 CREATE SHARED DISKS Shared disks are created on SAN. We are using here starwind for demonstration. Using starwind create 3 disks i) One for Quorum (512 MB) ii) One for MS DTC service (1024 MB) iii) One for SQL data files (30 GB) 3

4 4

5 5

6 6

7 7

8 8

9 Similary create two other disks. 3.2 PRESENT DISKS TO CLUSTER iscsi initiator comes pre-installed in Windows Open iscsi initiator from Administrator tools in OS Cluster nodes 9

10 Go to discovery tab and click Add Portal. Provide the IP of the machine where starwind (SAN) was installed 10

11 Click OK PROPOSAL Now got to Targets tab and select LUN from the list. Click Log on In Popup window click Advance 11

12 In Advance window make following changes Local adaptor Microsoft iscsi Initiator Source IP Ip address of your system Target portal Ip address of the SAN server. 12

13 Click ok. 13

14 Check option ---- Automatically Restore This connection when the system boots. PROPOSAL Click ok. Repeat the same step for all the LUN in the Target option. 14

15 Now Click on Volumes and Devices and Click on Auto Configure PROPOSAL. Open the Computer management using command compmgmt.msc. You will Find that the entire SAN disk are attached to the Server. Select each Disk Right click Select Bring Online. 15

16 And Initialize disk 16

17 17

18 Right Click on Unallocated space which is in Black colour. Create volume on disk, format the disk and assign drive letter. 18

19 Click next..next until finish. Now we are able to see those SAN drives attched to the server and shown in My computer. Rename the Drive if required. 19

20 Repeat the same steps of iscsi initiator on the other Node. 20

21 4 CREATING WINDOWS 2008 CLUSTER To create Win server 2008 cluster 4.1 ADD FAILOVER CLUSTER FEATURE In Administrative tools go to Server Manager 21

22 In features click Add features. In pop up window select Failover clustering. In Add features wizard select Failover Clustering 22

23 Click Next PROPOSAL Click Install 23

24 Click close after success 24

25 4.2 CREATE NEW CLUSTER PROPOSAL In Administrative tools go to Failover Cluster Management Click Validate a Configuration 25

26 In pop up window click Next 26

27 In select servers windows enter name/ip of all nodes and click Add PROPOSAL After adding servers click next 27

28 Click run all tests PROPOSAL Click next..next until tests start 28

29 After tests success report should appear PROPOSAL 29

30 After success click Create a cluster PROPOSAL Click next in popup window 30

31 Add name of servers to be added to cluster PROPOSAL Click Next. Give a name to the cluster and Provide the cluster ip address by whcih the clients on the network will access the cluster. This is a virtual ip address of the cluster. 31

32 Make sure the IP is free and not already assigned to any machine. PROPOSAL click Next. Click Next 32

33 After success click Finish 33

34 To check whether the cluster is working fine or not. Stop cluster service of the node which is PROPOSAL currently the owner of the cluster resources. All resource will transfer to the other node. If it is not replicating then may be the cluster is not configured properly. Need to cross check the cluster configuration. 4.3 ADD QUORUM DISK In cluster manager window, right click on the cluster and select Configure Cluster Quorum Settings in More Actions. 34

35 Click next Click next 35

36 Select disk created for Quorum click next until finish. 4.4 ADD MSDTC SERVICE TO CLUSTER Opne Failover cluster Management. Right Click on Services and Applications and select Configure a Service or Application. 36

37 In popup window click next 37

38 Select Distributed Transaction Coordinator (DTC) and click Next PROPOSAL Give name and free IP Click next. 38

39 Select the disk created for DTC PROPOSAL click next until finish. 39

40 40

41 41

42 5 INSTALLING SQL 2008 ON CLUSTER USING SILENT INSTALL PROPOSAL Mount CD on the node or copy the SQL Server 2008 Setup at local drive of the server. Run following command from the command prompt (D: is the drive where SQL DVD is mounted in this case) D:\setup /CONFIGURATIONFILE= c:\configfilecluster.ini /FAILOVERCLUSTERIPADDRESSES="IPv4; ;Cluster Network 2; " The configuration file is attached: ConfigFileCluster.ini. txt 5.1 BEFORE INSTALLATION Following are some of the actions/prerequisites for installation of SQL Cluster: 1. Create Domain account to work as service. 2. Disk for SQL data files should be available on windows cluster. Contents of Configuration file: ;SQLSERVER2008 Configuration File [SQLSERVER2008] 42

43 ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory PROPOSAL structure, registry structure, and service names will reflect the instance ID of the SQL Server instance. INSTANCEID="MSSQLSERVER" ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. ACTION="InstallFailoverCluster" ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components. FEATURES=SQLENGINE,REPLICATION,FULLTEXT,SSMS,ADV_SSMS ; Displays the command line parameters usage HELP="False" ; Specifies that the detailed Setup log should be piped to the console. 43

44 INDICATEPROGRESS="True" PROPOSAL ; Setup will not display any user interface. ;QUIET="True" ; Setup will display progress only without any user interaction. QUIETSIMPLE="True" ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. X86="False" ; Specifies the path to the installation media folder where setup.exe is located. MEDIASOURCE="D:" ; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature. 44

45 ERRORREPORTING="False" PROPOSAL ; Specify the root installation directory for native shared components. INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server" ; Specify the installation directory. INSTANCEDIR="C:\Program Files\Microsoft SQL Server" ; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature. SQMREPORTING="False" ; Specify a default or named instance. MSSQLSERVER is the default instance for non-express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS). INSTANCENAME="MSSQLSERVER" ; Specifies a cluster shared disk to associate with the SQL Server failover cluster instance. 45

46 FAILOVERCLUSTERDISKS="Cluster Disk 3" ; Specifies the name of the cluster group for the SQL Server failover cluster instance. ;FAILOVERCLUSTERGROUP="SQL Server (MSSQLSERVER)" FAILOVERCLUSTERGROUP="SQLServerGrp" ; Specifies the name of the SQL Server failover cluster instance. This name is the network name that is used to connect to SQL Server services. FAILOVERCLUSTERNETWORKNAME="sqlservernw" ; Agent account name AGTSVCACCOUNT="SANDEEP\SQLCLUS" AGTSVCPASSWORD="dbnms#123" ; Startup type for Integration Services. 46

47 ISSVCSTARTUPTYPE="Automatic" PROPOSAL ; Account for Integration Services: Domain\User or system account. ISSVCACCOUNT="NT AUTHORITY\NetworkService" ; Controls the service startup type setting after the service has been created. ASSVCSTARTUPTYPE="Automatic" ; The collation to be used by Analysis Services. ASCOLLATION="Latin1_General_CI_AS" ; The location for the Analysis Services data files. ASDATADIR="Data" ; The location for the Analysis Services log files. ASLOGDIR="Log" 47

48 ; The location for the Analysis Services backup files. ASBACKUPDIR="Backup" ; The location for the Analysis Services temporary files. ASTEMPDIR="Temp" ; The location for the Analysis Services configuration files. ASCONFIGDIR="Config" ; Specifies whether or not the MSOLAP provider is allowed to run in process. ASPROVIDERMSOLAP="1" ; Level to enable FILESTREAM feature at (0, 1, 2 or 3). FILESTREAMLEVEL="0" 48

49 ; Specifies a Windows collation or an SQL collation to use for the Database Engine. PROPOSAL SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS" ; Account for SQL Server service: Domain\User or system account. SQLSVCACCOUNT="SANDEEP\SQLCLUS" SQLSVCPASSWORD="dbnms#123" SAPWD="dbnms#123" ; Windows account(s) to provision as SQL Server system administrators. SQLSYSADMINACCOUNTS="SANDEEP\Administrator" ; The default is Windows Authentication. Use "SQL" for Mixed Mode Authentication. SECURITYMODE="SQL" ; The Database Engine root data directory. 49

50 INSTALLSQLDATADIR="S:\Program Files\Microsoft SQL Server" PROPOSAL ; Specifies how the startup mode of the report server NT service. When ; Manual - Service startup is manual mode (default). ; Automatic - Service startup is automatic mode. ; Disabled - Service is disabled RSSVCSTARTUPTYPE="Automatic" ; Specifies which mode report server is installed in. ; Default value: FilesOnly RSINSTALLMODE="FilesOnlyMode" ; Add description of input argument FTSVCACCOUNT FTSVCACCOUNT="NT AUTHORITY\LOCAL SERVICE" 50

51 5.2 ADDING NODE TO SQL CLUSTER PROPOSAL Mount CD on the node which is to be added. Run following command from the command prompt (D: is the drive where SQL DVD is mounted in this case) on the node which is to be added. D:\setup /CONFIGURATIONFILE= c:\addnode.ini The configuration file is attached: AddNode.ini.txt Contents of configuration file are: ;SQLSERVER2008 Configuration File [SQLSERVER2008] ACTION="AddNode" HELP="False" INDICATEPROGRESS="True" QUIETSIMPLE="True" X86="False" MEDIASOURCE="D:" INSTANCENAME="MSSQLSERVER" FAILOVERCLUSTERGROUP="SQLServerGrp" FAILOVERCLUSTERNETWORKNAME="sqlservernw" AGTSVCACCOUNT="SANDEEP\SQLCLUS" 51

52 AGTSVCPASSWORD="dbnms#123" PROPOSAL SQLSVCACCOUNT="SANDEEP\SQLCLUS" SQLSVCPASSWORD="dbnms#123" FTSVCACCOUNT="NT AUTHORITY\LOCAL SERVICE" 52

53 5.3 INSTALL SQL TOOLS PROPOSAL If sql management tools are not installed by then these can be installed by running following command on the respective nodes: Setup.exe/qs /Action=Install /Features=Tools Check the manual and Automatic Failover cluster of SQL DB. END of the Document 53