Failover Cluster Instance always on
we have two node cluster active passive with shared storage , I have setup AlwaysOn as DR on standalone instance
daily morning on failover cluster events, i am getting following critical events
On windows log i couldn't see much information, please help me
Can you provide the version of Windows Server that you are using as cluster nodes? Behavior will be different between Windows Server 2008, 2012 and 2012 R2. While in the past, changing the NodeWeight property of a cluster node may be an appropriate solution,
Windows Server 2012 R2 introduced dynamic witness where a witness is configured to either have a vote or not have a vote depending on the state of the cluster and the quorum. Combined with dynamic quorum (which was introduced in Windows Server 2012,) which
dynamically adds or removes a vote from a node depending on the status, the behavior will be different depending on what version of Windows Server you are running. A more appropriate approach (if you are running Windows Server 2012 or 2012 R2) is to configure
the LowerQuorumPriorityNodeID property of the cluster.
http://technet.microsoft.com/en-ca/library/dn265972.aspx
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course
Similar Messages
-
Exploring AlwaysOn Failover Cluster Instances in SQL Server 2014 Tecnet Labs
I like the Labs and have found them very usful. I have a problem with: Exploring AlwaysOn Failover Cluster Instances in SQL Server 2014. The lab starts but hangs on opening SQLONE and the Manual never loads. I have tried coming out and starting again but
get returned to the same failing session. I thought I would mention it here as the is no way to feedback a response as the appraisal only happens once the lab is completed, i.e. no apparent link on the lab site. The session ends when the HOL is reported
as not responding.Hi,
I'd try this first:
https://vlabs.holsystems.com/vlabs/SystemRequirements.aspx
If that's no help, try the 'Help and Support' link on this page:
https://vlabs.holsystems.com/vlabs/technet?eng=VLabs&auth=none&src=vlabs&altadd=true&labid=12693#
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing) -
I haven't had the opportunity to implement a SQL Server Failover Cluster Instance (FCI) for over 10 years and that was done with two physical, identical database servers way back in the day of Windows Server 2003 and SQL Server 2000 (old school).
Can a SQL Server 2008 R2 Failover Cluster Instance (FCI) be implemented between two Hyper-V hosted virtual machines? The environment in question already has Windows Server 2012 R2 Hyper-V hosts in place, so I'm just looking to see if this is even
possible and/or supported when utilizing virtual machines.
The client in question is currently using SQL Server 2008 R2 instances running on Win2008R2, Win2012, and Win2012R2, but I'd also be interested how this can be done or not with SQL Server 2012 or 2014 as well. Thanks in advance.
Bill ThackerYes, it can be done with Hyper-V guests. In fact, with Windows Server 2012 R2 Hyper-V, guests can use the Shared VHDX feature for shared storage used by Windows clusters. The guests can run Windows Server 2008 and higher provided that the Hyper-V Integration
Services are installed to support Shared VHDX. The only challenge here is making the Hyper-V hosts highly available as well, running it on WSFC.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course -
Dedicated network for AlwaysON replication traffic when a replica is a Failover Cluster Instance
Hi,
We are planning to setup dedicated network for our Availability Group replication traffic. We have a Failover Cluster Instance as the primary replica and a standalone SQL server instance as the secondary.
I understand that we will need to manually configure the database mirroring endpoints on both the replicas to listen on the specific IP.
But how do I configure the database mirroring endpoint on the Failover Cluster Instance ?
Please help.
Thanks and Regards,
JishaIf you have a dedicated network for your Availability Group replication traffic between the FCI and the standalone instance, you need to identify if there will be other network services included in the mix. For example, your public network is already using
it's own DNS server by virtue of Active Directory integration. Your dedicated network for replication traffic may or may not have its own DNS server so configuring the endpoints would involve using either IP addresses like the one highlighted in the
blog post or using hosts file with fully qualified domain names so you can use them when creating the endpoints
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course -
Transactional replication from a failover cluster instance to a SQL Server Express DB
Hello,
I have been poking around on Google trying to understand if there are any gotchas in configuring transactional replication on a instance DB of a failover cluster, to a SQL Server Express DB. Also, this client would like to replicate a set of tables between
two instances DB's which both reside on nodes of the cluster.
Everything I've read suggests there is no problem using transactional replication on clustered instance as long as you use a shared snapshot folder. I still have some concerns:
1) Should the distributor need to live on a separate instance?
2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
inconsistency between the publisher and subscriber.
There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
Thanks in advance.1) Should the distributor need to live on a separate instance?
Answer: It is recommended to configure the distributor on the different server, but it also be configured on Publisher/subscriber server. (Subscriber in our case is not possible as its a Express edition)
2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
inconsistency between the publisher and subscriber. There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
Answer: If you configure both publisher and distributor on the same server and the SQL instance is failed over, the data synchronization/replication is suspended till the instance comes online.
Once the instance is up,all the replication jobs will start again and it will continue to synchronize the data to subscriber. No manual intervention is required. -
Service Accounts for Reporting Service in SQL Server Failover Cluster setup
I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
There are 2 options to configure the service account for SSRS:
Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
http://msdn.microsoft.com/en-us/library/ms143504.aspx
which is the recommended one? is it option 2?
There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
Security Note: Always run SQL Server services by using the lowest possible user rights. Use a MSA or virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
directly to a service SID, where a service SID is supported.
Thanks very much for your help!Hi Luo Donghua,
In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
Of cause, you can also use domain accounts in your clustering.
Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support -
SQL Server 2012 Failover Cluster Setup
I have to set up a Lab Test environment for SQL Server 2012 with failover clustering. What are the most cost effective specifications for H\W & S\W. AFAIK Apart of Enterprise edition, Standard edition can support failover clustering for upto
2 nodes with one node in passive mode. Somewhere (Here) I got that it is possible to configure SQL Server failover clustering On SQL
Server 2012 Developer edition. Also Is it possible to use Windows 7 Platform with SQL Server 2012 Developer Edition for configuring Always on Failover Clustering. Although I have researched alot, but puzzled. Seeking for experts advise. Thanks in advance.
Pranshul GuptaYes you can configure and install in windows 7.. but make sure you have made all the proper updates as per the microsoft suggestion..
Software and hardware requirments for sql 2012
http://msdn.microsoft.com/en-us/library/ms143506%28SQL.110%29.aspx
http://www.yourdba.com/?p=123
http://resources.arcgis.com/en/help/system-requirements/10.2/index.html#//015100000070000000
Developer Edition..
SQL Server 2012 Developer Edition will continue to be part of the SQL Server 2012 family. The Developer edition provides the same feature set as the Enterprise edition. However, it's licensed per developer and can't be used for production work.
Clustering FAQ's
http://www.brentozar.com/archive/2012/02/introduction-sql-server-clusters/
SQL Server licensing :
http://www.microsoft.com/sqlserver/en/us/future-editions/sql2012-licensing.aspx
http://www.microsoft.com/sqlserver/en/us/get-sql-server/how-to-buy.aspx
Overview and support :
http://msdn.microsoft.com/en-us/library/cc645993.aspx
FCI Failover Cluster Instances (SQL Server)
http://technet.microsoft.com/en-us/library/ms189134.aspx
AlwaysOn Availability Groups (SQL Server) -- AG's
http://technet.microsoft.com/en-us/library/hh510230.aspx
Raju Rasagounder Sr MSSQL DBA -
Dear All...................I have a two-2 node sql server 2012 sp1 failover cluster.........I need to turn "Always On" on one of the databases.
1. Is it really applicable in this scenario?
2. Would I get any benefit from it?
3. Is it even possible?
thank in advance.Raju is correct. Just to add… AlwaysOn is an term which covers two features Failover Cluster Instances (AlwaysOn FCI) and Availability Group (AlwaysOn AG). For both the features you need to have Windows Server Failover Cluster (WSFC) feature.
If you compare FCI and AG, below are the differences.
For FCI, you need to have shared storage between nodes and at a given point of time, one SQL Instance would run on one of the node. In AG, there is no requirement of shared storage. You can have standalone instances on each nodes and configure AG between
them. Note that AG can also be configured between FCI and standalone instances (with some limitations)
AG can be used SQL Server 2012 onwards whereas FCI was available in earlier versions as well.
AG is database level feature whereas FCI is for whole instance of SQL Server.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle -
SQL Server Agent fails to connect to DB after enabling mirror on failover cluster
Hello:
We have multiple databases running in a Failover Cluster instance: SQL 2012SP1 on Server 2008 R2 failover cluster (NOT AlwaysOn). We are trying to add a high-performance mirror in a standalone instance for DR. My understanding is that should be a perfectly
normal, supported configuration.
The mirroring is working properly; however, the clustered SQL Server agent is unable to run jobs that run in the mirrored databases.
We get the following in the job log: Unable to connect to SQL Server 'VIRTUALSERVERNAME\INSTANCE'. The step failed.
There is a partner message in the agent log: [165] ODBC Error: 0, Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported. [SQLSTATE IMH01]
The cluster is not a mulitsubnet cluster. All hosts are connected to the same subnets and there is no storage replication. I can not find any place where I can adjust the connect string options for SQL Agent.
Any guidance or suggestions on how to resolve this would be appreciated.
~joeSQL Team - MSFT:
Thank you for taking the time to research and provide a clear answer.
This seems very much a workaround and very unsatisfactory.
You are correct, there is an IP dependency with OR condition. Moving to an AND condition is not viable for us. The whole point is to provide network redundancy. With an AND condition, if EITHER network interface fails, the service will go offline or fail
to come online without manual intervention. This is arguably worse for uptime than having a single interface available.
We are in process of rewriting all our SQL jobs to start in tempdb before transitioning to the appropriate target database. If this works for all of our jobs, I will mark the above response as answer.
Again, thank you for the answer.
Regards,
Joe M. -
Upgrading from SQL Server 2012 Standard to SQL Server 2014 Standard Failover Cluster
Goal: To upgrade my default instance from SQL Server 2012 to SQL Server 2014 in a failover cluster.
Given:
1) Operating System Windows 2012 R2
2) 2 Virtual Machines in a cluster with SQL Server as a Guest Cluster resource. The two VMS are called APPS08 and APPS09. They are our development environment that is setup similar to our production environment.
Problem: When running the SQL Server 2014 upgrade, I started on the VM that was not running the instance. I then moved onto upgrading on the node that was running the instance. As soon as the install attempt to failover the running instance
an install error occurred that it could not failover. After many install attempts I consistently received the error
The SQL Server Failover cluster instance name 'Dev01'
already exists as a cluster resource. Opening Failover cluster manager there is no record of a DEV01.
New Strategy: Create a SQLCluster called DEV07. At the end of the Install I get 'Resource for instance 'MSSQLSERVER' should not exists. Neither I nor my Windows 2012 guy understand what Resource the install may be referring to.
We do not see anything out of the ordinary.
Any suggestions as to what Resource may be seeing the default instance would be greatly appreciated.Hi PSCSQLDBA,
As your description, you want to upgrade the default instance in SQL Server cluster.
>> 'SQL Server failover cluster instance name 'Dev01' already exists as cluster resource'
This error could occur when there is a previously used instance name which may not be removed completely.
To work around the issue, please use one of the ways below.
1. At command prompt, type Cluster res. This command will list you all the resources including orphan resources. To delete the orphan resource, type Cluster res <resource name>/delete.
For more information about the process, please refer to the article:
http://gemanjyothisqlserver.blogspot.in/2012/12/sql-2008r22012-cluster-installation.html
2. Delete DNS entries, and force a replication of DNS to the other DNS servers.
For more information about the process, please refer to the article:
http://jon.netdork.net/2011/06/07/failed-cluster-install-and-name-already-exists/#solution
>> 'Resource for instance 'MSSQLSERVER' should not exist'
This error could occur when you already have MSSQLSERVER as a resource in the cluster, which may not be removed completely. To work around the issue, you could rebuild the SQL Server cluster node.
Regards,
Michelle Li -
BizTalk using a SQL failover cluster in IAAS?
The "BizTalk Offerings: Server, IaaS, and PaaS Feature List" (see
http://social.technet.microsoft.com/wiki/contents/articles/19743.biztalk-offerings-server-iaas-and-paas-feature-list.aspx) say that when running BizTalk as IAAS in Azure,
No Failover Cluster Instance (FCI) for SQL Server.
What does this mean?
Is it not possible to create a BizTalk instance which uses a SQL Server Failover Cluster in Azure?
Kind regards,
MartinHi Leonid,
Thanks for your answer. I got the impression that HA is possible now for SQL Server on Azure IAAS.
See also
http://blogs.msdn.com/b/microsoft_press/archive/2014/08/18/from-the-mvps-sql-server-high-availability-in-windows-azure-iaas.aspx
Kind regards,
Martin -
Windows Server 2012R2 Failover Cluster error with mounted volumes
Hi all,
I've a problem with mounted volume on a WSFC build on top of Windows Server 2012R2, the situation is:
M: is the volume hosting mounting points
disk-1, disk-2, disk-3 are volume mounted on M:\SomeFolder
Theese volumes are used by a SQL Server Failover Cluster Instance, but my problem is related to WSFC. I've set dependencies so disk-1, disk-2, disk-3 depend upon H:
If I try a failover of the role "SQL Server" I observe that when the disk come online in the other node they fail with this error:
Cluster resource 'disk-1' of type 'Physical Disk' in clustered role 'SQL Server (ISQL2014A)' failed. The error code was '0xaa' ('The requested resource is in use.').
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.
If I manually take offline H: and than bring it online and then manually take online all disk (1 to 3) they come online with no error.
I'm going crazy!I've found the root of the problem: the servers are virtual machine on a VMware ESX 5.5 infrastructure, VMware claims that on 5.5 multipath is supported for raw device mapping disks but disabling multipath (I've set to fixed path) the Windows Server Failover
Cluster stops to get problems.
Now we have opened a support call with VMware. -
DPM 2012 R2 CU4 protecting SQL 2014 AlwaysOn AG with Failover Cluster vs. DR location
Hello!
We have a problem protecting any Database of SQL 2014 AlwaysOn Availability Group with SQL Failover Cluster Instance when moved to DR location. Everything is protected using DPM 2012 R2 CU4 from Primary location.
FACTS
- all servers are Windows Server 2012 R2
- all servers are Virtual (except Hyper-V hosts obviously:)
- that means virtualization is based on Windows Server 2012 R2 Hyper-V
- all clusters (SQL, Exchange,...) are Guest Clusters on Hyper-V
- SQL 2014
- DPM 2012 R2 CU4
- Primary and DR location
SETUP
SQL
- Primary location: SQL 2014 Guest Cluster with SQL Failover Cluster Instance using Shared VHDX disks
- DR location: SQL 2014 Standalone using VHDX disks
- AlwaysOn Availability Group expands between the primary and DR location.
DPM
- Primary location: DPM 2012 R2 CU4
- DPM 2012 R2 CU4 Agents installed on every possible SQL 2014 Server.
SCENARIO
- DPM is backing up all the SQL Databases normally as long as they exist on any SQL Cluster Node on Primary location.
- As soon as any Database is moved to DR location, that Database is not backed up anymore with the following error.
DPM ERROR
Starting synchronization on SqlServerName\DatabaseName failed:
Error 104: An unexpected error occurred while the job was running.
Error details: The system cannot find the path specified (0x80070003)
Recommended action: Retry the operation.
TROUBLESHOOTING
- Tried to modify SQL Protection Group in DPM Server while Database was active on DR location
> error enumerating volumes or drives D:\, E:\, F:\ (I don't have exact error atm)
> this looks like DPM is not aware that DPM is active on DR location to me
- Checked Technet, blogs and forums; no useful information
QUESTION
Is this expected or by-design behavior? Is this a bug? I am aware there were quite some issues backing up AG's from DPM 2012 SP1 ans SQL 2012 on.
Does anybody have a lab of that kind to try it out?
Thank you!
Best Regards,
Damjan Grimšič
LpdOK. The issue has been resolved. Issue was related to possible Disks Owners in Failover Cluster Manager Console for SQL Cluster.
In Primary's site SQL Cluster Failover Manager Console / Storage / Disks.
SQL Server(s) from Secondary location need(s) to be unchecked as Possible owner(s) in Advanced Policies for all relevant Volumes.
Lpd -
Configure SSL SQL Server 2012 Cluster Instance
Hi,
I am trying to configure a SSL Certificate on a named clustered instance but i can't
This is the errorlog message
2014-12-11 14:28:51.49 spid10s Error: 17182, Severity: 16, State: 1.
2014-12-11 14:28:51.49 spid10s TDSSNIClient initialization failed with error 0xd, status code 0x38. Reason: An error occurred while obtaining or using the certificate for SSL. Check settings in Configuration
Manager. The data is invalid.
2014-12-11 14:28:51.49 spid10s Error: 17182, Severity: 16, State: 1.
2014-12-11 14:28:51.49 spid10s TDSSNIClient initialization failed with error 0xd, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The data is invalid.
2014-12-11 14:28:51.49 spid10s Error: 17826, Severity: 18, State: 3.
2014-12-11 14:28:51.49 spid10s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error
log.
2014-12-11 14:28:51.50 spid10s Error: 17120, Severity: 16, State: 1.
2014-12-11 14:28:51.50 spid10s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.Hi Jame,
According to your description, you encountered the error when you were trying to configure a named clustered instance to use SSL certificate.
Based on my research, the error 17182 "TDSSNIClient initialization failed with error 0xd, status code 0x38" occurs specifically because of the fact that the string under Certificate value cannot be properly converted back to a valid thumbprint
of the certificate.
A common root cause for these symptoms is an invisible character that may have been inadvertently added to the certificate's Thumbprint value, when it gets copied out of the Certificates snap-in's rich-edit control in MMC. For example, if the thumbprint
contains the Unicode character, then it may cause this issue, the following similar issue is for your reference:
http://blogs.msdn.com/b/sqljourney/archive/2013/07/23/when-using-ssl-sql-failover-cluster-instance-fails-to-start-with-error-17182.aspx
For more details and the resolution about this issue, please refer to the following article:
https://support.microsoft.com/kb/2023869?wa=wsignin1.0
If you have any question, please feel free to let me know.
Regards,
Jerry Li -
Witness Server in a failover cluster
Hi.
I was reading about this witness server in a failover cluster but always thought that the switch between active and passive would be automatic, never thought of a "vote" and a "quorum" to reach.
Under what circumstances do I need this quorum (and therefore a witness server) and what happens if I am even?
Does a witness server have necessarily to be a third one or can be set up as either the active or the passive one?
CheersHi,
In addition to Jared's suggestion, I would like to clarify the following things:
1. The witness server and its directory are used only for quorum purposes where there's an even number of members in the DAG.
2. The witness server should be in the same Active Directory forest as the DAG.
3. It is recommended to specify a Client Access server as the witness server for Exchange 2013 DAG.
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support
Maybe you are looking for
-
Version 10.0.42.34 crashes all browswers on Windows 7
The latest version of Flash crashes all browsers on Windows 7 home premium and I can't get 10.0.32.18 to install because it says it's not the latest version. I have downloaded and run the stand alone uninstaller and rebooted and no luck. How does the
-
Can I use the Time Capsule as a storage device for my Ipad?
I want to get an Ipad for my wife because all she does is surf the net, email, and photoshop pictures. Can I get an IPAD and a Time Capsule and use the Time Capsule as like a shared drive to push pictures from the Ipad to the Time Capsule? I do not w
-
Leopard dvd not recognized by macbook pro
hello, i have a macbook pro running 10.4.10 and it doesn't recognize the leopard installation dvd. the same dvd works on my G4 and was successful with the upgrade. the macbook just ejects the dvd after i insert it. i am able to play movie dvd's and/o
-
I have Office Mac for home and office. Can I use the same installation disk on an Ipd2?
-
Pavilion dv7 advanced boot options keyboard not working
1. Print screen key has never worked 2. In Advanced Boot Options screen, arrow keys do not function to select Safe Mode, Esc key does not work to cancel out of screen.