January 20, 2017 at 2:29 am
Hi All,
I have 2 SQL Server 2016 EE one is in my local data center and another one is on the cloud. users accessing local data center. now I want to configure always on between local server and cloud server for DR and HA purpose. both servers are not in same domain. so kindly suggest how to configure always on.
-- Ragu Thangavel<
January 22, 2017 at 3:03 am
Windows 2016 now provides domainless and multi domain clustering so you should look toward this first and then build your AG on top of that
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 22, 2017 at 2:30 pm
Windows 2016 now provides domainless and multi domain clustering so you should look toward this first and then build your AG on top of that
Wow. I had not heard of this up until now. I know that SQL Server 2016 had a lot of new features to promote, but I am a little surprised this has not been marketed more. Finally an easy to failover/manage alternative to db mirroring in scenarios where domain membership was not a valid option!
Has anyone tried this out yet? Is management/failover of the AG similar to a traditional AG in SSMS or T-SQL?
Joie Andrew
"Since 1982"
January 22, 2017 at 10:11 pm
This was removed by the editor as SPAM
January 22, 2017 at 11:21 pm
Joie Andrew
"Since 1982"
January 22, 2017 at 11:57 pm
Yes I have been exploring the new cluster features in Windows 2016. I am planning an article to show a nondomain\workgroup cluster with Alwayson availability groups
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 14, 2019 at 7:47 am
I have done this on my Laptop & blogged the same. Below is the link for the same.
https://www.chiranjeevivamsydba.com/search/label/Multi%20Domain%20Always%20on
October 5, 2024 at 3:47 pm
Hello,
I am trying this configuration with four servers.
Three are in the same AD, and one is in a different AD.
I followed all the instructions (install Failover Clustering feature on all nodes, create same local admin user on all nodes, configure all DNS suffixes on all the nodes, uncheck "Register the connection's addresses in DNS). I also created DNS records for the nodes in the two domains.
I can ping the DNS names of node 4 from nodes 1, 2, and 3. But every time I try to create the cluster, I get an error stating that node 4 cannot be contacted. I updated local host files on all the servers but have the same issue.
How did you guys make it work? I don't know what I am missing.
Thanks for the help.
October 5, 2024 at 3:53 pm
I am trying to set up this, but I need help.
I have four servers (Node 1, 2, and 3 are in the same domain, and Node 4 is in a different domain).
I followed all the instructions: installed the Failover Clustering feature on all nodes, created an admin user on all nodes (same username and password), added the DNS suffixes of the two domains on all the nodes, uncheck the "Register this connection's addresses in DNS. I can ping Node 4 from Node 1, 2, and 3. But when I ran the new-cluster command, it failed with the error "Node 4 cannot be contacted".
October 7, 2024 at 6:58 am
What networking restrictions are there in place, there are a number of ports required for the nodes to fully communicate, are there any firewall devices
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply