Restarting mirrored databases after patching

  • We are looking for a procedure to restart our database server after we have done patching.

    Our situation

    Two Microsoft SQL 2008 R2 server installed on VMARE virtuel machines with

    the Windows Server 2008 R2 OS

    The SQL is mirrored without a witness server

    HA is performed using VMotion

    We had some issues when restarting the SQL Servers with some of the databases

    The mirror was suspended

    We could not get the mirror working because an entry in the transactionlog on the passive database was missing

    We had to stop the mirror , restore the database and configure the mirror again

    How can stop this from happening

  • domstrad (10/24/2014)


    The SQL is mirrored without a witness server

    HA is performed using VMotion

    If you're mirroring the database then the HA is at the sql server level, introducing VMotion will not help.

    Essentially there shouldnt be any disconnection issue, but if however during transit from one host to another the network is breaking down you may quickly hit the mirror session timeout. You should'nt lose transactions it may just be that the transaction is still in the principal send queue.

    First thing i would do is stop VMotioning the mirror servers.

    domstrad (10/24/2014)


    We had to stop the mirror , restore the database and configure the mirror again

    How can stop this from happening

    Did you try resuming the mirror session?

    When patching a mirror node you patch the passive node first, reboot if necessary and then manually failover to the mirror as new principal. Patch the new passive node and reboot, then fail back if required.

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Resume did not start the mirror

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

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