October 23, 2014 at 9:34 am
I have 2 servers in the array (SRV and SRV-001-002) with SQL Server 2012 SP2 and Windows Server 2012 R2, one primary and one secondary, using AlwaysOnAG. I currently have an availability group, called AG_MTZ, synchronous and automatic failover, with 45 databases in that group.
In a cluster configured for FileShareWtiness Quorum therefore currently have 3 votes and my 2 servers and 1 Quorum.
Everything working, until this moment.
I set up a test environment for a new project where we have 15 filais scattered in different cities and have a link in all, these branches have the SQL Server database servers, with only one database. I am wanting to pick up these banks and bring matrix and make this server a secondary affiliate, and these banks will be used only when the link goes outside.
Let the scenario:
1 - I created a new availability group, AG_FILIAL_02 where the primary server was the SRV-001 and the SRV 002 and SRV-BRANCH-side, respectively, synchronous and manual failover.
2 - I put the vote of the branch server (SRV-BRANCH) = 0
3 - Link to the crashed drive, we have no prediction of return, there will start to get interesting scenario.
Until this moment, the primary server still remains the SRV-001, and the database is being replicated to the secondary in this seat, if the SRV-002, without getting replicate the SRV-BRANCH.
With that, I need to perform a forced failover for this availability group and become the basis of dipinivel data for application, ie, as the link is out, the only way I found to make the database available through Data was forced failover.
I did the procedure of forced failover successfully and have suspended replication, the application worked, and even when everything was going well. When the link back, as did a forced failover, my branch server becomes primary and the matrix become secondary, but in the middle of this procedure, my AG_MTZ goes offline and the online is AG_FILIAL_02 and synchronizes all data.
I'm not understanding why my AG_MTZ is getting offline, in my entedimento this should not occur because an availability group could not influence the other.
Should this not occur, and independent work groups.
October 23, 2014 at 9:38 am
i'd love to help more but it's not entriely clear what your issue is
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 26, 2014 at 10:28 am
Hello!
I'll try to summarize, when performed a forced failover secondary server in my AG in which other database is getting offline.
October 27, 2014 at 10:50 am
Are your database files hosted on Cluster Shared Volumes (CSV) or traditional cluster disks.
If they are on CSVs you should see no outage at failover. If they are on traditional cluster disks you will see an outage.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply