sql server 2012 availability group not synchronizing after network outage

  • Hi. I've been working with sql server for some time, but couldn't find any way to fix this problem without rebooting the production and secondary sql servers, which is not very good for uptime :-).

    I hope someone out there may be able to offer some suggestions, which would be really appreciated.

    I'm running a primary and secondary availability group on sql 2012 enterprise edition on windows server 2012, and it runs fine except when a network outage occurs.

    Then the handshaking keeps failing, and the secondary databases all show not synchronizing.

    The primary DBs all show synchronized.

    I tried following several different troubleshooting guides for always on, but nothing I tried fixed the issue.

    The only way to get them in sync is to reboot both primary and secondary.

    Just rebooting the secondary didn't fix it.

    The secondary server error log showed AlwaysOn Availability Groups connection with primary DB established, then DB mirroring login succeeded, then error 35250, the connection to the primary replica is not active, then connection timeout.

    Was wondering if upgrading to windows server 2012r2 could help this, or does anyone have any suggestions on commands to try in future, to eliminate all these prod reboots?

    I increased query connection timeouts to 60, but that didn't help.

  • 1) Have you patched up SQL Server (and Windows)?? There were quite a few patched bugs with AGs.

    2) When you set things up, did you follow the LARGE amount of gotta-do's for installation, config, testing, etc? Always On has a LOT of caveats, provisos, limitations, gotchas, etc!!!!

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • Thanks very much for the reply.

    I wasn't the one to set it up, but will check if there are any windows or sql server patches that need to be installed.

  • The sql server is SP1.

    I'm going to install SP2 in dev, and then the latest, CU7, and then put it in prod after everyone tests for some time.

    Thanks again, Kevin.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply