Availability group Automatic failover

Hi
setup a simple 2 node AG, sync. (SQL 2014 enterprise on windows 2012R2 standard)
if I set it as manual failover everything works as expected. however when I switch to automatic failover and stop SQL service on the primary node the AG resource in cluster does offline and doesn't failover to secondary node.
both nodes are available to the cluster resourse.
would appreciate your feedback as to what might be the reason
Regards
Shaunt

Hi,
I would verify if Database Availability Group means AlwaysOn Availability Group.
How did you set the FailureConditionLevel?
Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
There are two useful articles may be helpful:
SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
Thanks.
Tracy Cai
TechNet Community Support
Hi,
Thanks for the reply.
It's an AlwaysOn Availability Group.
In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
I'll take a look at the links you provided.
Regards,
Bob

Similar Messages

SQL 2012 Database Availability Group - Force Automatic Failover

Hi All,
I'd appreciate some help in understanding the following scenario in my test environment.
I have created a DAG with 2 replica servers (both of which are HyperV VM's running W2012 Std).
From a client PC in my test lab, I can connect to the virtual listener of my DAG and confirm via the "select @@servername" command that I am connecting to the primary replica server.
Using the Failover Wizard, I can easily move to primary instance between my 2 nodes and the command above confirms that the primary replica server has changed. So far so good.
What I wanted to test, was what would happen to my DAG in the event of a complete loss of power to the server that was acting as the primary replica server. At first, I thought I would stop the SQL Server service on the primary server, but this did not result
in my DAG failing over to the secondary replica. I have found out that the only way I can do this is by effectively shutting down the primary server in a controlled manner.
Is there any reason why either stopping the SQL Server service on the primary replica, or indeed forcing a power off of the primary replica does not result in the DAG failing over to the secondary replica?
Thanks,
Bob

Hi,
I would verify if Database Availability Group means AlwaysOn Availability Group.
How did you set the FailureConditionLevel?
Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
There are two useful articles may be helpful:
SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
Thanks.
Tracy Cai
TechNet Community Support
Hi,
Thanks for the reply.
It's an AlwaysOn Availability Group.
In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
I'll take a look at the links you provided.
Regards,
Bob

SQL AlwaysOn Availability Group modifies preferred owner node on move/failover

I have a two node Windows Server 2012 R2 failover cluster with two SQL Server 2012 Enterprise AlwaysOn Availability groups configured. Within the cluster I have configured a preference order on which node a AlwaysOn Availability Group should run.
Get-ClusterGroup -Name "AlwaysOn1" | Set-ClusterOwnerNode -Owners "node1","node2";
Get-ClusterGroup -Name "AlwaysOn2" | Set-ClusterOwnerNode -Owners "node2","node1";
After configuring the preference and retrieving the preference order it is configured as it should be. When I do a failover the preference order is adjusted to first the node it currently runs on and second the other node instead of leaving the preference
order as it was. It doesn't matter if I use the PowerShell "Move-ClusterGroup" or the "ALTER AVAILABILITY GROUP [AlwaysOn1] FAILOVER" T-SQL command. From the cluster log it is shown that the preference is modified after the resource
has been moved.
INFO [GUM] Node 2: executing request locally, gumId:15859, my action: /rcm/gum/SetGroupPreferredOwners, # of updates: 1
INFO [RCM] rcm::RcmGum::SetGroupPreferredOwners(AlwaysOn1,<vector len='2'>
The default groups within the cluster "Available Storage" and "Cluster Group" keep their preference setting when configured (only configured for testing to verify it has to do with the SQL Server Availability Group resource type).
The Windows Server 2012 R2 servers are updated using the latest Windows Updates and SQL 2012 has build number 11.0.5556.
For other cluster groups which I have configured in the past like file, Hyper-V (used for affinity to get VM's which have a lot of traffic between them within the same virtual switch to reduce latency and additional hops. it would be nice if vNext will have
a affinity option for cluster groups besides the anti-affinity within the current version)
I would like to know if someone could explain why the SQL Server Availability Group resource always modifies the group preference. I might understand this with a three node cluster where the first two are running in Synchronous commit mode and the third
one in Asynchronous commit mode.
Thanks in advance,
Dennis van den Akker

Hi Dennis van den Akker,
Do not use the Failover Cluster Manager to manipulate availability groups, for example:
Do not add or remove resources in the clustered service (resource group) for the availability group.
Do not change any availability group properties, such as the possible owners and preferred owners. These properties are set automatically by the availability group.
Do not use the Failover Cluster Manager to move availability groups to different nodes or to fail over availability groups. The Failover Cluster Manager is not aware of the synchronization status of the availability replicas, and doing so can lead to extended
downtime. You must use Transact-SQL or SQL Server Management Studio.
The related KB:
Failover Clustering and AlwaysOn Availability Groups (SQL Server)
https://msdn.microsoft.com/en-us/library/ff929171.aspx
The similar thread:
SQL Server Clustering 2008 (Multi Node)
https://social.msdn.microsoft.com/Forums/sqlserver/zh-CN/c35fe863-3fed-4a6e-830b-b79aa032c198/sql-server-clustering-2008-multi-node?forum=sqldisasterrecovery
Best Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Failover Occured manually or automatically (SQL Server AlwayOn with Availability Groups)

Hello everyone,
we had a Failover today on a Windows Server 2012 Failover Cluster with SQL Server Always On and now I'd like to know if the failover was done by the Cluster (or SQL?) or manually from a user...
In the Cluster Log I can see following entry: INFO [RCM] rcm::RcmApi::MoveGroup: (CVGID2, 1, 0, MoveType::Manual )
So I assume that the failover was done by a user... But: I can see only Movetypes of "Manual" in the cluster log of this always on system...
So my question is: Is it possible that since SQL Server (Always On) is kind of "driving" the cluster, that if it makes an automatic failover the Cluster will log this as a "manual" failover because it was not done by the Cluster service
itself?
Thanks for any help!
Ville

Hi Ville,
When we meet this event it indicate it is not an issue since the failover was triggered manually.
The related third party article:
dbi services Blog
http://www.dbi-services.com/index.php/blog/entry/wsfc-manual-or-automatic-failover-that-is-the-question
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

please post you question on failover clusters in the cluster forum. THey will explain how this works and point you at scipts.
You should also look in the Gallery for cluster management scripts.
¯\_(ツ)_/¯

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster) with scrpiting

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

You are trying to implement manually what should be happening automatically in the cluster. If the primary SQL Server becomes unavailable in the data center, it should fail over to the secondary SQL Server automatically. Is that not working?
You also might want to run this configuration by some SQL experts. I am not a SQL expert, but if you have both hosts in the data center in a cluster, there is no need for replication between those two nodes as they would be accessing
the database from some form of shared storage. Then it looks like you are trying to implement Always On to the DR site. I'm not sure you can mix both types of failover in a single configuration.
FYI, it would make more sense to establish a file share witness in your DR site instead of placing a third node in the data center for Node Majority quorum.
. : | : . : | : . tim

Perform Forced Manual Failover of Availability Group (SQL Server 2012) and WSFC (Windows Server Failover Cluster)

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Fail-over Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Fail-over Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Fail-over of Availability Group (SQL Server) and WSFC (Windows Server Fail-over Cluster)
Can you please guide me for script writing for automatic fail-over in case of primary data-center outage?

+1 to David's comment. I would not suggest to run a script automatically. During such failover you might have data loss and decision has to be made with business owners during disaster.
During such situation, you need to start cluster service in force quorum mode (/fq switch) and then perform manual failover of AG to DR site.
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

2012 SQL AlwaysOn Availability Group - JDBC re-connection not happening in case of Multisubnet failover

Hi There,
Having some problem with MultiSubNet AG failover re-connection using SQL JDBC driver 4. Details given below.
SETUP:
We have a three node 2012 Windows Server Cluster, on top it we have 2012 SQL Sever AlwaysOn Availability Group.
Two nodes are in one subnet and other in a different subnet to make this as a multisubnet AlwaysOn AG.
An AG Listener is configured with a DNS name and two VIP assigned (For two subnet) to it. We were able to failover from one subnet to other using the SQL Studio successfully.
NEED:
We have a java application which will be connected to AG Listener name. In case of failover, automatic re-connection to DB/AG Listener name should happen.
For this we use "sqljdbc4.jar" and added
'multiSubnetFailover=true' in our connection string. The connection String is given below.
cURL="jdbc:sqlserver://testsqlag:1433;databaseName=SalesDB;multiSubnetFailover=true;loginTimeout=200;applicationName=MyApp";
THE PROBLEM:
In case of AG failover, driver is not trying to re-connect to the AG Listener name. Not sure how to make it work.
Is this supported in SQL Server 2012 ?
Thanks,
Krishna.

Hi Sean,
Thanks for your answer.
I looked at the link earlier, but it was not very clear that, whether the mssql jdbc driver will automatically re-connect to AG Listener name in case of failure of Primary replica which will result in Multisubnet failover. Pasted the confusing statements
from the link
http://msdn.microsoft.com/en-us/library/gg558121(v=sql.110).aspx.
Also, because a connection can fail because of an availability group failover, you should implement connection retry logic, retrying a failed connection until it reconnects.
Connecting With MultiSubnetFailover :
During a multi-subnet failover, the client will attempt connections in parallel. During a subnet failover, the Microsoft JDBC Driver for SQL Server will aggressively retry the TCP connection.
Thanks,
Krishna.

Failover cluster vs Availability Groups

I am trying to understand the advantages of FCI over AG and vice versa. I have read several articles but none talks about when one should use FCI over AG or AG over FCI.
Basically I am going to make a SharePoint farm and for that I need to decide whether I should go for FCI or AG. Any help is appreciated.

Failover cluster is an instance protection level and
Availability Groups is a database protection level.
>>>>2. We can overcome this problem by using RAID (correct me if I am wrong)
Can you expand a little bit? What RAID configuration did you mean? How RAID protects you from let me say network issue caused failover?
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
So isn't instance level protection better than database level protection because in instance level, databases are automatically protected?
My understanding of RAID is if some thing happens to primary SAN then the other secondary SAN will takes its place depending on RAID configuration!?

Setting Up Alerts for Always on Availability Groups Failover

Hi Folks,
In SQL Server 2008R2 we set up alerts for Mirroring failover using WMI Alerts. As Like this.
Now we need to configure similar alerts for Always on Availability Groups(AAG) in SQL Server 2012, but it seems that there is no such WMI Alerts or any standard way to set up the alerts for getting notified for AAG Failover. Click
Here
Should I manually Create a SQL Agent Job using
these DMVs and schedule it at frequent Interval to get notified about any AAG failover or is there any standard way as for mirroring Failover alerts? Any suggestion or help is appreciated.
Pranshul Gupta

Maybe you wanna have a look at this:
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/13/monitoring-alwayson-health-with-powershell-part-1.aspx
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/13/monitoring-alwayson-health-with-powershell-part-2.aspx
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/15/monitoring-alwayson-health-with-powershell-part-3.aspx
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/15/the-always-on-health-model-part-4.aspx
Bodo Michael Danitz - MCT, MCITP - free consultant - performance specialist - www.sql-server.de

Automatically add a Database to an Availability Group

Dears, I need to know if there any way to configure SQL always on to automatically add new Databases to an Availability Group.
Ayman Saleh

Hi can any one update the TSQL script here:
Requirements:
Every time the newly created or added databases should be full backed up once in the shared location with
automated script.
Newly created database should be added into always on group and should be added to available replica automatically
with the TSQL script

Cluster failover but Availability Group do not

We recently had an issue where a file share was unavailable. It caused the cluster to failover. However, the Availability Group did not failover. The application was trying to connect to the secondary database which it couldn't since the failover had not
happened. We are set up using Quorum with a File Share Witness. We have manually failed this over successfully. Any ideas on why the Availability Group did not failover would be most appreciated. We do not have any experts in this area so please help us figure
out where to look.

Availability listener are a good way of providing a fault tolerance for the client and in addition providing read-intent or read-only access to the secondary replicas. If you need it, you can go through these documentations. They show the why and how to
set them up. If you have any additinal questions let me know.
http://msdn.microsoft.com/en-us/library/hh213417.aspx
Always make sure to configure AG relevenat parts through SSMS not the cluster Service manager itself. There are some points that you might want to tweak in the cluster manager, but most parts should be configured (and for most cases they are sufficient)
in the SQL Server related tools (SSMS)
-Jens
Jens K. Suessmeyer http://blogs.msdn.com/Jenss

Moving the Reporting Services and Report Server DB into AlwaysON Availability Group

I have configured the new set of SQL 2012 AlwaysOn Availability Group and need to move the SSRS and it's Report Server DB into that Availability Group.
Can anyone give tell me the steps to do this move?
Can I just backup the ReportServer DB into the AG server then import that DB into the SSRS running on the new AlwasyOn AG SQL?

Hello,
Based on your description, it seems that you want to move the Report Server database to a different server. If so, both the reportserver and reportservertempdb databases must be moved or copied together. You can move the databases by using Detaching
and Attaching or Backup and Restore.
What's more, you should also backup the encryption keys for the report server database you want to move and then restore to the new server.
You can configure report server databases in Always On Availability Group to be part of a replica; however Reporting Services will not automatically use a different replica for the report server databases when a failover occurs
Reference:
Moving the Report Server Databases to Another Computer
Reporting Services with AlwaysOn Availability Groups (SQL Server)
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Orchestrator 2012 R2 on SQL 2012 SP1 Availability Group

Hi all,
I've recently setup a new install of SCOrch 2012 R2 on a SQL 2012 SP1 Availability Group. Everything went smooth and appears to be functioning correctly up until a failover occurs (manual or automatic). Once there is a failover between database
nodes, the Orchestrator servers (Mgmt and Runbook) lose connectivity to the database and will not reconnect until the services are restarted and then they work again.
Has anyone setup Orchestrator on an Availability Group and are you seeing similar issues from a failover?
Thanks!
Jon

Hi Jon,
has each member of the availability group the same master key to read encrypted data like passwords and the license code?
https://blog.uvm.edu/jgm/2013/05/28/sql-2012-tde-and-availability-groups/
Btw, if you still interested in a SAP IP:
http://www.sc-orchestrator.eu/index.php/integration-packs/integration-pack-fuer-sap-vip4sap
Regards,
Stefan
www.sc-orchestrator.eu ,
Blog sc-orchestrator.eu

Multi Site SQL High Availability group

Hi,
We have our primary Data Centre where we have 2 MS SQL 2012 Enterprise Servers and 2 SharePoint 2013 Enterprise servers.
We have SQL High Availability group implemented on our primary Site (Site A)
Site A has subnet of 192.168.0.0.
We recently added a new DR Site (Site B). Site B we have MS SQL 2012 Enterprise Servers. Site B have a subnet of
172.1.1.0
Both sites are connected via a VPN Tunnel. MS SQL 2012 Enterprise Server on Site B has been added in have SQL High Availability
group of Site A.
SQL High Availability group have 2 IPs 192.168.0.32 and 172.1.1.32. SQL Listener have 2 IPs 192.168.0.33 and 172.1.1.33
We want to make sure that if Site A completely down then Site B work as an active Site. But when Site A down we are unable
to ping High Availability group and Site B is unable to work as active site. SQL and SharePoint services are completely down.
Site A has AD(Primary Domain Controller) and Site B has ADC(Additional Domain Controller).
Site A has witness server.
We are using Server 2012 Data Centre
Please suggest.
Farooq

SharePoint is not the same as any other applications. The DR site has to be a completely different farm from your production. This means that the SharePoint_AdminContent and config databases on both farms are different and should not be included in the Availability
Group (they do not support asynchronous Availability Group.) Only content databases and other SharePoint databases supported in an Availability Group should be included as per this
TechNet article. Have a look at this
blog post for your networking configuration.
The reason your Windows cluster service goes down in the DR data center when the when your primary data center goes down is because the cluster has no majority votes. You have 4 available votes in your cluster - 3 in the primary data center in the form of
the 2 Availability Group replicas and the witness server and 1 in the DR data center. If the Windows cluster does not have majority of votes, it automatically shuts down the cluster. This is by design. That is why when this situation happens, you need to force
the cluster to start without a quorum as described in
this article (Windows Server 2012 R2 introduced the concept of dynamic witness and dynamic quorum to address this concern.) By default, the IP address of the Availability Group listener name will be registered on all of the DNS servers if the cluster is
running Windows Server 2012 and higher (this is the RegisterAllProvidersIP property that Samir mentioned.) However, you need to flush the DNS cache on the SharePoint web and application servers and point them to the correct IP address on the DR server after
failover. This is because the default TTL value of the Availability Group listener name is 20 minutes.
It is important to define your DR strategies and objectives when designing the architecture to make sure that the solution will meet your goals. This will also help you automate some of the processes in the DR data center when failover or a disaster occurs.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Availability group Automatic failover

Similar Messages

Maybe you are looking for