March 5, 2025 at 3:25 pm
Hi All,
We have setup a 3 node SQL Server 2019 (CU30) multi subnet cluster with 2 nodes on production site and 1 node in disaster recovery (DR) site. The DR site does not have any AD/Domain and it is still under the same AD/Domain as production (Just different subnet but same AD - One in Ohio and one in chicago IL). All the ports are open between the 2 sites but after adding the DR node to the cluster, DBs are not replicating. I have added an IP address for the DR site to the Listener but it is not working. Could this be because the DR site must also have a AD/Domain ?. The Listener takes the second IP address (10.10.40.9) but the databases do not replicate. They show up in "Availability Databases" of the ALways On group but not replicating at all using the Automatic seeding. Here are some of the errors I got. Thanks for any help. The big question is whether the DR node must have it's own AD/Domain or not.
Kevin Williams
Message
A connection timeout has occurred while attempting to establish a connection to availability replica 'PRODSERVER\INST1' with id [83ECE30D-9ACB-47AA-82F9-F1AE77B3F55B]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance.
Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [83ECE30D-9ACB-47AA-82F9-F1AE77B3F55B]->[03C5AE4F-84E2-485D-8F84-7699E4B8CC7B], database [PRODDB1], remote endpoint [TCP://CHICAGO.firestone.com:5023], source operation [0FE86A20-E6D7-4B9D-8BC5-83E4A10ED461]: Seeding encountered a transient failure, state '108', maximum retries exceeded'
Message
Automatic seeding of availability database 'PRODDB1' in availability group 'MIDNORTH_AG1' failed with a transient error. The operation will be retried.
No matching network interface found for resource 'MIDNORTH_AG1_10.10.40.9' IP address '10.10.40.9' (return code was '5035'). If your cluster nodes span different subnets, this may be normal.
March 5, 2025 at 3:59 pm
I have no idea, but I'd lean towards networking. I'd be sure that firewalls on the machine, as well as routers are open here.
A few searches show things like basic networking
March 5, 2025 at 4:13 pm
Thanks Steve. Is that mean we don't need to have a AD on the DR site and just need 2 IP addresses (2 NICs - One for the cluster and the other for the listener) for the cluster ?
March 5, 2025 at 4:18 pm
Maybe. I'm definitely not the AG expert or cluster guy here. You might send Perry Whittle a DM and ask him to respond here. He wrote the Stairway on clustering/AGs here.
Not sure you need two NICs, but two IPs are probably what is needed. I think these need to be unique.
March 5, 2025 at 4:42 pm
But the 2 IP address we need has no bindings on the DR site. Anotherwords, when I add the second IP on the Listener for the DR subnet, there is no place for it to create the Listener name/DNS. The one in the production site already exist and there is another one needed on the DR site which makes me think that we need a separate AD/Domain site on the DR network,
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply