Creating 4 Node SQL Cluster

Hi
I need to create a 4 Node - SQL 2012 Cluster (all in active Mode).
Node-1 will be having 1 Instance, Node-2 will be having 2 Instance, Node-3 will be running with 1 instance, and Node-4 will be running with 6 SQL Instance.
Let me know whether can I install all the 10 Instance on Node-1 and then can i go ahead and add the node-2 by selecting 10 Instances which is already installed and then node-3 and node-4.
or Let me know if any other recommended way of Setting up the Cluster.
Raj

Hi,
In the Server 2012 Failover cluster the node maximum is 64, the SQL server also have the maximum node limit, such as SQL 2008 clustering depends on which version of the software
you purchase, along with which version of the operating system you intend to use. Therefore for the rigid plan I suggest you ask the issue in SQL forum.
More information:
SQL Server forum:
http://social.technet.microsoft.com/Forums/sqlserver/en-us/home?category=sqlserver
Before Installing Failover Clustering
http://msdn.microsoft.com/en-us/library/ms189910.aspx
Thanks for your understanding and support.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Creating Allwayon SQL cluster for MS SQL Resource proidver.

Hi All,
i have set up SQL Alwayson 2014 Enterprise and also a File server cluster in order on connect both to the WAP.
i was able to create the SQK WAP on the admin portal group with the file server cluster. but when i am trying to connect the MS SQL resource i am setting the following error on the wap admin portal:
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify
that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
i look into the SQL logs - i seems like the user(SQL user to connect from the WAP to SQL) able to perform authentication with the SQL.
Next - i look in WAPADMINAPI event viewer --> MGMTSVC-SQLServer--> operational -->
and i was getting the following error :(event ID 160)
Unexpected exception for operation '', version '', client request Id '', server request Id '', exception 'System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The
server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception
(0x80004005): The network path was not found
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
timeout)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.WindowsAzure.Server.Common.SqlProcExecutor.<ExecuteNonQueryAsync>d__d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.WindowsAzure.Management.ResourceProvider.SqlServer.Controllers.HostingServersController.<CreateSysAdminLogin>d__7d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.WindowsAzure.Management.ResourceProvider.SqlServer.Controllers.HostingServersController.<CreateHostingServerAsyncInternal>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.WindowsAzure.Management.ResourceProvider.SqlServer.Controllers.HostingServersController.<CreateHostingServer>d__15.MoveNext()
ClientConnectionId:00000000-0000-0000-0000-000000000000'.
what can i do in order to fix it?
TNX
Eran.

WAP and SQL do not have to be in the same domain, This is an issue regarding NETBIOS name resolving.
Your WAP and SQL probably in a different subnet, so a different broadcast domain.
When you add your SQL Availablity Group in WAP if first makes a connection over TCP/IP.
When it reads the members of the AG, it tries to resolve the hostnames over NETBIOS/Named Pipes.
This fails because there servers are not in the same broadcast domain.
I'm communication with someone from the WAP team to get this fixed, although I'm not sure this is something that needs to be fixed in WAP.
Workaround:
Put your SQL Server node names in the hostfile of your WAP Admin servers.
- Darryl

Replace 2 Nodes in Cluster

Have a 2 node SQL Cluster & looking for best way to replace these with two new servers. I was thinking of removing 1 SQL node and then remove node from windows failover cluster mmc. Then unplug crossover cable and plug into new server and make new
server same name as one that was just removed.. Then add to cluster and start w. SQL nodes.. thoughts? any articles,etc to follow?

Hi,
You can refer the following same scenario solution:
Add or Remove Nodes in a SQL Server Failover Cluster (Setup)
http://technet.microsoft.com/en-us/library/ms191545.aspx
Replace broken node on SQL 2008 failover cluster
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/a25cba7a-4762-45b5-
be4c-18fc13ec7eab/replace-broken-node-on-sql-2008-failover-cluster?
forum=sqldisasterrecovery
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to add a new instance to a 2 node SQL 2008 R2 Cluster under the same networkname

Hello All,
I'm fairly new to sql and have just deployed a new 2 node SQL 2008 R2 cluster.
During installation, I created a networkname SQLCLU and a named instance I01.
I now would like to add another Instance (I02) under the same networkname.
What is the proper procedure to do this?
I don't believe that I should do this using the action: "New SQL Server failover cluster" from the setup menu, but rather using the action "New Installation or add features to an existing installation"
With the second option, I'm however not sure how I should make this instance clustered..
Should I also execute the "New Installation or add features to an existing installation" action on the 2nd node in the cluster?
Many thanks for your advice!
Filip

You cannot use the same network name for 2 instances. You need to use a different network name for the second instance I02
A failover cluster instance contains:
A combination of one or more disks in a Microsoft Cluster Service (MSCS) cluster group, also known as a resource group. Each resource group can contain at most one instance of SQL Server.
A network name for the failover cluster instance.
One or more IP addresses assigned to the failover cluster instance.
One instance of SQL Server that includes SQL Server, SQL Server Agent, the Full-text Search (FTS) service, and Replication. You can install a failover cluster with SQL Server only, Analysis Services
only, or SQL Server and Analysis Services
http://msdn.microsoft.com/en-in/library/ms179410(v=sql.105).aspx

Creating a windows cluster 2012 for sql server 2012 clustered installation

Hello,
I am trying to create a windows cluster for sql server 2012 clustering on windows server 2012 R2 standard edition-64bit OS
when i perform the test after adding the cluster nodes i get this warning on networking.:Validate the servers can communicate
do i have to enable UDP port 1434?
I enabled ports 3343 on both the server but i still get the error.Please see the image below .Please suggest.
Thank you.
lucky

Do you have installed one SQL Server instance on the node?
http://blogs.technet.com/b/meamcs/archive/2013/02/15/sql-2012-failover-cluster-build-step-by-step-part-1-installing-sql-2012.aspx
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

3 Node Cluster with 2 node SQL Always_On

We currently have more than 20 always_on clusters i.e. all following the below configurations
Server 1, Server 2 (High Hardware Configuration i.e. 16 CPU & 30 GB RAM) & File-share Witness on a small box (2 CPU with 4 GB RAM). We have seen some situations where nodes not able to communicate with the file-share and taking the cluster resource
down
Question: Can we create a windows cluster with 2 nodes i.e. (2 big hardware configuration for SQL + 1 small hardware configuration) to make it a 3 node windows cluster and have SQL on only the first 2 nodes with Always_ON ?

Hi,
Could you apply the following updates and see if it will alleviate the symptoms?
System event log errors every 15 minutes on a Windows Server 2008 R2-based Cluster configured with Node Majority and File Share Witness quorum
http://support.microsoft.com/kb/2750820
A cluster resource remains offline after the "Run this resource in a separate Resource Monitor" option is disabled in Windows Server 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;977837
In addition, you may update the NIC drivers and disable TCP chimney offload and check the result.
Information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;951037
If still no progress, upload the cluster.log to your OneDrive and share the link here.
Understanding the Cluster Debug Log in 2008
http://blogs.technet.com/b/askcore/archive/2010/04/13/understanding-the-cluster-debug-log-in-2008.aspx
Thanks.
Tracy Cai
TechNet Community Support

HOWTO: Create 2-node Solaris Cluster 4.1/Solaris 11.1(x64) using VirtualBox

I did this on VirtualBox 4.1 on Windows 7 and VirtualBox 4.2 on Linux.X64. Basic pre-requisites are : 40GB disk space, 8GB RAM, 64-bit guest capable VirtualBox.
Please read all the descriptive messages/prompts shown by 'scinstall' and 'clsetup' before answering.
0) Download from OTN
- Solaris 11.1 Live Media for x86(~966 MB)
- Complete Solaris 11.1 IPS Repository Image (total 7GB)
- Oracle Solaris Cluster 4.1 IPS Repository image (~73MB)
1) Run VirtualBox Console, create VM1 : 3GB RAM, 30GB HDD
2) The new VM1 has 1 NIC, add 2 more NICs (total 3). Setting the NIC to any type should be okay, 'VirtualBox Host Only Adapter' worked fine for me.
3) Start VM1, point the "Select start-up disk" to the Solaris 11.1 Live Media ISO.
4) Select "Oracle Solaris 11.1" in the GRUB menu. Select Keyboard layout and Language.
VM1 will boot and the Solaris 11.1 Live Desktop screen will appear.
5) Click <Install Oracle Solaris> from the desktop, supply necessary inputs.
Default Disk Discovery (iSCSI not needed) and Disk Selection are fine.
Disable the "Support Registration" connection info
6) The alternate user created during the install has root privileges (sudo). Set appropriate VM1 name
7) When the VM has to be rebooted after the installation is complete, make sure the Solaris 11.1 Live ISO is ejected or else the VM will again boot from the Live CD.
8) Repeat steps 1-6, create VM2 and install Solaris.
9) FTP(secure) the Solaris 11.1 Repository IPS and Solaris Cluster 4.1 IPS onto both the VMs e.g under /home/user1/
10) We need to setup both the packages: Solaris 11.1 Repository and Solaris Cluster 4.1
11) All commands now to be run as root
12) By default the 'solaris' repository is of type online (pkg.oracle.com), that needs to be updated to the local ISO we downloaded :-
+$ sudo sh+
+# lofiadm -a /home/user1/sol-11_1-repo-full.iso+
+//output : /dev/lofi/N+
+# mount -F hsfs /dev/lofi/N /mnt+
+# pkg set-publisher -G '*' -M '*' -g /mnt/repo solaris+
13) Setup the ha-cluster package :-
+# lofiadm -a /home/user1/osc-4_1-ga-repo-full.iso+
+//output : /dev/lofi/N+
+# mkdir /mnt2+
+# mount -f hsfs /dev/lofi/N /mnt2+
+# pkg set-publisher -g file:///mnt2/repo ha-cluster+
14) Verify both packages are fine :-
+# pkg publisher+
PUBLISHER                   TYPE     STATUS P LOCATION
solaris                     origin   online F file:///mnt/repo/
ha-cluster                  origin   online F file:///mnt2/repo/
15) Install the complete SC4.1 package by installing 'ha-cluster-full'
+# pkg install ha-cluster-full+
14) Repeat steps 12-15 on VM2.
15) Now both VMs have the OS and SC4.1 installed.
16) By default the 3 NICs are in the "Automatic" profile and have DHCP configured. We need to activate the Fixed profile and put the 3 NICs into it. Only 1 interface, the public interface, needs to be
configured. The other 2 are for the cluster interconnect and will be automatically configured by scinstall. Execute the following commands :-
+# netadm enable -p ncp defaultfixed+
+//verify+
+# netadm list -p ncp defaultfixed+
+#Configure the public-interface+
+#Verify none of the interfaces are listed, add all the 3+
+# ipadm show-if+
+# run dladm show-phys or dladm show-link to check interface names : must be net0/net1/net2+
+# ipadm create-ip net0+
+# ipadm create-ip net1+
+# ipadm create-ip net2+
+# ipadm show-if+
+//select proper IP and configure the public interface. I have used 192.168.56.171 & 172+
+# ipadm create-addr -T static -a 192.168.56.171/24 net0/publicip+
+#IP plumbed, restart+
+# ipadm down-addr -t net0/publicip+
+# ipadm up-addr -t net0/publicip+
+//Verify publicip is fine by pinging the host+
+# ping 192.168.56.1+
+//Verify, net0 should be up, net1/net2 should be down+
+# ipadm+
17) Repeat step 16 on VM2
18) Verify both VMs can ping each other using the public IP. Add entries to each other's /etc/hosts
Now we are ready to run scinstall and create/configure the 2-node cluster
19)
+# cd /usr/cluster/bin+
+# ./scinstall+
select 1) Create a new cluster ...
select 1) Create a new cluster
select 2) Custom in "Typical or Custom Mode"
Enter cluster name : mycluster1 (e.g)
Add the 2 nodes : solvm1 & solvm2 and press <ctrl-d>
Accept default "No" for <Do you need to use DES authentication>"
Accept default "Yes" for <Should this cluster use at least two private networks>
Enter "No" for <Does this two-node cluster use switches>
Select "1)net1" for "Select the first cluster transport adapter"
If there is warning of unexpected traffic on "net"1, ignore it
Enter "net1" when it asks corresponding adapter on "solvm2"
Select "2)net2" for "Select the second cluster transport adapter"
Enter "net2" when it asks corresponding adapter on "solvm2"
Select "Yes" for "Is it okay to accept the default network address"
Select "Yes" for "Is it okay to accept the default network netmask"Now the IP addresses 172.16.0.0 will be plumbed in the 2 private interfaces
Select "yes" for "Do you want to turn off global fencing"
(These are SATA serial disks, so no fencing)
Enter "Yes" for "Do you want to disable automatic quorum device selection"
(we will add quorum disks later)
Enter "Yes" for "Proceed with cluster creation"
Select "No" for "Interrupt cluster creation for cluster check errors"
The second node will be configured and 2nd node rebooted
The first node will be configured and rebootedAfter both nodes have rebooted, verify the cluster has been created and both nodes joined.
On both nodes :-
+# cd /usr/cluster/bin+
+# ./clnode status+
+//should show both nodes Online.+
At this point there are no quorum disks, so 1 of the node's will be designated quorum vote. That node VM has to be up for the other node to come up and cluster to be formed.
To check the current quorum status, run :-
+# ./clquorum show+
+//one of the nodes will have 1 vote and other 0(zero).+
20)
Now the cluster is in 'Installation Mode' and we need to add a quorum disk.
Shutdown both the nodes as we will be adding shared disks to both of them
21)
Create 2 VirtualBox HDDs (VDI Files) on the host, 1 for quorum and 1 for shared filesystem. I have used a size of 1 GB for each :-
*$ vboxmanage createhd --filename /scratch/myimages/sc41cluster/sdisk1.vdi --size 1024 --format VDI --variant Fixed*
*0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%*
*Disk image created. UUID: 899147b9-d21f-4495-ad55-f9cf1ae46cc3*
*$ vboxmanage createhd --filename /scratch/myimages/sc41cluster/sdisk2.vdi --size 1024 --format VDI --variant Fixed*
*0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%*
*Disk image created. UUID: 899147b9-d22f-4495-ad55-f9cf15346caf*
22)
Attach these disks to both the VMs as shared type
*$ vboxmanage storageattach solvm1 --storagectl "SATA" --port 1 --device 0 --type hdd --medium /scratch/myimages/sc41cluster/sdisk1.vdi --mtype shareable*
*$ vboxmanage storageattach solvm1 --storagectl "SATA" --port 2 --device 0 --type hdd --medium /scratch/myimages/sc41cluster/sdisk2.vdi --mtype shareable*
*$ vboxmanage storageattach solvm2 --storagectl "SATA" --port 1 --device 0 --type hdd --medium /scratch/myimages/sc41cluster/sdisk1.vdi --mtype shareable*
*$ vboxmanage storageattach solvm2 --storagectl "SATA" --port 2 --device 0 --type hdd --medium /scratch/myimages/sc41cluster/sdisk2.vdi --mtype shareable*
The disks are attached to SATA ports 1 & 2 of each VM. On my VirtualBox on Linux, the controller type is "SATA", whereas on Windows it is "SATA Controller".
The "--mtype shareable' parameter is important
23)
Mark both disks as shared :-
*$ vboxmanage modifyhd /scratch/myimages/sc41cluster/sdisk1.vdi --type shareable*
*$ vboxmanage modifyhd /scratch/myimages/sc41cluster/sdisk2.vdi --type shareable*
24) Start both VMs. We need to format the 2 shared disks
25) From VM1, run format. In my case, the 2 new shared disks show up as 'c7t1d0' and 'c7t2d0'.
+# format+
select disk 1 (c7t1d0)
[disk formated]
FORMAT MENU
fdisk
Type 'y' to accept default partition
partition
0
<enter>
<enter>
1
995mb
print
label
<yes>
quit
quit26) Repeat step 25) for the 2nd disk (c7t2d0)
27) Make sure the shared disks can be used for quorum :-
On VM1
+# ./cldevice refresh+
+# ./cldevice show+
On VM2
+# ./cldevice refresh+
+# ./cldevice show+
The shared disks should have the same DID (d2,d3,d4 etc). Note down the DID that you are going to use for quorum (e.g d2)
By default, global fencing is enabled for these disks. We need to turn it off for all disks as these are SATA disks :-
+# cldevice set -p default_fencing=nofencing-noscrub d1+
+# cldevice set -p default_fencing=nofencing-noscrub d2+
+# cldevice set -p default_fencing=nofencing-noscrub d3+
+# cldevice set -p default_fencing=nofencing-noscrub d4+
28) It is better to do one more reboot of both VMs, otherwise I got a error when adding the quorum disk
29) Run clsetup to add quorum disk and to complete cluster configuration :-
+# ./clsetup+
=== Initial Cluster Setup ===
Enter 'Yes' for "Do you want to continue"
Enter 'Yes' for "Do you want add any quorum devices"
Select '1) Directly Attached Shared Disk' for the type of device
Enter 'Yes' for "Is it okay to continue"
Enter 'd2' (or 'd3') for 'Which global device do you want to use'
Enter 'Yes' for "Is it okay to proceed with the update"
The command 'clquorum add d2' is run
Enter 'No' for "Do you want to add another quorum device"
Enter 'Yes' for "Is it okay to reset "installmode"?"Cluster initialization is complete.!!!
30) Run 'clquorum status' to confirm both nodes and the quorum disk have 1 vote each
31) Run other cluster commands to explore!
I will cover Data services and shared file system in another post. Basically the other shared disk
can be used to create a UFS filesystem and mount it on all nodes.

