September 17, 2012 at 12:14 am
Hi,
Principal server mirroring monitor history logs (intervel time every 3 min)
Unsent Log 7588 KB
unrestored log 600 KB
Mirror over head - 40 Milliseconds
Next intervel time those are 0 kb, 0 millseconds,
Does it means everything restored at mirror database?
September 17, 2012 at 1:15 am
ananda.murugesan (9/17/2012)
Hi,Principal server mirroring monitor history logs (intervel time every 3 min)
Unsent Log 7588 KB
unrestored log 600 KB
Mirror over head - 40 Milliseconds
Next intervel time those are 0 kb, 0 millseconds,
Does it means everything restored at mirror database?
What does the mirroring status tell you on each occasion for the principal and mirror?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 17, 2012 at 1:21 am
What does the mirroring status tell you on each occasion for the principal and mirror?
Every occasion for the principal & mirror server status is sychcronized mode.
September 17, 2012 at 5:20 am
The unrestored log is the portion of the log at the mirror server that has not yet been replayed against the mirror database. Everything's been send across (it is synchronised mirroring), the replay is just very slightly behind. At 600k, I wouldn't worry, that shouldn't take more than a few seconds to replay if/when a failover occurs.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 17, 2012 at 5:30 am
ok, SQL agent side mirror logs jobs running every 3 minites, I understod the next time intervel history logs display those were 0KB, 0 milliseconds, so everything restored at mirror database at next time sychronized . I don't want worry about it.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply