Questions tagged [availability-groups]

Availability Groups are a new feature of SQL Server 2012 that provide continuous data synchronization, automatic failover and secondary read access for one or many SQL Server databases.

Availability Groups are different from Database Mirroring in several ways. The major differences are mostly centered around the ability to read the data on multiple other instances and the capabilities around automatic failover.

Official Info: An availability group supports a failover environment for a discrete set of user databases, known as availability databases, that fail over together. An availability group supports a set of primary databases and one to four sets of corresponding secondary databases. Source: http://msdn.microsoft.com/en-us/library/ff877884.aspx

Provides an integrated set of options including automatic and manual failover of a group of databases, support for up to four secondaries including two synchronous secondaries and seamless application failover using availability group listener. Source: http://www.microsoft.com/sqlserver/en/us/solutions-technologies/mission-critical-operations/SQL-Server-2012-high-availability.aspx

Resource: For more information on the capabilities and latest improvements to SQL Server Availability Groups you can visit the AlwaysOn Team Blog

Note that Availability Groups are part of and sometimes referred to as "AlwaysOn" - but "AlwaysOn" is a marketing term that refers to all of Microsoft's high availability and disaster recovery features over multiple server technologies.

1583 questions
2
votes
0 answers

How to use a different vlan for mirroring in an availability group

I want to setup the following with SQL Server 2014 Enterprise and Windows Server 2012 R2. I have two nodes and a fileshare for witness. Both are virtual machines in the same vsphere cluster. To minize the network traffic in our network, the network…
Philipp
  • 21
  • 2
2
votes
1 answer

SQL Always on Availability LSN Query

Please can somebody explain how the following works: Scenario: Two nodes in always on availability group configuration (all databases). If I have a backup job on node 1 to backup Full and Log backups to a network share, then failover to node 2 and…
Hpk
  • 304
  • 2
  • 12
1
vote
0 answers

SQL AlwaysOn Failover Due to Missed Heartbeats

I have setup SQL AlwaysOn between primary and DR data centers. Here is the setup: Primary data center: Server1 (Primary), Server2 (Sync Commit Secondary), Server3 (ASync Commit Secondary) DR data center Server4 (ASync Commit Secondary) Data…
Raj
  • 11
  • 1
  • 3
1
vote
1 answer

Always on Availability Groups - Disaster Recovery + High Availability in SQL Server 2019

I'm reading some articles on how to create an Always on Availability Groups - Disaster Recovery (HA + DR) environment. In many blogs it shows that to create this environment I will need three servers, as shown in the figure below. Where would SQLP3…
Carlos D
  • 21
  • 1
  • 3
1
vote
1 answer

Using CName to point to the Availability Group listener

I have SQL Server 2008 named "OldSQLServer". Its data is accessed by hundred of SQL Servers via linked server. I am moving the "OldSQLServer" to AG on SQL Server 2019, windows 2019. And I want to keep connecting to it by “OldSQLServer” name. So I…
1
vote
1 answer

Can I have a sql 2017 read-scale AG on different Windows server OSs; i.e. Windows server 2016/2019?

I hope the title is self-explanatory. We want to add another node to our sql server 2017 read-scale AG. I would like to go with Windows server version 2019, and cannot find any information that says I cannot. Any concerns, comments or experience on…
JohnH
  • 433
  • 4
  • 10
1
vote
0 answers

cent os 7 alwayson primary is in resolving state and not going to secondary

I have configured AlwaysOn in external mode between two CentOS 7 VMs. When manual failover happens, primary goes to resolving state. It never turns to secondary and secondary is always in secondary state -- All nodes (linux01 and linux02) sudo pcs…
Srini
  • 11
  • 1
1
vote
1 answer

Always On - keep secondary database readable when connection to primary node failed

By default, secondary replica brings databases into offline state when connection to the primary replica fails. We are using SQL 2016 SP1. The goal is to reduce interruption for users on secondary async replica when primary replica goes offline for…
Alex Bochkov
  • 165
  • 10
1
vote
1 answer

AlwaysOn read only replica slower then prime

I’m running into an issue. My readOnly replica (on Node B) takes twice as long to execute a query as on my primary (Node A). But when I fail over to Node B (which becomes my primary) it runs fine, but then it runs slow on the new replica so I don't…
Tomasz
  • 186
  • 2
  • 13
1
vote
0 answers

availability-groups

I was in the process of configuring aag on two new 2014 Enterprise servers. The configuration going good and the cluster, the nodes, the listener, the fileshare witness are online. Everything seems normal and I can failover from one node to another.…
Mahari
  • 19
  • 3
1
vote
1 answer

Physical Move of Secondary Replica to a new Location

We plan on moving a secondary replica of an SQL2014 AlwaysOn group to another physical location although it will have the same IP address after the move. The shutdown may be between 24 and 48 hours. Is there anything that would need to be done on…
bmiguelh
  • 51
  • 1
  • 2
1
vote
1 answer

Do you need SQL Server AAG when using SQL Server FCI/RAID10?

If I have a 2-Node AlwaysOn Automatic Failover Cluster Instance with a shared disk and RAID-5 or RAID-10 to account for a SAN failure with the same setup in a second datacenter with data propagation via SAN Replication, is there a way to benefit…
PASQLDBA
  • 53
  • 1
  • 6
1
vote
1 answer

How to enable/disable SQL agent jobs during fail over (AlwaysOn)

Note: this is not duplicate question. I have setup AlwaysOn. I have created SQL agent jobs manually on both the nodes. right now all the active jobs are running if node is PRIMARY. Challenge My DBA will disable few SQL agent jobs manually in only…
kudlatiger
  • 269
  • 2
  • 4
  • 21
0
votes
0 answers

Stored procedure execution issue on always on 3rd node

we have an alwayson three node setup. our client is executing a stored procedure on 3rd node. The stored procedure runs for 30 minutes and it is terminated and giving below error message without any results. Kindly assist on this Msg 3949, Level 16,…
0
votes
1 answer

Questions regarding removing a secondary node from an availability group

I have a 2 node AG in a non-prod environment and we are looking to shut down the secondary node for cost savings, leaving this with just the primary node. I have some questions based on this process, and my research hasn't answered all of them. …
DBA Greg14
  • 257
  • 2
  • 16
1
2