The Solaris Cluster 4.1 Installation and Concepts Guide are available at :-
http://docs.oracle.com/cd/E29086_01/index.html
Thanks.

SQL Cluster services is not start in secound node.

SQL Cluster services is not start in secound node.

Start or Stop the Cluster Service on a Cluster Node
https://technet.microsoft.com/en-us/library/cc771742.aspx
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

Can a SQL Cluster have many Master Secret \ SSO systems?

We are trying to build a BizTalk environment that will offer multiple BizTalk instances off one SQL cluster.
Our SQL cluster consists of 2 servers configured in an ACTIV\ACTIVE configuration and reads data from a SAN.
We have to set up 6 BizTalk instances to create 6 environments for UAT, Support, DR, etc. These BizTalk groups will contain 2 BizTalk servers each. Each instance will have a group of service accounts assigned to it ino order to separate the environments
but will still use the same SQL cluster.
We have named cluster resources for each UAT, Support, etc for the SAN so that the databses are written and read from mounted disks.
My question and confusion surrounds SSO and the clustering of the Master Secret for multiple instances.
I want to cluster the Master Secret on the existing SQL cluster as the documentation states, but I am not sure if this is correct when there are multiple BizTalk instances running off the the same SQL cluster. The nodes of the SQL cluster will have
the SSO service installed and so too will the BizTalk servers in each instance group - UAT, Support, etc. So, would this mean there is only one master secret being used for all BizTalk instances, which I feel is wrong?
Or should the master secret just exist on a bizTalk server without HA?
I want HA but not sure where the SSO and master secret should go and ensure there are no dependencies from the other BizTalk instances should the SSO service need restarting on the SQL cluster.
I have not implemented multiple instances on the same SQL cluster before so this is new and confusing. The microsoft documentation isn't too great either.
Any help and guidance would be greatly appreciated.

