Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

unrestored log? Expand / Collapse
Author
Message
Posted Monday, September 17, 2012 12:14 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 3:58 AM
Points: 1,061, Visits: 3,020
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?
Post #1359984
Posted Monday, September 17, 2012 1:15 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 10:29 AM
Points: 6,420, Visits: 13,810
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"
Post #1360002
Posted Monday, September 17, 2012 1:21 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 3:58 AM
Points: 1,061, Visits: 3,020
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.
Post #1360005
Posted Monday, September 17, 2012 5:20 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 1:14 PM
Points: 39,977, Visits: 36,340
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1360114
Posted Monday, September 17, 2012 5:30 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 3:58 AM
Points: 1,061, Visits: 3,020
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.
Post #1360118
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse