Post reply

Has anyone had problems with the mirroring not re-establishing itself after partner goes down for a while?

  • July 20, 2016 at 1:50 pm

    #315428

    We had some weekend maintenance recently where the mirror partner's connection was lost (due to a firewall issue). During that time, several hundred gigs of data was queued up on the primary site. When the connection was re-established, the Mirroring service was unable to re-establish itself. Are there any official thresholds on this? I thought we were able to pause the mirror and have it resume, if necessary. It seems like it just got "too far behind" and didn't even try to deliver the mess in its backlog.

  • July 21, 2016 at 6:51 am

    #1891300

    On thing you can try is to stop and restart the mirroring endpoint. This sometimes wakes up the mirroring and it will start trying to catch up - To list all endpoints in a SQL Server instance, you can query sys.endpoints catalog view that contains one row for each endpoint:

    select * from sys.endpoints

    --

    To stop an endpoint:

    ALTER ENDPOINT endpoint_name STATE = STOPPED

    --

    To start an endpoint:

    ALTER ENDPOINT endpoint_name STATE = STARTED

  • July 21, 2016 at 8:45 am

    #1891347

    Yeah, I tried restarted the endpoints. Didn't help.

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

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