Sql-server – Accessing a network share via a SQL Server 2012 Availability Group

sql serversql-server-2012

If you have a SQL Server Cluster called CLS, with machines CLS1 and CLS2, accessing:

\\CLS\network\path

is equivalent to accessing either

\\CLS1\network\path

\\CLS2\network\path

depending on whether CLS1 or CLS2 is the currently active instance.

The same behavior isn't occurring on a SQL Server 2012 Availability Group I've set up to try out AGs. I have three machines called PRI, SEC1 and SEC2 in an availability group called AG. I can access the databases via AG, and can remote desktop AG, but cannot access network shared via AG.

Are you supposed to be able to, by default, access networks shares via the AG?
If not, can this behavior be enabled?

Edit: I am primarily interested in the administrative shares (c$, d$ etc.)

Best Answer

CLS is not an alias for either CLS1 or CLS2. CLS is a cluster, not a real machine. You cannot access \\CLS\c$ simply because no such thing exists. There is only \\CLS1\C$ and \\CLS2\C$ and you can access either of them. You should figure out which one is the one you're interested and access that.

Related Solutions

Sql-server – SQL Server cluster not available after failure of the “main” server

Without looking at the cluster logs or any other form of error reporting, all I can do is guess here.

But my initial thoughts are that you may have hit the failover threshold. By default, this is going to be set to a maximum of n - 1 failures (where n is the number of nodes) over a period of 6 hours. Yes, that's a long time, and especially in a 2-node cluster that isn't very many failures (only equates to one failure). This threshold is set to prevent the Ping-Pong effect of cluster groups.

In production, this is probably a good thing. But in testing/development/non-prod it is pretty common to run into this initially perplexing problem, as you may be trying to consecutively failover. It is worth noting that these parameters are 100% configurable. All you need to do is go into the properties of the cluster group, and in the "failover" tab you will have the option to change these two parameters (Maximum failures in the specified period and Period (hours). Here is what this looks like in the Failover Cluster Manager:

enter image description here

Note: in my screenshot, the threshold is set to 2 because I have a 3-node cluster.

Likewise, this can be seen with PowerShell (accessing the FailoverClusters module).

# you may need to set your cluster group name to whatever it is named
# in your environment
#
Get-ClusterGroup -Name "SQL Server (MSSQLSERVER)" | 
    Select-Object Name, FailoverThreshold, FailoverPeriod

Sql-server – Primary server ‘XYZ’ can not write to shared drive during availability group configuration

PORT 5022 was not added to secondary node's firewall

After adding rule, it worked like charm

This is how I found the solution

Open command prompt

     Telnet NODE2 5022

This failed

Best Answer

Related Solutions

Sql-server – SQL Server cluster not available after failure of the “main” server

Sql-server – Primary server ‘XYZ’ can not write to shared drive during availability group configuration

Related Question