SQL Server Always On

Hi we are using SQL 2012 Enterprise edition, I tried to click on the always on availability tab from the SQL Server management studio, but it gets an error message "Enable the option from SQL server configuration manager". I checked the instance
properties and found always on high availability option from there. It displays the following message
'This computer is not a node in a failover cluster' and the option was in disabled. Please help me on this how to resolve this issue.
Thanks

Hi Karj,
Please check the following link , sure it will helps to resolve your Issue.
http://msdn.microsoft.com/en-us/library/ff878259.aspx
http://sqlmag.com/sql-server-2012/microsoft-sql-server-2012-alwayson-availability-groups-feature
DBA

Similar Messages

SQL Server Always on Availability

Test environment:
Just we took backup of master database from PRODUCTION (Always On) server then restored on QA server.
All DB's showing Recovery Pending. Now i want to delete all databases on QA. But while deleting Db's getting below error:
“ The database is currently joined to an availability group. Before you can drop the database you need to remove it from availability group”.
Since QA DB is standalone server we can't configure Always On or DB mirroring.
What is the alternative method for dropping or deleting all these databases with out configuring high availability?
This is only for testing. Once cleanup done we will restore DB's from backup.
Please suggest me. Actually this is customer requirement. Without restoring master we can achieve but i want to know the how to resolve this kind of errors.

I tested this by restoring the master of a HADR enabled instance onto a stand-alone instance.
DROP DATABASE AdventureWorks2012;
Msg 3752, Level 16, State 1, Line 1
The database 'AdventureWorks2012' is currently joined to an availability group.
Before you can drop the database, you need to remove it from the availatility group.
ALTER AVAILABILITY GROUP agAdventureOLTP REMOVE DATABASE AdventureWorks2012;
Msg 35221, Level 16, State 1, Line 2
Could not process the operation. AlwaysOn Availability Groups replica manager is disabled on this instance of SQL Server. Enable AlwaysOn Availability Groups, by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry
the currently operation. For information about how to enable and disable AlwaysOn Availability Groups, see SQL Server Books Online.
DROP AVAILABILITY GROUP agAdventureOLTP
Command(s) completed successfully.
DROP DATABASE AdventureWorks2012;
Command(s) completed successfully.
So yes, it seems to be possible to do this by first dropping the AG and then dropping the database.
However I'd be concerned about the amount of 'unnecessary' metadata left behind by this approach. I really think best option is to script out your users (look into sp_help_rev_login) and
objects and have a 'warm' server on standby for disasters.

SQL Server Always on Listerner doesnt realign to primary

We habve set up SQL Server 2012 Always on between 2 (I1 and I2) computers using the listener as a connection point.
I1 is primary (Read Write)
I2 is sub (Read Only)
If we connect via the Listener we get hooked to I1 (verifed using @@SERVERNAME)
and all sql executed changes flow as expected to I2
However when we do a failover (automatic or manual) so that I2 becomes primary and I1 is now sub the listener still connects to I1 as the base (using SSMS to verify) and tries to send all commands to I1. Which then fail as I1 has become readonly
as the sub.
Reconnecting seems to have no effect.
Is this expected behaviour for the Listener ? or should it have directed the connection to the new primary I2 ?
Do we have to drop all connections for the Listener to repoint to the new primary I2 ?
Is this a configuration issue on my end ?

Hello,
Did you configure the Quorum in the Windows Server Failover Cluster, which is required for Automatic failover?
What's more, automatic failover is supported only when the current primary and the secondary replica are both configured with failover mode set to AUTOMATIC and the secondary replica currently synchronized.
Reference:http://technet.microsoft.com/en-us/library/hh213151.aspx#AutomaticFailover
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

SQL Server Always On Multiple Instances

I have 2 instances on 2 server for each I have the default set up and then an instance called Test.
i.e. Server1, Server2 and Server1/Test, Server2/Test
I have set up "Always on", on the default instances, and have a database called Test on both so I know that is working correctly.
As soon as the Server1/Test and Server2/Test instances are set up it automatically picks up the Always On Group and Test database.
Is it possible to stop this as I would like to use the separate instance for different databases?
Thanks
Chris

UPDATE
Chris opened support case with Microsoft and fortunately it came to my notice. Based on our troubleshooting we found that it was connection to wrong instance via management studio "registered server"
After giving proper port, the issue was resolved.
Nice talking to you Chris. Thanks!
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

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]

SQL Server Alwayson availability groups automation

Hi all,
I had configured SQL Server always on availability groups on windows server 2012 and it was successful.
I’ve installed and successfully configured our SQL Server 2012 AlwaysOn 2-node windows cluster servers. I've gotten AlwaysOn working great, and our
Front End servers for the Intranet will be using SharePoint 2013. The glitch is that SharePoint 2013 is configured to add databases automatically to our SQL Server 2012 back end, but NOT to AlwaysOn. As we know “we must manually find, select, back-up and then
add those new databases individually to get them into AlwaysOn."
But wait; that can be quite a task, constantly checking the SQL Server back-end servers to see what databases were created, then having to add them
into AlwaysOn, 7/24!
Im looking for an automated script or process that will check for new databases, back those new databases up in FULL mode, (for being added to AlwaysOn, of course) then
add those databases to Always On, all automatically.
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
Regards,
SQL LOVER.

awaiting for responses.
Kindly help the bewlo request.
Newly created database should be added into always on group and should be added to available
replica automatically with the TSQL script and perform restoration.
There is no out of the box solution for this. You may want to created a SQL Job (PowerShell) which can detect database which is newly created and perform steps to add new database to AG.
1. take full backup.
2. Take log backup.
3. restore then on secondary.
4. Add database to AG
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

Two wistnesses in a SQL Server fail over group

Is it possible to have two witnesses in a SQL Server Always on Availability Group Fail Over Cluster? Our goal is to have redundant witnesses in an Azure availability set.
Thanks,
Mike

AlwaysOn uses Windows Failover Clustering for quorum. See, eg Understanding Quorum Configurations in a Failover Cluster
You can do this, but with Dynamic Quorum it's probably not helpful. If you loose your witness vote, the cluster will adjust the quorum requirements.
David
David http://blogs.msdn.com/b/dbrowne/

SQL 2012 Always On Availability Groups

Has anyone configured FIM SYnc, FIM Service and MSF in SQL 2012 Always On Availability groups
I do not believe we can configure the SQL connection string for FIM Sync or FIM Service to include "multisubnetfailover"
TIA
Nigel

I commented on this here:https://social.technet.microsoft.com/Forums/en-US/64f55628-3b5d-4d16-9044-dcbe7053581d/lack-of-support-for-fim-database-mirroring?forum=ilm2
Additional comments:
SQL Server Always On Failover Cluster Instances should be supported just as SQL Clustering is supported.
SQL Server Always On Availability Groups are not supported, just as Database Mirroring in synchronous mode (which is required for automatic failover) is not supported. I can't find authoritative statements of this on the web. But I know this to be the
case.
Ultimately, the reason for lack of support for mirroring (for automatic failover or in synchronous mode) is that the product group has said so (in conferences and webinars). Meaning the product group has not tested it or has and decided that it doesn't
work or adds risk.
Possible underlying reasons:
1) To do automatic failover with mirroring or Availability groups you must edit the connection string. The way FIM builds the connection string out of the components in the registry don't permit this.
2) Running mirroring in synchronous mode slows down performance in two ways: first is the additional traffic to send it to the mirror partner (or replica), second and most important is that synchronous requires that the primary not truly commit the transaction
until it has been committed to the secondary which means transactions take longer. For some products this can result in an unacceptable performance degradation.
Hopefully, MIM will support Availability groups.
David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

SQL Server 2014 Always on HA takes 8-14 seconds to fail over. Application side timeouts occur

