SQL cluster name on a Windows Failover Cluster

Hello,
I am installing a SQL cluster (first timer) using Windows server and SQL (both 2008 R2)
Windows failover cluster is setup and functioning. I am now installing the SQL failover cluster part.
Question: What should be the "SQL server network name", should it be the same as my Windows cluster name or different name ?
Thanks for your help,
Luca

It should be different, this is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters.
SQL Server Network Name —
Specify a network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.
https://msdn.microsoft.com/en-us/library/ms179530.aspx?f=255&MSPPError=-2147217396
This will be the name used to identify your cluster on the network. This is the name that will be available on the
network for the clients to connect SQL instance.
http://www.mssqltips.com/sqlservertip/1709/install-sql-server-2008-on-a-windows-server-2008-cluster-part-3/

Similar Messages

  • The acount information could not be verified - SQL 2005 SP3 installation on Windows 2008 R2 Failover Cluster

    Hi,
    We have a problem when we are trying to install SQL SP3 on SQL 2005 cluster.
    The problem is described bellow:
    We installed a new Windows 2008 R2 x64 failover cluster with two nodes.
    As a next step we installed SQL 2005 Enterprise edition x64 on this failover cluster. We have finished the installation without problems. After SQL installation we are trying to install SQL SP3 . We have logged on using a domain administrator account and
    we start the installation of SP3 with that user. In authentication mode screen the test gives a success status using either domain administrator-windows authentication or sa-sql authentication. On remote user account screen, when we give the domain
    administrator account we get the message "the account information could not be verified. Press ok to return to authentication mode screen to determine the reason for failure".
    We have tried to give the SQL services startup user on remote user account screen but the error is the same.
    the domain administrator account exists on security logins of SQL with sysadmin rights.
    Can someone help?
    Thanks. 

    Hi StelioMavro,
    According to your error message, when you install SQL Server 2005 SP3 in your failover cluster, we need to verify if there was other instance that had been removed and the installation did not pass the login check. I recommend you use windows authentication
    instead of SQL Server authentication when applying SP3. And the windows account used to run the SP3 setup program must have administrator privileges on the computer where SP3 will be installed.
    For more information about how to install SQL Server 2005 SP3 in failover cluster, you can review the following article.
    http://www.sqlcoffee.com/Tips0007.htm
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Cluster resource 'SQL Network Name (SQLCLUS1)' of type 'Network Name' in clustered role 'SQL Server (DB1)' failed.

    Cluster resource 'SQL Network Name (SQLCLUS1)' of type 'Network Name' in clustered role 'SQL Server (DB1)' failed.
    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster
    Manager or the Get-ClusterResource Windows PowerShell cmdlet.
    I keep getting this error message. Can someone please help. Thank You.
    Kranp.

    Hi Kranp,
    As the issue is more related to Windows Server high availability
    , I recommend you post the question in the
     Windows Server High Availability (Clustering)
     forum. It is appropriate and more experts will assist you.
    Besides, there are similar threads regarding to the above error for your reference.
    2012 Cluster service name failing
    SQL 2012 Failover Cluster - unable to start because
    of 'Network Name' failed
    Issues with resource creation on W2K12 SQL
    failover cluster, confirm procedures
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • IP Resource Errors While Building a Windows Failover Cluster on Azure

    I have setup a failover cluster in Microsoft Azure on four VMs. I have two nodes in one subnet/region, one node in another subnet/region and a final node in a third subnet/region. The cluster passed the validation wizard and was successfully built, but the
    two nodes in other subnets will not go online, reporting "Failed to bring the resource 'IP Address x.x.x.x' online".
    Azure Vnet Setup
    Vnet 1 - South Central US - 10.16.16.0/16 - Nodes 1 & 2 - Online
    Vnet 2 - West US - 10.116.16.0/16 - Node 3 - Offline
    Vnet 3 - East US - 10.216.16.0/16 - Node 4 - Offline
    All three IP Address resources are DHCP. I've attempted to make them static but they still failed while coming online. If I click "Information Details" on the error I get:
    Error code: 0x80071397
    The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource.
    It seems to be an issue with the way Azure DHCP works, but I'm stalled. There must be a way to get his working. What am I missing?

    Hi Michael Lapidakis,
    Starting in Windows Server 2008, a feature called an “OR dependency” was added to Failover Clustering which gave admins the ability to have nodes with a Network Name that
    could use one IP Address OR another IP Address .In a multisite cluster, it is expected that 1 IP address is offline as it is an OR relationship.
    You can refer the following related article to realize more detail settings of multi-site site cluster IP settings.
    IP Resource Errors While Building a Windows Failover Cluster on Azure
    https://social.technet.microsoft.com/Forums/en-US/ca2cbf5e-abef-4c23-9cff-7b6ca44acc23/ip-resource-errors-while-building-a-windows-failover-cluster-on-azure?forum=winserverClustering
    I’m glad to be of help to you!
    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.

  • Do SameSubnetDelay or SameSubnetThreshold setting need restart windows failover cluster ?

    Hi ,
    I set SameSubnetDelay=2000 and SameSubnetThreshold = 10,but after a failover, when i check the cluster log, we still found SameSubnetDelay and SameSubnetThreshold  use default setting.
    So i want to konw do these settings need restart windows failover cluster core resource group to take effect?
    Our windows version: Windows 2008 R2 SP1
    Many thanks.

    Thanks for your reply.
    After set up new values for these two settings , i checked the values use "cluster /prop " command, it indeed show new values. 
    But after a sql server cluster instance failover, i checked the cluster log to find the cause of failover ,in the cluster log it showed default values for these settings. There were two times like this.
    I will keep watching this, and next time i will post the setting values and cluster log.

  • Moving Physical SQL Cluster into Virtual SQL Cluster based on Hyper-V Failover

    Hello All............I have a SQL Cluster based on Physical Hardware that has Three-3 instances as well. I have setup a Hyper-V Failover Cluster (2012 R2) and have built Virtual/Guest SQL Cluster (2012 R2) upon it.  Now, I intend to move
    the instances/databases from Physical SQL Cluster to Virtual SQL Cluster.
    1.  Is this supported?  If so, I would appreciate any guidance on it?
    2.  Is P2V of SQL Cluster supported in Hyper-V Failover Cluster based on Windows Server 2012 R2?

    Hi Sir,
    Please refer to the following blog regarding moving SCCVM SQL database to another SQL server:
    http://blogs.technet.com/b/configurationmgr/archive/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server.aspx
    It is quoted from the  similar thread :
    https://social.technet.microsoft.com/Forums/en-US/a1558842-cdf5-4e5f-8f10-d660e96eae1b/migration-sql-for-sccm-2012?forum=configmanagermigration
    But it seems that is a migration of system center production , I would suggest you to post the question to system center forum ：
    https://social.technet.microsoft.com/Forums/en-US/home?forum=configmanagermigration%2Coperationsmanagergeneral&filter=alltypes&sort=lastpostdesc
    Best Regards,
    Elton Ji
    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.

  • Windows Failover Cluster (Errors retrieving file shares)

    I'm having an issue with Windows Failover Cluster with a Windows Server 2012 R2  machine. I have two cluster nodes (nodeA and nodeB). My issue is that when nodeA is the owner node, and I open failover cluster manager  <clusterName> >>
    roles >> <fileserver role> >> shares tab it will hang and say that it is loading, but this will occur infinitely. Although when I go to nodeB (not the owner node) and I go to shares it will show me all of the shares that I have. Next when
    I go to <clusterName> >> Nodes  >> click on Roles tab the information says "There were errors retrieving file shares."
    Now when I switch the nobeB to the owner node, I cannot view the shares on that machine but can now view them on nodeA. 
    We alse have a test network where I have recreated the machines, environment and the failover cluster to as close as the production network as I can except everything works great in the test network 

    For anybody searching on this later...
    I was getting "There were errors retrieving file shares" no matter which node of my cluster
    owned the fileshare service.  Turns out my problem was that my servers don't have internet access and I had set a system proxy.  The fix described in the link below was to exclude the local domain from the proxy.
    http://blogs.technet.com/b/askcore/archive/2012/12/03/cluster-aware-updating-cau-interaction-with-proxy-servers.aspx

  • Question on sql cluster failover behaviour

    Hi Experts,
    I have a doubt on SQL Cluster.
    In SQL cluster, If we MOVE the group or failover the group to another node what happens to the user connections(say 100 conn's) and ongoing open transactions during failover?
    Will all connections gets disconnected and open transactions gets rollbacked or the connections and txns will be moved to other node?
    Could anyone shed some insight on this?
    Thank you.

    All connections get disconnected an ongoing transactions have to be rolled back. Its like restarting the service, just on the other node.
    Bodo Michael Danitz - MCT, MCITP - free consultant - performance specialist - www.sql-server.de

  • CAS. NLB or Windows failover cluster

    Hi.
    Tell me please. Can i use Windows failover clustering for CAS?
    Now i use NLB for CAS and Windows failover cluster for DAG.
    I want create a one more cluster for two CAS servers (disable NLB).
    What is the difference for CAS between NLB and Windows failover clustering?
    Thanks.

    Yeah, failover cluster is not recommended. There are three basic options for load balancing Exchange 2013 CAS:
    DNS Round Robin
    Windows NLB
    L4 Load Balancer
    Round Robin is the easiest, but doesn't really do load balancing, or check that the servers are up.
    NLB will load balance and check that servers are up, but won't protect against service level failures. There are also some other down sides with NLB (see second link below).
    The load balancer is generally the way to go, as is much easier to configure on Exchange 2013 than 2010, due to the session affinity changes in CAS (technically, L7 load balancer was needed for 2010). Obviously, this is not a free option.
    Here are a few links that are good to read:
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/introducing-load-balancing-exchange-server-2013-part1.html
    http://technet.microsoft.com/en-us/library/jj898588(v=exchg.150).aspx

  • SQL cluster 2008 R2 migration to new Hardware in VM

    Hi,
    We have a task to migrate existing Physical SQL Cluster DB to new Hardware but in VM. (cannot argue with the client)
    hence our plan is to install new Cluster in VM with same Windows and SQL version i.e Win 2K8 R2 ENT w/SP and SQL 2K8
    R2 STD w/SP and use SQL mirroring option for the DB to migrate on the new Server (keeping the downtime to as low as possible and advantage of bringing the old server online in case of any issues..)
    Below points are for a single instance, couple of DB to migrate:
    Keep the  physical production server running
    In-Parallel build New SQL Cluster in VM (keep same version windows/sql)
    Keep Same drive letter for Quorum, MSDTC, DATA, LOG & Backup
    Keep the same Instance Name, SQL Network Name can be different (will be changed to old network name once the PROD is shutdown)
    Check all logins windows and SQL to be same on both the clusters
    Copy all the jobs, SSIS packages etc.. .create the location folder as per current server on the VM SQL Cluster
    Perform full backup of old cluster company-db databases or use the existing latest backup (full, differential, transaction)
    Restore databases in the new cluster with no recovery so additional log file or differential backup can be restored
    Create SQL Mirroring for the Database and select the principal server (old cluster) and the mirror server (new VM cluster)
    Choose mirroring without witness ( no auto failover as we don’t need the old server later)
    Start the mirroring – (hopefully everything synchronized and working)
    During the downtime –
    Stop the application/ client connection – if possible
    Failover the DB through Mirroring option
    Once the mirrored server becomes Principal and data is accessible – stop the mirroring
    Now the new VM SQL Cluster DB is online
    Shutdown the old cluster company-db (Node1 & Node2)
    Come back to VM SQL Cluster and change the Network name to the old server network name (so that client connections are not affected)
    Check if the DNS entries are updated with correct name and IP address
    Delete DNS entries for old company-db on DNS Servers if not deleted, delete the old server SQL network name in computer object
    Stop SQL Resources on the new VM SQL Cluster (take it offline all the resources)
    Bring online the SQL Resource and make sure the SQL resources are online and new network name is reachable
    Wait till you see machine name company-db in active directly (AD) and DNS server will have entry for company-db
    Verify connectivity for company-db from outside.
    If things are not going as per the plan then shut down the new VM cluster
    Revert back the DNS settings
    Power up the Old SQL Server
    The DB will show “restoring mode” – use command to make it online “RESTORE DATABASE (dbname) WITH RECOVERY”
     Check the DB
    Start using the OLD server again
    Troubleshoot the failed scenario ;)
    Need to know if the above steps are okay, and any consideration once the new VM SQL Cluster is online.
    Kindly let me know if there anything else to transfer apart from the logins, jobs, folder location etc.. !! 
    Many Thanks

    Hello,
    Well if you don’t change the instance name (name = ABC) then its OK.
    Try the following resources about transferring SQL Server logins:
    http://support.microsoft.com/kb/918992/en-us
    http://www.mssqltips.com/sqlservertip/2081/transfer-sql-server-jobs-task-and-transfer-sql-server-logins-task-in-ssis/
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • SQL Cluster - Unable to obtain IP Address from System Center IP Pool

    Hi everyone,
    we are trying to deploy a SQL cluster into a windows azure pack tenant cloud.
    Our azure pack environment contains:
    - 4X Hyper-V server in a failover cluster
    - 1X SCVMM server
    - multiple WAP server
    Steps we have done:
    -    Windows failover cluster is installed and configured successfully
    -    Quorum disk was configured successfully
    -    SQL server 2014 installation (via static IP) is successfully. But routing between the VMs is not possible.
    -    SQL server 2014 installation (via DHCP) fails at the end of the installation with following error:
            -> We used DHCP to obtain an IP from the scvmm IP pool.
    (01) 2015-04-22 15:29:11 Slp: Running Action: cluster_ip_address_cluster_config_Cpu64
    (01) 2015-04-22 15:29:11 Slp: Action Data:
    (01) 2015-04-22 15:29:11 Slp:   Feature = SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64
    (01) 2015-04-22 15:29:11 Slp:   Scenario = install
    (01) 2015-04-22 15:29:11 Slp:   Timing = ConfigNonRC
    (01) 2015-04-22 15:29:11 Slp:   ConfigObjectType = Microsoft.SqlServer.Configuration.ClusterConfiguration.ClusterIPAddressPrivateConfigObject
    (01) 2015-04-22 15:29:11 Slp:   FeatureName = SQL_Engine_Core_Inst
    (01) 2015-04-22 15:29:11 Slp:   FeatureCpuType = Cpu64
    (01) 2015-04-22 15:29:11 Slp:   FeaturePackageId = sql_engine_core_inst
    (01) 2015-04-22 15:29:11 Slp:   FeatureClusterState = CompleteFailoverCluster
    (01) 2015-04-22 15:29:11 Slp: Creating IPv4 address 'SQL IP Address 1 (SQLADFS)'.
    (01) 2015-04-22 15:29:11 Slp: Creating cluster resource 'SQL IP Address 1 (SQLADFS)' of type 'IP Address' in group 'SQL Server (ADFS)'
    (01) 2015-04-22 15:29:11 Slp: Bringing IP address resource 'Type='IP Address' NetworkName='Cluster Network 1' Group='SQL Server (ADFS)' Resource='SQL IP Address 1 (SQLADFS)'' online
    (01) 2015-04-22 15:29:11 Slp: Bringing cluster resource 'SQL IP Address 1 (SQLADFS)' online
    (01) 2015-04-22 15:29:12 Slp: Prompting user if they want to retry this action due to the following failure:
    (01) 2015-04-22 15:29:12 Slp: ----------------------------------------
    (01) 2015-04-22 15:29:12 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2015-04-22 15:29:12 Slp: Inner exceptions are being indented
    (01) 2015-04-22 15:29:12 Slp:
    (01) 2015-04-22 15:29:12 Slp: Exception type: Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException
    (01) 2015-04-22 15:29:12 Slp:     Message:
    (01) 2015-04-22 15:29:12 Slp:         The cluster resource 'SQL IP Address 1 (SQLADFS)' could not be brought online.  Error: There was a failure to call cluster code from a provider. Exception message: Generic failure
    . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
    (01) 2015-04-22 15:29:12 Slp:         .
    (01) 2015-04-22 15:29:12 Slp:     HResult : 0x86d8003a
    (01) 2015-04-22 15:29:12 Slp:         FacilityCode : 1752 (6d8)
    (01) 2015-04-22 15:29:12 Slp:         ErrorCode : 58 (003a)
    (01) 2015-04-22 15:29:12 Slp:     Data:
    (01) 2015-04-22 15:29:12 Slp:       resourceName = SQL IP Address 1 (SQLADFS)
    (01) 2015-04-22 15:29:12 Slp:       errorMessage = There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state
    to perform the requested operation.
    (01) 2015-04-22 15:29:12 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException@58
    (01) 2015-04-22 15:29:12 Slp:       DisableRetry = true
    (01) 2015-04-22 15:29:12 Slp:     Inner exception type: Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException
    (01) 2015-04-22 15:29:12 Slp:         Message:
    (01) 2015-04-22 15:29:12 Slp:                 There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The
    group or resource is not in the correct state to perform the requested operation.
    (01) 2015-04-22 15:29:12 Slp:                 .
    (01) 2015-04-22 15:29:12 Slp:         HResult : 0x86d70002
    (01) 2015-04-22 15:29:12 Slp:                 FacilityCode : 1751 (6d7)
    (01) 2015-04-22 15:29:12 Slp:                 ErrorCode : 2 (0002)
    (01) 2015-04-22 15:29:12 Slp:         Data:
    (01) 2015-04-22 15:29:12 Slp:           ExceptionMessage = Generic failure
    (01) 2015-04-22 15:29:12 Slp:           StatusCode = 5023
    (01) 2015-04-22 15:29:12 Slp:           Description = The group or resource is not in the correct state to perform the requested operation.
    (01) 2015-04-22 15:29:12 Slp:           WatsonData = Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException@2
    (01) 2015-04-22 15:29:12 Slp:         Stack:
    (01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
    (01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.ClusterResource.Online(Int32 timeout)
    (01) 2015-04-22 15:29:12 Slp:         Inner exception type: System.Management.ManagementException
    (01) 2015-04-22 15:29:12 Slp:             Message:
    (01) 2015-04-22 15:29:12 Slp:                         Generic failure
    (01) 2015-04-22 15:29:12 Slp:             HResult : 0x80131501
    (01) 2015-04-22 15:29:12 Slp:             Data:
    (01) 2015-04-22 15:29:12 Slp:               WmiErrorCode = Failed
    (01) 2015-04-22 15:29:12 Slp:               WatsonData = Failed@5023
    (01) 2015-04-22 15:29:12 Slp:               Description = The group or resource is not in the correct state to perform the requested operation.
    (01) 2015-04-22 15:29:12 Slp:               ErrorType = 1
    (01) 2015-04-22 15:29:12 Slp:               Operation = ExecMethod
    (01) 2015-04-22 15:29:12 Slp:               ParameterInfo = MSCluster_Resource.Name="SQL IP Address 1 (SQLADFS)"
    (01) 2015-04-22 15:29:12 Slp:               ProviderName = WinMgmt
    (01) 2015-04-22 15:29:12 Slp:               StatusCode = 5023
    (01) 2015-04-22 15:29:12 Slp:             Stack:
    (01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
    (01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject
    inParameters, InvokeMethodOptions options)
    (01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.WMIInterop.Resource.BringOnline(UInt32 TimeOut)
    (01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
    (01) 2015-04-22 15:29:12 Slp: ----------------------------------------
    We have tried to reinstall the servers multiple times, without result.
    Can anyone assist us in this case?
    Thanks
    Kind Regards
    Julian

    Hi Darryl,
    thanks for your supply.
    We don't have an DHCP in the Cloud. System Center DHCP is used for assigning IP addresses and routing inforamtion to the vms.
    This works fine for assigning IP addresses to the vms.
    At my current point of understanding network virtualisation with system Center, we do not have an alternative to this way of assigning IP addresses.
    Kind Regards
    Julian

  • 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 with Always on

    Hi
    I have 2 sites Ho & DR
    I have 2 sql servers in each site
    I need to make on each site sql cluster and between the 2 sites we need to make always on
    please need the steps for this scenario
    MCP MCSA MCSE MCT MCTS CCNA

    Hi Yasser,
    According to your description, you want to setup a disaster recovery solution combining SQL Server Failover Cluster in Primary Datacenter and Availability Group on a SQL Server Failover Cluster in Secondary Datacenter. Assume that, in the Primary DataCenter,
    SQL_PV is the FCI instance and CLP_1 and CLP_2 are the two nodes. In the Secondary DataCenter, SQL_SV is the FCI instance and CLS_1 and CLS_2 are the two nodes as the screenshot below shows.
    To achieve the goal, you could follow the steps below:
    1.Add two nodes CLS_1 and CLS_2 from secondary datacenter into the existing
    Windows Server Failover Cluster(WSFC). Please note that all nodes for an availability group must exist on a single WSFC within the same Active Directory domain, even between datacenters.
    2.Configure Shared Storage for both CLS_1 and CLS_2 nodes.
    3.Install FCI instance of SQL 2012 Enterprise edition using "New SQL Server Failover Cluster Installation" and join the other secondary node using Add node to a SQL Server failover Cluster.
    4.Enable Always on Availability Group on newly installed FCI.
    5.Define the possible owner for each SQL Server FCI as the following:
    a. Go to "SQL Server" services on the Cluster instance under SQL_PV group and go to SQL Properties. Under Advanced Policies, choose only CLP_1 and CLP_2 as possible owner for SQL_PV.
    b. Go to "SQL Server" services on the Cluster instance under SQL_SV group and go to SQL Properties. Under Advanced Policies, choose only CLS_1 and CLS_2 as possible owner for SQL_SV.
    For more information about the process, please refer to Scenario 2 in the article:
    http://www.mssqltips.com/sqlservertip/3150/adding-sql-server-alwayson-availability-groups-to-existing-failover-clusters/
    Regards,
    Michelle Li
    If you have any feedback on our support, please click
    here.

  • Disk and tempdb configuration for multiple Instances in one SQL cluster

    Hi Everyone ,
      I am in planing to build SQL Cluster on Blade server . Two blades are allocated for SQL. and planning to cluster those two blades. It will be windows 2012R2 and SQL 2012/2014. Initially it was plan to put most of database on one SQL instance. but
    due to other requirements I will be Installing more SQL Instance on same cluster. 
    for now Everything will be on  RAID 10 but do not have more details about storage yet that how it will get configured
    256 GB Ram on Each blade server.
    1) what are the Disc configuration recommendation for data and log files when each instance get added?
    2) what are the Disc configuration recommendation for  tempdb files when each instance get added?
    3) Each Instance Tempdb file on Same drive is good practice?
    Any other Best practices should follow for this setup?
    Thank you ....
    Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach A.Shah

    1) what are the Disc configuration recommendation for data and log files when each instance get added?
    Keep both the sql instances in diffèrent drives.read the below link for RAID levels and according to your usage you can cofigure it..
    http://technet.microsoft.com/en-us/library/ms190764%28v=sql.105%29.aspx
    Storage best practice.
    http://technet.microsoft.com/en-us/library/cc966534.aspx
    2) what are the Disc configuration recommendation for  tempdb files when each instance get added?
    Its good to have sepreate drive for tempdb and each instance too with correct allocation or configuration..RAID5
    for data if you must, but have to keep a spare drive around for that.
    Best is 10 everywhere. If that's too expensive, then 1 or 10 for log and 5 for data (and 10 for TempDB)
    RAID 5 is terrible for logs because it has a high write overhead. Tran logs are write-heavy, not read-heavy.
    3) Each Instance Tempdb file on Same drive is good practice?
    Tempdb configuration is depends, its completelty based on your server and tempdb usage..Make sure to have equal size for all the files in tempdb, As a general rule, if the number of logical processors is less than 8, use the same number of data files
    as logical processors. If the number of logical processors is greater than 8, use 8 data files and then if contention continues, increase the number of data files by multiples of 4 (up to the number of logical processors) until the contention is reduced to
    acceptable levels or make changes to the workload/code.
    http://www.confio.com/logicalread/sql-server-tempdb-best-practices-initial-sizing-w01/#.U7SStvFBr2k
    http://msdn.microsoft.com/en-us/library/ms175527(v=sql.105).aspx
    http://www.sqlskills.com/BLOGS/PAUL/post/A-SQL-Server-DBA-myth-a-day-(1230)-tempdb-should-always-have-one-data-file-per-processor-core.aspx
    Raju Rasagounder Sr MSSQL DBA

  • 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.

Maybe you are looking for