New answers tagged

1

Removing SQL Server from failover cluster - you have to run the setup.exe and in maintenance you have to select remove node. Then removing the node from windows cluster, I would suggest you use PowerShell Remove-ClusterNode –Name node4 #change your node name here The Remove-ClusterNode cmdlet removes a node from a failover cluster. After the node is ...


0

I have just evicted in the past, it will stop the cluster services for you.


1

Yes they are correct it will increase the execution time. As the comments state though there is no measurable way to determine this unless you have a matched test/stage environment and try it both ways (which would also be a best guess since you cannot know latency and bandwidth of your network and the load on the nodes). I see this as the company asking ...


0

You may be missing an important part of the puzzle or at least I didn't see it anywhere in your post... ApplicationIntent=readonly is one half of the equation... You also need to pass the parameter MultiSubnetFailover=True. For instance, in the Additional Connection Parameters tab, you want to enter the following... ...


2

As I understand, you are performing a full backup and log backups on server 1, then you perform a fail over to server 2. When you start performing the log backups on server 2 it follows the log chain. So to answer your question: No it is not needed to perform a full backup job every time your availability group fails over. I suggest that you test this in ...


2

Does the Windows Failover Cluster for a multi-subnet SQL Server Availability Group require a static IP entry for each subnet? The CNO will require an IP address for every subnet it could reside in. I am running SQL Server 2012 on Windows Server 2012 Hyper V VMs in 2 separate subnets in the same domain. I understand that I will need an IP from ...


0

There is no easy answer for this, you will have to go through the entire process from scratch and preferably do it several times so you know exactly what to expect, then focus on monitoring it. This is well documented though and you should start with a search engine query to get familiar with it. Edwin is a resident HA expert in the SQL Server community ...


0

There are 2 High Availability types: Advanced HA on Enterprise edition Standard or Basic HA on Standard edition (or BI edition) Capabilities, prerequisites and restrictions You can look for SQL Server 2014 Capabilities at the top of page 5: SQL Server 2014 Licensing Guide. If you look at the 2nd row from the bottom of the Compare edition table (SQL ...


0

The Availability Group Listener (AGL) is part of the AG's Windows Server Failover Cluster (WSFC) Resource. It is a Virtual Network Name with n number of IP addresses. Being in a cluster resource it will only run on a single node of the WSFC and that node will be the primary node of the AG. It is not a thread within SQL Server. The WSFC handles the failover ...


3

What to do when your AlwaysOn cluster loses quorum? I have been into this situation especially with Multi-subnet clustering spanning different countries (NY-LD-HK). How to avoid Quorum Loss in a multi-subnet cluster ? Change the cluster default setting to a more relaxed monitoring state especially Cluster Heartbeat settings using CrossSubnetDelay, or ...


6

AGs are based on Windows Clustering. The WSFC procedures for quorum loss apply. WSFC Disaster Recovery through Forced Quorum Force a WSFC Cluster to Start Without a Quorum Once the WSFC is running, you can then force AG, if needed. Perform a Forced Manual Failover of an Availability Group: After forcing quorum on the WSFC cluster (forced quorum), ...


2

The way I try to explain it to people is that the listener leverages the Windows Failover Cluster for its functionality; you cannot create the listener without the cluster already existing as the cluster itself creates the listener. As such, it is Active Directory (AD) that hosts it and the nodes that use the cluster can use any services that cluster has, in ...


3

After poking around in SSMS for a while I noticed that on the secondary replica there was a pause icon next to the Availability Databases. The primary had shown both were "green", but there was an option on the secondary to Resume Data Movement. I resumed the first database, and immediately the In Recovery status message was removed. A minute later it ...



Top 50 recent answers are included