Hi All,
I have a very similar post in the SQL Server 2014 forums too (https://social.technet.microsoft.com/Forums/sqlserver/en-US/adb5e338-907e-4405-aa62-d3ea93c7a98a/sql-server-2014-always-on-ha-takes-814-seconds-to-fail-over-application-side-timeouts-occur?forum=sqldisasterrecovery) -
advice in the end was to post a question here.
SQL Server Nodes, 2014 (12.0.2480.0)
1 Share witness (on separate subnet)
1 Cluster
1 Listener
I have been testing the response time to failovers – both manual (right-click, fail over in SSMS) and Automatic (shut down the primary host). The way I am testing response is to have a SSMS query running on my desktop, connected to the listener querying
a small table and hit execute.
The Query response time, from execute to receiving the result, has been between 8 and 14 seconds based on my testing. My previous experience (in a separate environment) showed around 2 second fail over times in a very similar configuration.
Availability DB is 200Mb and is not actively used. The nodes are synchronised.
SQL Server Hosts: Windows 2012, 2 cpu, 8gb RAM.
Questions:
1: It’s a big question but what should I expect for a ‘normal’ fail over time. Keep in mind this scenario is about as simple as it gets.
2: As it stands an 8 to 14 second ‘outage’ could cause some applications to time out. Or am I being un-reasonable? I am seeing the very simple query in SSMS to time out with this:
Msg 983, Level 14, State 1, Line 2
Unable to access availability database 'DATABASE' because the database replica is not in the PRIMARY or SECONDARY role. Connections to
an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
Cluster logs are long - this section accounts for 8 seconds of the 11 second outage I experienced. I can supply the full log if required. Also this log is just the 2 cluster nodes, I removed the witness share to make sure it was as simple as possible.
00001090.00002128::2015/02/25-03:05:08.255 INFO [GEM] Node 2: Deleting [1:65 , 1:71] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:10.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:11.888 INFO [GEM] Node 2: Deleting [1:72 , 1:73] (both included) as it has been ack'd by every node
00001090.00002698::2015/02/25-03:05:11.889 INFO [GUM] Node 2: Processing RequestLock 2:49
00001090.00002128::2015/02/25-03:05:11.890 INFO [GUM] Node 2: Processing GrantLock to 2 (sent by 1 gumid: 67)
00001090.00002698::2015/02/25-03:05:11.890 INFO [GUM] Node 2: executing request locally, gumId:68, my action: /dm/update, # of updates: 1
00001090.00002128::2015/02/25-03:05:12.890 INFO [GEM] Node 2: Deleting [1:74 , 1:74] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:15.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:16.988 INFO [GUM] Node 2: Processing RequestLock 1:28
Thanks in advance.
Keegan

Hi Keegan,
From these event log , what I can see is "Sending request Netname" wasted the time .
Could you please tell us the network configuration of that cluster nodes ?
If I recall correctly , it is recommended to only remain Tcp/IP protocol and disable NetBIOS over TCP/IP for "Private Network" , also do not configure DNS/Wins default gateway for "Private Network" :
https://support.microsoft.com/kb/258750?wa=wsignin1.0
After that please test again .
Best Regards,
Elton JI
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 Subscriber Support, contact [email protected] .

Cannot connect to SQL SERVER with Always on availability group listener name

Hi everyone,
I have setup always an availability group listener for sql server on port 1433, have opened the port in firewall , remote connections are enabled in the sql server, but still I am not able to connect to the sqlserver instance with the help
of the availability group listener name.
I get the following error.
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:
TCP Provider, error: 0 - The wait operation timed out.)"} System.Exception {System.Data.SqlClient.SqlException
Have gone through several blogs for the solution but none of them helped.
Please let me know if anyone has fixed the issue.
Regards,
Divya

Prior to making SS connection, can you establish the connection with a networking tool?
SS connectiviy trouble shooting:
http://technet.microsoft.com/en-us/library/ms378845.aspx
http://stackoverflow.com/questions/5919524/not-able-to-telnet-sql-port-1433-locally-or-remotely
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/227f431a-4274-4d95-b605-67541d78ef03/test-sql-connection-with-telnet?forum=sqldataaccess
Kalman Toth Database & OLAP Architect
Free T-SQL Scripts
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

SQL Server 2012 Always On ?

Hi all,
If the PB application uses a Sql Server 2012 database well configured for high availability ("Always On"), is there something to deal with in PowerBuilder or is it totally transparent on client side ?
In previous version there were a FailOverPartner database parameter to fill but it seems useless with Sql Server 12 am I right ?
Is there something about it in the Pb 12.6 documentation (we use 12.5.2) ?
Or is it just not supported in 12.5.2 ?
Thanks in advance

Things depend upon what your expectations are when using the failover features of SQL Server2012. You will not be able to have the somewhat seamless failover as you did using the FailOverPartner parameter (which is unfortunate) if you utilize failover clustering. You will need to detect the original connection fail and then reconnect the transaction object.
If you set up 2012 with a failover partner as in 2008R2 things should work the same (but we are talking about Microsoft however...)
Matt

SQL Server 2008 R2 Transaction Replication Tracer Tokens always pending

On a new transaction replication publiciation/subscription, the tracer tokens I generate always show pending for publisher to distributor and distributor to subscriber. The log reader agent is running and last action continues to update. The
Performance column in the repl monitor shows Excellent with a 00:00:03 latency. Distribution cleanup, agent history clean up, and replication agents checkup all show job succeeded and a resent last start time and their running times are usualy around
a second or show 00:00:00. On the subscriber, the "view synchronization status" is being updated with number of transactions and commands being delivered. I can confirm that updates are making it to the subscriber database. On
the surface, everything apears ok but I'm bothered by the tracker tokens not working.
this is SQL Server 2008 R2 10.50.1600.1 - OS is Windows Server 2008 R2 SP1.
-Larry
-Larry

In this case run sp_replcounters at the published db to see if the log reader delivers commands from the published db to the distribution db.
Yaniv Etrogi
site |
blog | linked in |
mail
Please click the Mark as Answer button if a post solves your problem! or
Vote As Helpful

Backup DB on Always-on Node 2 SQL Server

Always-on Node 2 SQL Server is configured with read only so my question is it possible to take backup of a Database on node 1 & node 2 of both the always-on configured SQL servers at the same time

I ran a super quick repro, these are the type of messages you'll get (depending on timing):
-- This is the replica not getting a lock
Msg 3013, Level 16, State 1, Line 3
BACKUP LOG is terminating abnormally.
Msg 35250, Level 16, State 11, Line 3
The connection to the primary replica is not active. The command cannot be processed.
-- This is the log backup on a primary or another secondary already took a log backup that covered the LSNs on the secondary asking for the log backup. Thus there is already a backup of it and the VLFs may have already wrapped. This is both a timing issue
and an issue of secondarys potentially being out of sync.
BACKUP LOG is terminating abnormally.
Msg 35295, Level 16, State 1, Line 3
Log backup for database "Another1" on a secondary replica failed because the last backup LSN (0x0000004b:00000030:0001) from the primary database is greater than the current local redo LSN (0x0000004a:00000180:0001). No log records need to
be backed up at this time. Retry the log-backup operation later.
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

Always on Availability on 2 different SQL Server clusters

SQL Server 2012 EE on WIndows 2008 R2.
Is it possible to have Always on Availability on 2 different SQL Server clusters ?. Could 2 SQL Server clusters be on 1 Windows server failover cluster (WSFC) ?. We have a Prod domain and DR01 domain with 3 nodes SQL Server clusters each. How can we setup
Always On Availability groups on these clusters to make replica of Production databases on the Prod to DR01 domain cluster ?. What do we need to do to get this working ?...................Thanks.

DCarlos unfortunately the requirement for AlwaysOn Availability Groups are a Single Domain, A single WSFC. The WSFC in multiple sites is supported with either a stretched VLan or multiple Subnets.
If your environment does require you to have different Domains for Prod and DR then you would have to look at potentially other ways of achieving your data replicated across from prod to DR.
You could look at using Database Mirroring (Yes I know this has been marked for deprecation) to achieve your data transfer. Or depending on your RPO and RTO requirements Logshipping may be an option.
Thanks
Warwick Rudd (MCM - SQL 2008 | MCT)
(SQL Masters Consulting |
My SQL Server Blog | Twitter)

Good device to put Instance root directory on a SQL Server 2012 Always On Failover Cluster ?

Hello, I'm currently testing SQL Server 2012 AlwaysOn Failover Cluster.
I wonder if I installed it correctly : I installed the software on both server with the instance root directory set to a directory on a cluster shared module.
The reason why I'm not sure is because, when I wanted to upgrade from SP1 to SP2, I wanted to do it first on the passive node, but it failed for most of the components it had to upgrade. So I first upgraded the active node then failover and upgraded the
newly active node.
I installed SQL Server this way because our system admins don't like us to install in on C:\ for their own reasons (maybe backup, or something ...)
I'm pretty sure there is something wrong. What's your point ?
Thanks in advance.

>I wonder if I installed it correctly : I installed the software on both server with the instance root directory set to a directory on a cluster shared module.
Nope.
SQL Server 2012 and earlier don't support data files on CSV volumes (SQL 2014 does).
And for any version of SQL Server the SQL Server instance directory should not be on a clustered disk. The Installation is local to each node, so should be on a non-clustered disk. It may be supported to put the instances in different locations
on the same clustered disk, but I wouldn't recommend it.
Installing the SQL Binaries on C:\ is fine. If you have another local volume you can also install them there.
David
David http://blogs.msdn.com/b/dbrowne/

SQL Server Always On

Similar Messages

Maybe you are looking for