Post reply

Pausing DB Mirror

  • September 27, 2011 at 2:41 am

    #248772

    Hi All,

    I have DB Mirroring with High Safety without automatic failover (Synchronous).

    We have an Reboot activity on Mirror server (passive node).

    My question here is before rebooting the Mirror server

    1. Do we need to "Pause/Stop" the DB mirror or not?

    2. Other than pausing DB mirror, anything else need to do?

    I am new to DB Mirroring. Please help me.

    Thanks

  • September 27, 2011 at 4:36 am

    #1387025

    personally i would ensure the 2 are synchronised and then pause the session, reboot the mirror and then resume the session

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

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

  • September 27, 2011 at 5:22 am

    #1387038

    Thanks Perry...

    But Please tell me what to do in case of below senario:

    1. Databases are synchronised

    2. I have paused the DB mirror

    3. Started Reboot of Mirror Server (Passive) and it was taken 15 mins to boot the server

    Assume i havent stopped the application during Reboot(Bcoz, it is urgent reboot and we dont get the downtime that easyly for Application)

    In above 3rd step, During the reboot time (in 15mins),If my Primary Server Database log file reaches to Max limit or if it is full, What should i have to do?

    If the above situation occurs what will be the resolution?

    Thanks

  • September 27, 2011 at 5:28 am

    #1387039

    i dont know much about your setup, is it likely the log will fill up in 15 mins?

    If you know the mirror would be down for an excessive period of time you should remove the session

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

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

  • September 27, 2011 at 11:11 am

    #1387364

    If the mirror in synchronous mirroring goes down the principle will still be able to run, so yes you should be fine to pause it, bounce the box, and then restart mirroring. Preferably off-hours or during a low traffic time because there will be a surge of the log that hasn't been sent yet, of course.

  • September 28, 2011 at 2:57 am

    #1387603

    I would echo Perry and Derrick, though would say that we dont 'pause' our mirrors. The only difference is warning/errors are logged in the server log of each server and the monitor job fails. Pauseing is cleaner but not necassery.

    We have lots of mirrors on each server so tbh i think we dont pause cause we're lazy. If you only have 1 db, may as well pause but it really isnt t hat critical.

    Adam Zacks-------------------------------------------Be Nice, Or Leave

  • September 28, 2011 at 3:26 am

    #1387616

    to extend further on what i have said, when i say excessive period i mean a few days, weeks, etc

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

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

  • September 28, 2011 at 6:39 am

    #1387704

    Friends thanks for your replies, I gained good info.

    By the way i have completed my activity(Rebooting Mirror for Patch upgrade) by Pausing Mirroring on 4 databases without any issues (thanks god).

    Thanks for timely support.

Viewing 8 posts - 1 through 7 (of 7 total)

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