Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

SQL cluster and AlwaysOn availability group

$
0
0

Hi all,

I have an interesting scenario.  I run a 2 node cluster (Windows 2012) with SQL 2012 SP1, which uses a SAN.  I need to create an availability group to have a set of these databases online on a standalone SQL server.  I have actually done this exact task in the past, but am struggling with an error message.  According to the Microsoft Technical group, this is 1 scenario which AlwaysOn may be used for (http://msdn.microsoft.com/en-us/library/jj215886.aspx).

So, I add a node to my 2 node cluster.  I then go into SSMS to configure the availability replica.  I get through the initial validation.  On the last step, I get an error.

-------------------

TITLE: Microsoft SQL Server Management Studio
------------------------------

Attempting to add availability replicas to the availability group resulted in an error. (Microsoft.SqlServer.Management.HadrTasks)

------------------------------
ADDITIONAL INFORMATION:

Create failed for Availability Replica 'USTAWVSHAGEMAN1\SQLCAD'.  (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.0.3000.0+((SQL11_PCU_Main).121019-1325+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+AvailabilityReplica&LinkId=20476

------------------------------

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

Failed to create, join or add replica to availability group 'ag8', because node 'standalone' is a possible owner for both replica 'cluster' and 'standalone\SQL'. If one replica is failover cluster instance, remove the overlapped node from its possible owners and try again. (Microsoft SQL Server, Error: 19405)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.3000&EvtSrc=MSSQLServer&EvtID=19405&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

I can't seem to get by this error.  My disk configuration matches,  my user accounts to run SQL server identical on all machines involved.  I read somewhere that the standalone machine needed to be a named instance and not the default, so I added a named instance as well.  Everything brings me back to this error.

Failed to create, join or add replica to availability group 'ag8', because node 'standalone' is a possible owner for both replica 'cluster' and 'standalone\SQL'. If one replica is failover cluster instance, remove the overlapped node from its possible owners and try again. (Microsoft SQL Server, Error: 19405)

If anybody could please help, I would greatly appreciate it.


Viewing all articles
Browse latest Browse all 4689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>