July 24, 2012 at 2:26 am
I have two databsaes in async mirroring. Today there was a massive value for unsent log (it was showing over 50GB) and a time to send log at over an hour.
I was investigating when all of a sudden the mirroring monitor showed mirroirng changed to a status fo "synchronizing". now the log has been moved to the mirror and the unrestored log is quite high, but at least its working.
I cannot figure out why this happened. there are no long running open transactions, no huge data loads going on and no network connectivity issues between servers. anyone got any ideas what might have happened?
July 24, 2012 at 2:54 am
winston Smith (7/24/2012)
I have two databsaes in async mirroring. Today there was a massive value for unsent log (it was showing over 50GB) and a time to send log at over an hour.I was investigating when all of a sudden the mirroring monitor showed mirroirng changed to a status fo "synchronizing". now the log has been moved to the mirror and the unrestored log is quite high, but at least its working.
I cannot figure out why this happened. there are no long running open transactions, no huge data loads going on and no network connectivity issues between servers. anyone got any ideas what might have happened?
Were both endpoints started?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 24, 2012 at 7:04 am
Is your disk in mirrored database fast enough to catch up with principal database? What does the Avg. Disk Write Queue Length counter show?
July 24, 2012 at 8:10 am
I found out that a large update caused the issue. there was a code drop that modified a lot of data. nobody was notified of this, hence i thought this must be caused by other issues.
Thanks for the help all.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply