Difference between revisions of "Creating SQL with Storage 2012R2 iSCSI cluster"
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<br /> | <br /> | ||
This article has been created by an automatic translation software. You can view the article source [[:fr:Creation cluster SQL avec Storage iSCSI sur 2012R2|here]].<br /><span data-translate="fr"></span> | This article has been created by an automatic translation software. You can view the article source [[:fr:Creation cluster SQL avec Storage iSCSI sur 2012R2|here]].<br /><span data-translate="fr"></span> | ||
− | + | ||
Line 17: | Line 11: | ||
== Problem == | == Problem == | ||
− | We want to mount a cluster <span class="notranslate">SQL</span> | + | We want to mount a <span class="notranslate">cluster</span> <span class="notranslate">SQL</span> with a <span class="notranslate">storage</span> on a server accessible en <span class="notranslate">iSCSI</span>, all on servers in <span class="notranslate">Windows</span> 2012 R2. |
== Debug == | == Debug == | ||
This platform requires 3 servers : | This platform requires 3 servers : | ||
− | * 2 <span class="notranslate">Windows</span> 2012R2 wit <span class="notranslate">SQL</span> 2014 wit 5 ports <span class="notranslate"> | + | * 2 <span class="notranslate">Windows</span> 2012R2 wit <span class="notranslate">SQL</span> 2014 wit 5 ports <span class="notranslate">Etherna</span> (This number can be retced according to the needs ) : ServSQ01 and ServS02 |
− | * 1 <span class="notranslate">Windows</span> 2012R2 in storage server | + | * 1 <span class="notranslate">Windows</span> 2012R2 in storage server with 9 ports <span class="notranslate">Etherna</span> (This number can be reduced according to the needs ) ServSto01 |
== Solution == | == Solution == | ||
− | In prerequisites, install <span class="notranslate">Windows</span> 2012 R2 on | + | In prerequisites, install <span class="notranslate">Windows</span> 2012 R2 on the 3 servers and it updates. |
− | + | the two servers <span class="notranslate">SQL</span> must be on the same domain. | |
Diagram nawor "simplifie" platform (Th <span class="notranslate">switchs</span> are not present to monitor which is connected to what ) : | Diagram nawor "simplifie" platform (Th <span class="notranslate">switchs</span> are not present to monitor which is connected to what ) : | ||
− | + | [[File:schema_reseau_simple.PNG]] | |
=== ServStor Serve Configuration 01 === | === ServStor Serve Configuration 01 === | ||
− | On | + | On this server we have 9 port naworks used. |
1 dedicated to manageme | 1 dedicated to manageme | ||
− | 2 x 4 dedicated ports to </span> | + | 2 x 4 dedicated ports to <span class="notranslate">iSCSI</span>. |
− | <span class="notranslate">NIC</span>1, <span class="notranslate">NIC</span>2 a <span class="notranslate">NIC</span>3 correspond to | + | <span class="notranslate">NIC</span>1, <span class="notranslate">NIC</span>2 a <span class="notranslate">NIC</span>3 correspond to the three present networks cards, each with 4 ports <span class="notranslate">gigabits</span>. |
− | (See diagram to identify | + | (See diagram to identify the connections ) |
− | For | + | For the networ <span class="notranslate">iSCSI</span>, we will use a <span class="notranslate"> IP </span>en 192.168.0.0/24 |
− | Here | + | Here the<span class="notranslate"> IP </span>configured on the server ServStor 01 : |
− | < | + | <pre> |
NIC1 port 1 : Votre IP de votre serveur | NIC1 port 1 : Votre IP de votre serveur | ||
NIC1 port 2 : Non utilisé | NIC1 port 2 : Non utilisé | ||
Line 60: | Line 54: | ||
NIC3 Port 3 : 192.168.0.17 | NIC3 Port 3 : 192.168.0.17 | ||
NIC3 Port 4 : 192.168.0.18 | NIC3 Port 4 : 192.168.0.18 | ||
− | </ | + | </pre> |
− | For all cards in 192.168.0.x will in | + | For all cards in 192.168.0.x will in the Advanced Settings tab <span class="notranslate">DNS</span>, and on the box unchec "<span class="notranslate">Register this connection's addresses in </span><span class="notranslate">DNS</span>" |
− | + | [[File:register_dns.PNG]] | |
− | On | + | On the server ServStor01, it installs the rol ''<span class="notranslate">iSCSI</span> <span class="notranslate">Target</span><span class="notranslate"> Server</span>'' |
− | + | [[File:roles_servstor01.PNG]] | |
− | In the | + | In the <span class="notranslate">Server Manager</span>, we will create disks <span class="notranslate">iSCSI</span> (who are at the end of the) and t <span class="notranslate">Target</span> <span class="notranslate">iSCSI</span> that go them with : |
− | + | [[File:iSCSI_servstor01.PNG]] | |
It therefor : | It therefor : | ||
− | * < | + | * <span class="notranslate">task / New iSCSI virtual disk</span> |
* Select the volume | * Select the volume | ||
* It gives it a name (one can notice its future path down ) | * It gives it a name (one can notice its future path down ) | ||
Line 104: | Line 98: | ||
ServSQ01 : | ServSQ01 : | ||
− | < | + | <pre> |
NIC1 port 1 : 192.168.0.22 | NIC1 port 1 : 192.168.0.22 | ||
NIC1 port 2 : 192.168.0.26 | NIC1 port 2 : 192.168.0.26 | ||
Line 112: | Line 106: | ||
NIC2 port 1 : 192.168.0.25 | NIC2 port 1 : 192.168.0.25 | ||
NIC2 port 2 : 192.168.0.21 | NIC2 port 2 : 192.168.0.21 | ||
− | </ | + | </pre> |
− | + | ServSQL02 : | |
<pre> | <pre> | ||
NIC1 port 1 : 192.168.0.24 | NIC1 port 1 : 192.168.0.24 | ||
Line 124: | Line 118: | ||
</pre> | </pre> | ||
− | For all cards in 192.168.0.x will in the Advanced Settings tab < | + | For all cards in 192.168.0.x will in the Advanced Settings tab <span class="notranslate">DNS</span>, and on the box unchec "<span class="notranslate">Register this connection's addresses in </span><span class="notranslate">DNS</span>" |
− | + | [[File:Register dns.PNG]] | |
− | * On both servers, installing the feature < | + | * On both servers, installing the feature <span class="notranslate">"Multipath I/O"</span>. |
− | + | [[File:Feature_mpio.PNG]] | |
− | * Once installed in the interface </span> | + | * Once installed in the interface <span class="notranslate">metro</span> de 2012R2 (started so click ) just type "<span class="notranslate">MPIO</span>" and click on the result : |
− | + | [[File:Mpio.PNG]] | |
− | * In the tab < | + | * In the tab <span class="notranslate">"Discover Multipaths"</span> on coche <span class="notranslate">"Add Support for iSCSI devices"</span> then clicked on <span class="notranslate">ADD</span>. It proposes to restart, is done. |
* Once restarted, it relaunches <span class="notranslate">MPIO</span>, and this ensures "MSF2005<span class="notranslate">iSCSI</span>BusType0x9" is present in the "device hardware i". | * Once restarted, it relaunches <span class="notranslate">MPIO</span>, and this ensures "MSF2005<span class="notranslate">iSCSI</span>BusType0x9" is present in the "device hardware i". | ||
* It then launche "<span class="notranslate">iSCSIinitiator</span> " on both servers <span class="notranslate">SQL</span> | * It then launche "<span class="notranslate">iSCSIinitiator</span> " on both servers <span class="notranslate">SQL</span> | ||
− | * One goes on the tab "Configuratio" and it retrieves t <span class="notranslate">"Initiator Name"</span> (the form <span class="notranslate">"iqn.1991-05.com.microsoft: | + | * One goes on the tab "Configuratio" and it retrieves t <span class="notranslate">"Initiator Name"</span> (the form <span class="notranslate">"iqn.1991-05.com.microsoft:ServSQL01.domain.tld"</span>) |
* It returns on the server ServSTOR 01 | * It returns on the server ServSTOR 01 | ||
* In <span class="notranslate">Server Manager</span>, "File and <span class="notranslate">storage</span> Service", "<span class="notranslate">iSCSI</span>", right click on the <span class="notranslate">Target</span> to go to its properties and then in <span class="notranslate">initiators</span> | * In <span class="notranslate">Server Manager</span>, "File and <span class="notranslate">storage</span> Service", "<span class="notranslate">iSCSI</span>", right click on the <span class="notranslate">Target</span> to go to its properties and then in <span class="notranslate">initiators</span> | ||
Line 154: | Line 148: | ||
In the end must be the <span class="notranslate">IPs</span> related to this form : | In the end must be the <span class="notranslate">IPs</span> related to this form : | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | * It returns in < | + | |
+ | * It returns in <span class="notranslate">"Favorite Targets</span>" and you look at the details of these. We check that there are good relations with <span class="notranslate">IP</span> in the preceding table | ||
=== Configuration o <span class="notranslate">Failover</span> servers ServSQL 01 et 02 === | === Configuration o <span class="notranslate">Failover</span> servers ServSQL 01 et 02 === | ||
Line 240: | Line 188: | ||
* We start the installation, choose <span class="notranslate">"New SQL Server Failover cluster installation"</span> | * We start the installation, choose <span class="notranslate">"New SQL Server Failover cluster installation"</span> | ||
− | + | [[File:Install_SQL1.PNG]] | |
− | * The choice of features, in our case (future use with < | + | * The choice of features, in our case (future use with <span class="notranslate">CRM 2015</span>) Let's check <span class="notranslate">Database Engine Services</span>, <span class="notranslate">SQL Server Replication, Full-Text and Semantic Extractions for Search, reporting services-native, management Tools basic / complete</span> |
* Choose a network name for the <span class="notranslate">SQL</span>. In our case we will use <span class="notranslate">SQLServ</span> | * Choose a network name for the <span class="notranslate">SQL</span>. In our case we will use <span class="notranslate">SQLServ</span> | ||
* On <span class="notranslate">cluster Disk Selection </span>You can choose those you want to use. In our case, we take the <span class="notranslate">cluster Disk</span> 1 et 3 (le 2 being th <span class="notranslate">quorum</span>, le 1 et 2 being volumes <span class="notranslate">databases</span> et <span class="notranslate">logs</span>) | * On <span class="notranslate">cluster Disk Selection </span>You can choose those you want to use. In our case, we take the <span class="notranslate">cluster Disk</span> 1 et 3 (le 2 being th <span class="notranslate">quorum</span>, le 1 et 2 being volumes <span class="notranslate">databases</span> et <span class="notranslate">logs</span>) | ||
Line 256: | Line 204: | ||
<span class="notranslate"> | <span class="notranslate"> | ||
− | < | + | <pre> |
The following error has occurre: | The following error has occurre: | ||
Line 263: | Line 211: | ||
Click 'Retry to retry the failed action, or click 'Cancel to cancel this action and continue setup. | Click 'Retry to retry the failed action, or click 'Cancel to cancel this action and continue setup. | ||
− | For help, clic: | + | For help, clic: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20<span class="notranslate">SQL</span>%20Server&EvtSr=Setup.rl&EvtI=50000&Collec=12.0.2000.8&EvtTyp=0x0AD5303%25400xB814387 |
− | < | + | </pre> |
</span> | </span> | ||
− | You should go in the volume concerned with Explorer < | + | You should go in the volume concerned with Explorer <span class="notranslate">windows</span>to display the hidden files and protected system files and change the rights on the folder <span class="notranslate">system volume information</span>. |
Once the intervention is finished, we go to <span class="notranslate">ServSQL02</span>. | Once the intervention is finished, we go to <span class="notranslate">ServSQL02</span>. | ||
Line 273: | Line 221: | ||
* It launches the Setup with <span class="notranslate">"Add a node to a SQL Server Failover cluster</span>" | * It launches the Setup with <span class="notranslate">"Add a node to a SQL Server Failover cluster</span>" | ||
− | + | [[File:Install_SQL2.PNG]] | |
* It follows the steps, most being pre-filled | * It follows the steps, most being pre-filled | ||
Line 280: | Line 228: | ||
− | Once the installation is complete, you have your </span> | + | Once the installation is complete, you have your <span class="notranslate">SQL</span> 2014 en <span class="notranslate">failover</span> wit <span class="notranslate">storage</span> logged in <span class="notranslate">iSCSI</span> on a <span class="notranslate">Windows</span> 2012 R2. |
You can make improvements, as a link between the 2 servers for the <span class="notranslate">heartbeat</span> for example, but it is optional. | You can make improvements, as a link between the 2 servers for the <span class="notranslate">heartbeat</span> for example, but it is optional. | ||
− | + | [[Category:Windows]] | |
− | |||
− | |||
− | |||
<comments /> | <comments /> |
Revision as of 09:15, 9 October 2015
This article has been created by an automatic translation software. You can view the article source here.
Problem
We want to mount a cluster SQL with a storage on a server accessible en iSCSI, all on servers in Windows 2012 R2.
Debug
This platform requires 3 servers :
- 2 Windows 2012R2 wit SQL 2014 wit 5 ports Etherna (This number can be retced according to the needs ) : ServSQ01 and ServS02
- 1 Windows 2012R2 in storage server with 9 ports Etherna (This number can be reduced according to the needs ) ServSto01
Solution
In prerequisites, install Windows 2012 R2 on the 3 servers and it updates. the two servers SQL must be on the same domain.
Diagram nawor "simplifie" platform (Th switchs are not present to monitor which is connected to what ) :
ServStor Serve Configuration 01
On this server we have 9 port naworks used. 1 dedicated to manageme 2 x 4 dedicated ports to iSCSI.
NIC1, NIC2 a NIC3 correspond to the three present networks cards, each with 4 ports gigabits. (See diagram to identify the connections )
For the networ iSCSI, we will use a IP en 192.168.0.0/24 Here the IP configured on the server ServStor 01 :
NIC1 port 1 : Votre IP de votre serveur NIC1 port 2 : Non utilisé NIC1 port 3 : Non utilisé NIC1 port 4 : Non utilisé NIC2 Port 1 : 192.168.0.11 NIC2 Port 2 : 192.168.0.12 NIC2 Port 3 : 192.168.0.13 NIC2 Port 4 : 192.168.0.14 NIC3 Port 1 : 192.168.0.15 NIC3 Port 2 : 192.168.0.16 NIC3 Port 3 : 192.168.0.17 NIC3 Port 4 : 192.168.0.18
For all cards in 192.168.0.x will in the Advanced Settings tab DNS, and on the box unchec "Register this connection's addresses in DNS"
On the server ServStor01, it installs the rol iSCSI Target Server
In the Server Manager, we will create disks iSCSI (who are at the end of the) and t Target iSCSI that go them with :
It therefor :
- task / New iSCSI virtual disk
- Select the volume
- It gives it a name (one can notice its future path down )
- Choose the size in "Fixed Size" (Leave "Clear the virtual disk on allocation")
- One choos "New iSCSI Target"
- We give a name to this "iSCSI Target"
- Click on ADD in part "access Servers"
- In the choice of the method of identification of the initiator, soldarity bottom IP and put a IPIt will change it later.
- Leave CHAP et Reverse CHAP unchecke
- We finish by "Create" The "close" Once completed
From the, you have a shared disk en iSCSI. Repeat the operation as many times as necessary. In our case we create 3 discs :
- 1 for databases
- 1 for the logs
- 1 for th quorum (1GB will s)
Configuration iSCSI servers ServSQ 01 et 02
In this part, we will connect the two servers SQL to the serve storage by links iSCSI. We will use the MPIO in order to use ou 4 links networks and to share the load.
Configuration IP servers :
NIC1 et NIC2 correspond to the two network adapters on servers. NIC1 owns 4 ports, NIC2 a 2. Here is the configura :
ServSQ01 :
NIC1 port 1 : 192.168.0.22 NIC1 port 2 : 192.168.0.26 NIC1 port 3 : IP Server NIC1 port 4 : non utilisé NIC2 port 1 : 192.168.0.25 NIC2 port 2 : 192.168.0.21
ServSQL02 :
NIC1 port 1 : 192.168.0.24 NIC1 port 2 : 192.168.0.28 NIC1 port 3 : IP du serveur NIC1 port 4 : non utilisé NIC2 port 1 : 192.168.0.27 NIC2 port 2 : 192.168.0.23
For all cards in 192.168.0.x will in the Advanced Settings tab DNS, and on the box unchec "Register this connection's addresses in DNS"
- On both servers, installing the feature "Multipath I/O".
- Once installed in the interface metro de 2012R2 (started so click ) just type "MPIO" and click on the result :
- In the tab "Discover Multipaths" on coche "Add Support for iSCSI devices" then clicked on ADD. It proposes to restart, is done.
- Once restarted, it relaunches MPIO, and this ensures "MSF2005iSCSIBusType0x9" is present in the "device hardware i".
- It then launche "iSCSIinitiator " on both servers SQL
- One goes on the tab "Configuratio" and it retrieves t "Initiator Name" (the form "iqn.1991-05.com.microsoft:ServSQL01.domain.tld")
- It returns on the server ServSTOR 01
- In Server Manager, "File and storage Service", "iSCSI", right click on the Target to go to its properties and then in initiators
- Clicked on ADD
- On coche "Enter a value for the selected type"
- One sets type "IQN" and we put the address found earlier on the server SQL.
- You click on OK, repeat the operation to add the "IQN" of the SQL on all the Targets
- Removing thIP It was previously put here.
- Once validated, it returns on our servers SQL, always in the iSCSI initiator, we go in the tab "Targets" and it connects to the server storage.
- We go in the tab "Favorite Targets", is on will Target visible then it mad remove.
- Returns the tab "Targets" then we go on properties for one of Target
- The switching off the current session, and then clicke Add Session. On coche enable Multipath, clicked on advanced. One choos "Microsoft iSCSI initiator" in "local adapter". En initiator IP it chooses the first IP iSCSI du serveur SQL. En Target portal IP it chooses the first IP iSCSI Server of storage. It valid 2 times. Repeat the operation for each network adapter in passing to the ip following the
In the end must be the IPs related to this form :
- It returns in "Favorite Targets" and you look at the details of these. We check that there are good relations with IP in the preceding table
Configuration o Failover servers ServSQL 01 et 02
We begin by installing the feature Failover clustering on the 2 servers SQL.
During this time you can go in the disk management (right click on the me Windows, "disk management"). From here we pass disks in "online" and it initializes (GPT). It also created the partitions and formats i
It then launche "Failover cluster Manager" and it po Validate Configuration to verify that everything is ok. Some warnings may be present at the network level.
Is then "Create cluster" :
- You enter the name of the two se SQL
- You enter the nam cluster, in our example we'll take clusterSQL01
- It puts the cluster I
- Leave "Add all eligible storage to the cluster" check
- It valid
You must now configure the quorum. To do this, you click on the na clusterand t "more actions" et "configure cluster quorum settings".
- Been next
- Select the quorum witness
- Configure a disk witness
- We check the corresponding disk to quorum
- been next The finish.
- The other two discs, it pointed "add to clustershared volume" (In "disks", it selects discs in questions in order to )
We get the disc a logs volume 1 and the disc a BDD volume 2 in our case.
We now have a cluster configured
Installation o SQL 2014 en cluster
We begin by ServSQL01
- It installs the feature .net 3.5
- We start the installation, choose "New SQL Server Failover cluster installation"
- The choice of features, in our case (future use with CRM 2015) Let's check Database Engine Services, SQL Server Replication, Full-Text and Semantic Extractions for Search, reporting services-native, management Tools basic / complete
- Choose a network name for the SQL. In our case we will use SQLServ
- On cluster Disk Selection You can choose those you want to use. In our case, we take the cluster Disk 1 et 3 (le 2 being th quorum, le 1 et 2 being volumes databases et logs)
- It then chooses the ip du failover SQL
- We choose the accounts and passwords for services (in our case we have created dedicated services accounts )
- In part "Database engine Configuration" in our case we use the Mixed mode. Also click on add the current user.
- Always in the same part in the tab Data Directories, you specify the database records (We therefore choose our volum iSCSI)
- For th reporting Services one p "Install & configure"
- It launches the Setup
If you encounter the following error during installation :
The following error has occurre: Updating permission setting for folder 'C:\clusterstorag\Volum2' failed. The folder permission setting were supposed to be set to 'D:P(A;ERE;F;;;B)(A;ERE;F;;;S)(A;ERE;F;;;C)(A;ERE;F;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)'. Click 'Retry to retry the failed action, or click 'Cancel to cancel this action and continue setup. For help, clic: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20<span class="notranslate">SQL</span>%20Server&EvtSr=Setup.rl&EvtI=50000&Collec=12.0.2000.8&EvtTyp=0x0AD5303%25400xB814387
You should go in the volume concerned with Explorer windowsto display the hidden files and protected system files and change the rights on the folder system volume information.
Once the intervention is finished, we go to ServSQL02.
- Installing th .net framework 3.5
- It launches the Setup with "Add a node to a SQL Server Failover cluster"
- It follows the steps, most being pre-filled
- It retyped passwords if necessary.
- It launches the Setup
Once the installation is complete, you have your SQL 2014 en failover wit storage logged in iSCSI on a Windows 2012 R2.
You can make improvements, as a link between the 2 servers for the heartbeat for example, but it is optional.
Enable comment auto-refresher