Caché Monitoring Guide - InterSystems Documentation
Caché Monitoring Guide - InterSystems Documentation
Caché Monitoring Guide - InterSystems Documentation
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Monitoring</strong> <strong>Caché</strong> Mirroring Performance<br />
Following are descriptions of the mirror journal checkpoint information displayed above:<br />
• LastJrnData — The address of the last journal data written to disk (to the mirror journal file) on each system. On a<br />
mirror that has an active (caught-up) backup, the LastJrnData on the backup should be the same as the LastJrnData on<br />
the primary. Sometimes, however, it is possible to observe the backup being ahead of the primary, and vice-versa, due<br />
to the way the data is presently collected.<br />
• CurJrnChkpnt — Relates to how up to date the databases are with respect to the dejournaling processes on the backup<br />
system. This information is updated periodically, but may not be reported in an up-to-date (to-the-second) format;<br />
however, if the backup is restarted, it begins processing updates from this journal offset.<br />
• MinTransIndex — The journal offset of the earliest open transaction on the primary. This indicates how far back<br />
transaction rollback needs to occur during a failover.<br />
• Journal file — The currently active mirror journal file name.<br />
The last section lists the mirrored databases, including the mirror status, on each node; typically, all databases are listed as<br />
active on each node:<br />
SYSONE SYSTWO SYSASYNC<br />
------------------ --------------- --------------- ---------------<br />
. . .<br />
Mirror Databases:<br />
DBONE: Active Active Active<br />
DBTWO: Active Active Active<br />
96 <strong>Caché</strong> <strong>Monitoring</strong> <strong>Guide</strong>