New answers tagged

0

If Production site SQL DB Servers are down, will Windows Server Failover Cluster be Online or Offline ? If you have a setup that relies on a quorum disc, this must be available - ergo offline. This is a non recommended setup. Whoever set it up did not bother to validate it makes sense. Geographically dispersed clusters are a proven technology (start ...


0

There is no reason to move the cluster core resources. They are NOT part of the availability group and function entirely on their own. There is no need to even have these on the same server as any of your AG resources. The core cluster group provides the administrative point for the cluster which is completely independent from any other resources on the ...


2

The terms are being confused sadly which is causing an issue. There's WCFS (Windows Clustering Foundation Services) which FCI (Failover Cluster Instance) runs on and requires shared disks. An AlwaysOn AG can also run on WCFS but it uses non shared storage and provides live read only replicas. In other words A FCI is a shared storage architecture and you ...


3

Nothing particular to worry about, but you will incur downtime as the SP runs its stuff in "script mode" during which users cannot connect. It might go without saying, but I'd ensure you have a valid (i.e. tested) backup of the databases (including the system databases) on the affected system prior to doing any patching, whether on a single-node cluster, a ...


2

Active/Active refers, typically, to the idea of having multiple copies of a database available concurrently. However, in SQL Server, there is no way to accomplish that for read-write databases, other than the somewhat edge case of sharding data across mutliple instances. In SQL Server, Active/Active is normally used to denote a multi-node Windows Server ...


2

Given CLUSTER_1, with NODE_1 and NODE_2, and virtual network VNN_1 with IP_1, these will work: VNN_1\INSTANCE IP_1\INSTANCE These will not work: CLUSTER_1\INSTANCE NODE_1\INSTANCE NODE_2\INSTANCE If you are unable to connect using VNN_1\INSTANCE then, can you ping it, and what does it resolve to? Is it configured for a single IP (i.e. not ...


3

Firstly, having 4 separate 2 node clusters with one FCI deployment in each seems to me to be a little extreme. The second model you describe does not really make sense to me. Instead of either deployment I would suggest running 2 Clusters of 4 nodes (you would need a witness for each) and consider one node in each as a dedicated failover node (i.e. that you ...


0

Same kind of message appeared in our environment as well. What I understand is, as the DB was in AAG, and when the node (secondary AAG group) goes under restart, the DB start-up will be taken care of by AlwaysOn instead of the regular SQL Server 3-phase process! If the message appears without any secondary node restart, we may have to consider ...


1

Looks like the JDBC 11g NAT+RAC issue. JDBC Connections Using SCAN Fail With ORA-12516/ORA-12520 (Doc ID 1555793.1) JDBC thin 11g connections using Single Client Access Name (SCAN) fail with errors: ORA-12520: TNS:listener could not find available handler for requested type of server ORA-12516: TNS : listener could not find instance ...


0

The concepts of quorum, and owners are separate topics. Just because a member of the WSFC doesn't get a vote in quorum does not mean it can't own a resource. Additionally, SQL Server doesn't really play a role at all--the same concepts apply regardless of what type of clustered resource you're dealing with. Quorum: The quorum is the number of votes ...


0

From a terminology perspective, there is a Windows Server Failover Cluster (WSFC), and a SQL Server Failover Cluster Instances (FCI). There's also an Availability Group (AG). AGs and FCIs are built on top of a WSFC. AGs and FCIs can be combined or separate. I try to avoid saying "Cluster" and use these acronyms to avoid ambiguity. From your description, it ...



Top 50 recent answers are included