25.01.2015 Views

Caché Monitoring Guide - InterSystems Documentation

Caché Monitoring Guide - InterSystems Documentation

Caché Monitoring Guide - InterSystems Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

10<br />

<strong>Monitoring</strong> <strong>Caché</strong> Mirroring Performance<br />

This chapter describes the tools that are provided to monitor mirrors:<br />

• Using the Mirror Monitor<br />

• Using the ^MIRROR Utility<br />

10.1 Using the Mirror Monitor<br />

You can monitor mirrors through the [System] > [Mirror Monitor] page from either failover member or any async members.<br />

The displayed information varies slightly depending on the member on which you run the mirror monitor:<br />

• Mirror Monitor on Failover Members<br />

• Mirror Monitor on Async Members<br />

10.1.1 Mirror Monitor on Failover Members<br />

When displayed from a failover member, the mirror monitor displays the following summary information:<br />

• Mirror name.<br />

• Failover member names, superserver addresses (which are used by external systems to communicate with failover<br />

members), and mirror private addresses (which are used by the failover members to communicate with each other).<br />

It also displays tables providing the following detailed information:<br />

• Status of all mirror members (failover and async), including the member names, current role and status of each member,<br />

and database latency information.<br />

• Mirrored databases, including the database names, location (directory) of the database, mirror status, and links to let<br />

you perform the following actions:<br />

– Active/Activate — Active indicates the mirrored database is in the correct directory on the correct system. Typically,<br />

Activate is displayed briefly for mirrored databases on a backup failover member or async members when the<br />

database is being restored from a backup or being copied from another mirror member.<br />

– Caught up/Catchup — Caught up indicates the mirrored database is up to date. Typically, on the primary failover<br />

member, Catchup indicates the mirrored database is read-only (because mirroring cannot determine if it is up to<br />

date). On the backup failover member, Catchup typically indicates the mirrored database is out of date, that mir-<br />

<strong>Caché</strong> <strong>Monitoring</strong> <strong>Guide</strong> 93

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!