Hello everyone,We had a big issue today during maintenance work in our SQL environment. I hope you can help us out what we are doing wrong in our SQL environment.So our environment:- 2x SQL Server 2014 Enterprise on Windows Server 2012 R2 (SRV1 and SRV2)-- Both Hyper-V VMs on different Hosts-- Both configured to an Windows Failover Cluster and AlwaysOn Availability Group (AG1)-- AG Listener: AG1_lis-- No shared storage (each Hyper-V Host has its own local storage)-- Asynchronous Mode-- SRV1 is primary, SRV2 is secondary SQL nodeWhat happened?- Shutting down Windows on SRV2 due hardware maintenance- Cluster goes offline, AG1 goes offline-- Error message: "Stopped listening on virtual network name 'AG1_lis'."-- Error message: "The availability group database "DatabaseXY" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization."Results?- AG1_lis wasn't available for our applications and they stopped working properly because database connection was lost!I think, I HOPE, this is not the normale behaviour when one node is shutting down (especially the secondary node!)I already searched a little bit and found two things which could be the problem but I am not sure:1. We haven't set any quorum. I had read a lot of documentation about AlwaysOn and my conclusion was that a quorum is not necessary in our environment. Am I totally wrong at that point ? Do we need a quorum in a 2-node cluster and without shared storage?[b]EDIT: This might be the problem. I will set up a Node and File Share Majority Quorum to solve this problem... [/b]2. I found this topic in this forum: http://www.sqlservercentral.com/Forums/Topic1465938-2799-1.aspxI see this in our environment. Our "Current Host Server" in Windows Failover Cluster Manager is SRV2. In SQL Server, our Primary Node of the AG1 is SRV1. Is this the problem? But why these differ? Is it normal?I hope you can help me with these two questions and my problem...Best regards,babo
↧