August 8, 2013 at 12:26 pm
Ok, I am about at my limit on this. I am trying to set up SQL 2012 Always On. I have tried setting it up with Two Instances on the same 2 node cluster. Did not work.
Now I have two separate clusters. Cluster1 with the database I want to replicate to the other cluster. Cluster2 with no database yet.
Getting an error that says The specified instance of SQL Server is hosted by a system that is not a Windows Server Failover Cluster node. I get this message when I try to add the Cluster2 as a replica.
What am I doing wrong?
Thank you
July 11, 2014 at 3:33 pm
[font="Verdana"]I too, am having the same problem.
Been on it for 2 weeks. Tremendous waste of time. Both clusters are up. Failed over and back multiple times. Shared storage works. But this... nothing![/font]
July 14, 2014 at 8:47 am
you need only one windows cluster.
July 14, 2014 at 8:55 am
I suspect you tried installing it as a cluster and shared storage. AlwaysOn does not work like traditional clusters. Here is a link on a how to for AlwaysOn. In short You will need to configure quorum and one cluster in failover cluster manager. You will install single instances of SQL with no shared storage. Make your drives are identical on each server (server A and server B).
MCSE SQL Server 2012\2014\2016
July 15, 2014 at 7:48 am
khott (8/8/2013)
Ok, I am about at my limit on this. I am trying to set up SQL 2012 Always On. I have tried setting it up with Two Instances on the same 2 node cluster. Did not work.Now I have two separate clusters. Cluster1 with the database I want to replicate to the other cluster. Cluster2 with no database yet.
Getting an error that says The specified instance of SQL Server is hosted by a system that is not a Windows Server Failover Cluster node. I get this message when I try to add the Cluster2 as a replica.
What am I doing wrong?
Thank you
All nodes must be part of the same Windows Server Failover Cluster. You can either use standalone instances to join to the availability group or you can introduce Failover Cluster Instances. However by doing this you limit the functionality inside the AO group and also reintroduce the storage single point of failure.
How did you configure the system previously and what errors did you get?
Have a read through these, they may help
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply