Mirrroring Issue

  • I am a bit of a SQL newbie so forgive me if this is a basic question. We are running SQL 2005 (latest SP) and mirror a database between 2 locations. By default we run high safety mode with a witness and automated failover. I need to do some work on the primary server and basically want to stop the auto failover for a short time and switch to High Performance - Asynch mode for the mirror. After some maintenace activity we will change back to High Safety with Witness.

    We have been able to accomplish this successfully however we are seeing an issue every time we move back to high safety mode. When we move back and apply the changes in SQL Management Studio we have one of the servers go to "synchronized" mode and one go to "synchronizing" mode. It varies between the primary and mirror which one is synchronized vs synchronizing, but it is reproduceable every time. I have tried leaving the synchronizing server alone for a while but its status never changes. ALso, using the mirroring monitoring it appears there is absolutely no activity despite the supposed synchronizing status.

    Has anyone seen this before? Can it be avoided? What is the best way to clean up the issue? We have found that stopping and restarting the SQL service on the "synchronizing" server seems to work fine, but that may not be the cleanest method. Just seems like an odd quirk. I have seen others report similar status but have seen no resolution overll.

    Thanks

Viewing post 1 (of 1 total)

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