post Windows Server 2008 you can have multiple MS DTC instances on one cluster. So unlike previous versions (w2k3) where the recommendation was to add MSDTC to the base cluster group, you can now have one instance of MSDTC cluster resource per resource group.
In short yes if you feel that MSDTC is becoming a bottleneck in your processing. Also it would be preferred that for each of your BizTalk Environments you create at least ONE MSDTC resource per environment.
Regards.

How to migrate SQL Cluster into Virtual SQL server or Virtual SQL Cluster

Hello All,
Currently we will be attempting to migrate a SQL cluster of (2 systems) into are virtual enviroment. We have been tracking the system requirements with Vmware Consolidation Tool and IO Meter to make sure our hosts have enough resources to accomidate this. All the metrics coming back looks like it will run just fine virtulized as the cluster was just for failover purposes anyhow and not for performance purproses. With that said a few questions have come up.
1.) What is the best way to virtulize this or to convert it (P2V)
- Should we just create a new Virtual Machine and install the same version of SQL and do a manual migration to the new SQL server and leave it as 1 SQL server with HA
- Or is there a way to P2V this kind of a setup ? if so what are the steps involved?
2.) If a P2V is possible I was under the impression that you will have to use a RAW mapping for the hard disks otherwise the cluster will not work ? Can anyone speak to this? as I'm pretty sure I have clustered windows server 2008 without RAW mapping before but not with SQL

Another quick question. The Vmware SQL Clustering KB article says:
vSphere MSCS Setup Limitations
Before you set up MSCS, review the list of functionality that is not supported for this release, and any
requirements and recommendations that apply to your configuration.
The following environments and functionality are not supported for MSCS setups with this release of vSphere:
n Clustering on iSCSI, FCoE, and NFS disks.
n Mixed environments, such as configurations where one cluster node is running a different version of ESX/
ESXi than another cluster node.
n Use of MSCS in conjunction with VMware Fault Tolerance.
n Migration with VMotion of clustered virtual machines.
n N-Port ID Virtualization (NPIV)
n With native multipathing (NMP), clustering is not supported when the path policy is set to round robin.
n You must use hardware version 7 with ESX/ESXi 4.0.
Can you not do clustering if your shared storage is iSCSI ? or can you not do RAW mapping with it to create the cluster ?

SQL Cluster requiremnt for Lync 2013

Hi
We are are planning to deploy Lync 2013 enterprise. Planning to use SQL cluster. Would like to clarify whether we must create a sepearte sql instance for Lync 2013 or can we use an existing shared instance to create a seperate database for Lync.
We prefer 2nd approach. Is there any issues or demerits using existing shared SQL instances?
Thanks and regards,
Aboo Arif

Hi AbooArif.
This kind of question is very common. Basically here is the Microsoft Documentation about it.
Database software support in Lync Server 2013
https://technet.microsoft.com/en-us/library/gg398990.aspx
This point is the important: "If you collocate Lync Server databases with other databases, we highly recommend assessing all factors that might affect availability and performance, as well as ensuring that, if one node fails, the remaining node can
handle the load. To verify failover capabilities, we recommend testing all failover scenarios."
We can say the following: It's recommended to use a separate SQL server for Lync, however collating Lync database with other SQL databases will work, but has an high probability of present some performance problems. Many customers prefer to use this option
considering the cost of SQL licenses.
It is important to consider all the hardware requeriments for the Lync Server BackEnd role:
https://technet.microsoft.com/en-us/library/gg398835.aspx because the normal issue when customers share the SQL server with other instances is due to performance issues. Also note
that if you have multiple front end pools, these cannot share a SQL server.
PLEASE REMEMBER, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answered"

VBScript to enumerate SQL Cluster information?

I am trying to create a WScript to enumerate certain information from the SQL Cluster, including:
Cluster name
Node names
Which node is active
The local SQL Server service that is part of the node (e.g., MSSQLSERVER, MSSQL$BACKOFFICE, etc)
The volume name for the shared drive/volume
I have found scripts to add clusters, and C# programs to enumerate cluster information, but so far have not been successful in creating a simple enumeration script.
I thought this would be an easy one but it is turning out to be trickier than I thought.
Thanks for any guidance.

Hi,
Another option is to use PowerShell to retrieve the cluster information.
Here are some articles abount this:
Monitor a SQL Server Cluster using PowerShell
http://www.mssqltips.com/sqlservertip/3154/monitor-a-sql-server-cluster-using-powershell/
Get-SQLInstance
http://gallery.technet.microsoft.com/scriptcenter/Get-SQLInstance-9a3245a0
Find All SQL Instances Using PowerShell Plus A Little More
http://learn-powershell.net/2013/09/15/find-all-sql-instances-using-powershell-plus-a-little-more/
Microsoft.FailoverClusters.PowerShell
http://technet.microsoft.com/en-us/library/ee461009.aspx
Hope the information helps.
Tracy Cai
TechNet Community Support

3 Node Failover Cluster With iSCSI

Is there any information available on the steps to create a 3 node failover cluster with iSCSI storage? Is there a step-by-step guide? I looked around but couldn't find much. Thanks!

Hi SCPSTech,
The 3 node cluster create steps same with 2 node, you can refer the following step by step white paper create the 2 node cluster then add the another node to cluster.
Configuring Failover Clusters with Windows Storage Server 2008
http://blogs.technet.com/b/storageserver/archive/2009/12/17/configuring-failover-clusters-with-windows-storage-server-2008.aspx
Add a Server to a Failover Cluster
http://technet.microsoft.com/en-us/library/cc730998.aspx
More information:
Add or Remove Nodes in a SQL Server Failover Cluster (Setup)
http://msdn.microsoft.com/en-us/library/ms191545.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Install db using sapinst on sql cluster

I'm having an issue installing the ep6 db using sapinst on a sql cluster. sapinst wants to install to the localhost/default, but I need to specify the "virtual" sql cluster name.
Is there a workaround using sapinst, or is there some special way one needs to backup/restore onto the cluster from another machine..
any ideas?
jm

<snip>
Marty McCormick
Posts: 17
Registered: 2/25/04
Hi Gabor-
Although it's not supported, you can get EP6 SP2 to work with clustered SQL server 2000 on a virtual MSCS cluster. (We have it working here on Win2003)
The instructions were posted somewhere on this discussion board before, but here they are again:
1) Install SQL as a default local instance with the DB files on a clustered drive. Make sure to choose custom install and select Binary 850 collation.
2) Select a clustered drive for the SQL data files.
3) Install SQL SP3
4) Install SQL hotfix xxxx
5) Run instcoll.exe on the local instance to upgrade to 850 BIN2
6) Run SAPinst, choose ?Database? and allow the setup to create the databases PCD and WCM
7) Detach the databases (Right click on the DB in SQL Enterprise Manger and Detach)
8) Upgrade the local SQL instance to a clustered instance (Note: when running sql setup again, make sure there is no other default instance running on the other node or you will not have the upgrade option). You will have to give the SQL install an instance name at this point.
9) Re-install SQL SP3
10) Re-install hotfix xxx
11) Re-run instcoll.exe (Note: You will have to do this while SQL services are running. Instcoll will prompt you to stop them using the SQL Services Manager, follow the instructions Instcoll displays).
12) Attach the PCD and WCM databases.
13) Run SAPInst on your portal servers and point the install at the clustered SQL virtual server name / instance.
General comments:
There are 3 main considerations when installing EP6 with a clustered SQL backend:
1) You can only run SAPinst ? Database (creates PCD and WCM databases, SAPPCD and SAPWCM users) against a local non-named instance of SQL (SAPinst used the local SQL pipe to connect)
2) Instcoll.exe will NOT run against a SQL installation that has the two EP6 databases (PCD/WCM) attached, hence the need to detach them before running setup / instcoll.
3) Be very careful with collations. After the upgrade to cluster operation the collation will not be the same. If you attach the PCD and WCM databases to a SQL server running the wrong collation YOU WILL CORRUP THE DATABASES!
</snip>

Cluster disk failed - 2 node multisite cluster

i am setting up a 2 node , 2 site cluster with no shared disks. on each node I have a C, D and E drive.
file share witness is setup on a 3rd site as a share.
when i go to failover cluster administrator, I see that cluster disk 1 and 2 are failed. any idea why?

Hi,
From your description “2 site cluster with no shared disks. on each node I have a C, D and E drive.“ it seems you didn’t setup the CSV disk, but in the server 2008 or above
system edition failover cluster the CSV is the necessary condition, you must setup the CSV disk first.
If you want to create one failover cluster in the Geographically separated site, please refer the following related article first.
SQL Server 2012 AlwaysOn – Part 4 – SAP configuration in Geo-Cluster configuration
http://blogs.msdn.com/b/saponsqlserver/archive/2012/02/29/sql-server-2012-alwayson-part-4-sap-configuration-in-geo-cluster-configuration.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Creating 4 Node SQL Cluster

Similar Messages

Maybe you are looking for