October 4, 2019 at 2:31 pm
Upgrading an old SQL Server 2008 to 2017 and was using Database Mirroring to transition over the databases (endpoints using Windows Authentication). Both instances are running the SQL Server services as the same domain user (sysadmin role / mapped to master). But for some reason my database mirroring keeps going between the "Synchronizing" and "Disconnected" states. I've attempted to recreate the endpoints, restart the mirroring, grab new full/log backs to startover, but each time I have the same result.
I'm able to get database mirroring working from the SQL Server 2008 instance to a 2012 instance, but cannot get the 2012 to 2017 database mirroring working either when I tried a test database.
When I look at the Event Log I see timeouts after the default 10 seconds, but increasing this number doesn't appear to help. I've also verified that the port(s) for the endpoint are opened in the windows firewall. What are items could I check to help diagnose the issue?
October 5, 2019 at 3:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
October 7, 2019 at 10:42 am
Are both sides running the same edition (i.e. Standard/Enterprise/etc.)? If not, they do need to be.
October 7, 2019 at 1:54 pm
Correct - All three instances are running Standard.
October 7, 2019 at 3:45 pm
Note - Have recreated endpoints and attempted a different port (5022) without success. Added port to inbound/outbound firewall rules as well.
October 14, 2019 at 7:10 pm
I ended up switching over to log shipping, but may have located the culprit. It appears that one of the cumulative updates (CU3) may address this particular issue.
I hope to test/confirm this week after applying the latest CU to the server. Hopefully, this helps others that encounter this in the future.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply