Caché Monitoring Guide - InterSystems Documentation

More documents

Recommendations

Info

Monitoring Caché Mirroring Performance roring cannot determined if the database is up to date, that journaling is not completed, or that the database is a target for dejournaling. Note: Catchup status is specified only for active mirrored databases. – Remove — Removes mirrored database from the mirror (that is, convert mirrored databases from mirrored to nonmirrored local use), as described in Removing Mirrored Databases from Mirrors in the “Mirroring” chapter of the Caché High Availability Guide. – More Actions — Lets you select or unselect mirrored databases so that you can perform the actions on multiple databases. Clicking an action link causes mirroring to attempt to perform the action (for example, Activate or Catchup the database). • List of async members, including member names, type, and status; secure async members that have not yet been authorized also display their X.509 distinguished name (DN). Note: If the DN is displayed, an Add button is displayed beneath the list of async members so that you can authorize the secure member as described in Adding Authorized Async Members to Mirrors in the “Mirroring” chapter of the Caché High Availability Guide. • List of authorized async members, including the X.509 DN and links to let you perform the following actions: – Edit — Lets you edit the secure async member’s X.509 distinguished name (DN). – Delete — Removes a secure async member from the mirror as described in Deleting Authorized Async Members from Mirrors. In addition, the page provides a link (View Mirror Journal Files) that lets you view all journal files or mirror journal files. 10.1.2 Mirror Monitor on Async Members When displayed from an async member, the mirror monitor page displays following summary information: • Async member name and, if applicable, the X.509 DN. • List of mirrors tracked by the async member, including the mirror names, address and port number of the mirror’s ISCAgent, the location (directory), type, and status of the async member, and a link (Details) that lets you display detailed information about each mirror. Click Details to display detailed information about the mirror identified in the row: • Mirror names. • Status of all mirror members (failover and async), including the member names, current role and status of each member, and database latency information. • Mirrored databases, including the database names, locations (directories), status, and links to let you perform any the following actions: – Active/Activate — Active indicates the mirrored database is in the correct directory on the correct system. Typically, Activate is displayed briefly for mirrored databases on a backup failover member or async members when the database is being restored from a backup or being copied from another mirror member. – Caught up/Catchup — Caught up indicates the mirrored database is up to date. Typically, on the async member, Catchup typically indicates the mirrored database is out of date, that mirroring cannot determined if the database is up to date, that journaling is not completed, or that the database is a target for dejournaling. Note: Catchup status is specified only for active mirrored databases. 94 Caché Monitoring Guide
Using the ^Mirror Utility – Remove — Removes mirrored database from the mirror (that is, convert mirrored databases from mirrored to nonmirrored local use), as described in Removing Mirrored Databases from Mirrors in the “Mirroring” chapter of the Caché High Availability Guide. – More Actions — Lets you select or unselect mirrored databases so that you can perform the actions on multiple databases. Clicking an action link causes mirroring to attempt to perform the action (for example, Activate or Catchup the database). 10.2 Using the ^Mirror Utility Mirroring provides a CHUI-based monitoring utility, accessible via the ^MIRROR utility. To start the utility, run the following case-sensitive command in the %SYS namespace in the Caché Terminal, and select Status Monitor from the Mirror Status submenu : %SYS> do ^MIRROR The best results are obtained when the monitor is run on the primary failover member, but it can be run from the backup member (or any connected async mirror member). Running the monitor from the primary failover member provides information about all the connected reporting nodes, some of which is not available when running the monitor from the backup or async members. Following is a sample of the output from the monitor: Status of Mirror JLAP at 19:37:09 on 12/02/2011 SYSONE SYSTWO SYSASYNC ------------------ --------------- --------------- --------------- Status Primary:active Backup:active Async LastJrnData 14881600 (#105) 14881600 (#105) 151092 (#105) CurJrnChkpnt 14881600 (#105) 151092 (#105) MinTransIndex 14881600 (#105) 14873168 (#105) 0 (#0) Journal file #105 MIRROR-JLAP-20111202.001 Mirror Databases: DBONE: Active Active Active DBTWO: Active Active Active The first section (the header) specifies the name of the mirror (JLAP) and the current date and time: Status of Mirror JLAP at 19:37:09 on 12/02/2011 The next section lists the systems: SYSONE SYSTWO SYSASYNC ------------------ --------------- --------------- --------------- Status Primary:active Backup:active Async This indicates that the JLAP mirror presently has a primary failover member called SYSONE, a backup failover member called SYSTWO, and an async member called SYSASYNC. The active status of the backup failover (SYSTWO) indicates that it is linked into the journal daemon on the primary and is presently eligible to take over; if the backup had a status of “Catchup.” it would indicate that the backup is presently not active and is in catch-up mode. The next section specifies the mirror journal checkpoint information: SYSONE SYSTWO SYSASYNC ------------------ --------------- --------------- --------------- . . . LastJrnData 14881600 (#105) 14881600 (#105) 151092 (#105) CurJrnChkpnt 14881600 (#105) 151092 (#105) MinTransIndex 14881600 (#105) 14873168 (#105) 0 (#0) Journal file #105 MIRROR-JLAP-20111202.001 Caché Monitoring Guide 95
Page 1 and 2:
Caché Monitoring Guide Version 201
Page 3 and 4:
Table of Contents About This Book .
Page 5 and 6:
B.4 Caché MIB Structure ..........
Page 7:
About This Book This book describes
Page 10 and 11:
Monitoring Caché Using the Managem
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Using the Caché Diagnostic Report
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Using the Caché Monitor The option
Page 26 and 27:
Using the Caché Monitor Option 4)
Page 28 and 29:
Using the Caché Monitor 3.2 Caché
Page 30 and 31:
Using the Caché Monitor Option 3)
Page 32 and 33:
Using the Caché Monitor Option 4 1
Page 34 and 35:
Using the Caché Monitor Input Fiel
Page 36 and 37:
Using the Caché Monitor 3.2.2.1 Ge
Page 38 and 39:
Using the Caché Monitor { // Get f
Page 41 and 42:
4 Gathering Global Activity Statist
Page 43 and 44:
Examples of ^GLOSTAT Output Statist
Page 45 and 46:
Examples of ^GLOSTAT Output Map: 22
Page 47 and 48:
Examples of ^GLOSTAT Output 4.3.6 E
Page 49 and 50: 5 Monitoring System Performance Usi
Page 51 and 52: Using ^PERFMON If you are running ^
Page 53 and 54: Using ^PERFMON Format: status = $$R
Page 55 and 56: Report Examples Metric Number 45 46
Page 57 and 58: 6 Monitoring Routine Performance Us
Page 59 and 60: Using ^PROFILE Option R X Descripti
Page 61: ^PROFILE Example There are 5 routin
Page 64 and 65: Examining Routine Performance Using
Page 73 and 74: 8 Monitoring Performance Using ^pBu
Page 75 and 76: Scheduling the ^pButtons Utility wi
Page 77 and 78: Customizing the ^pButtons Utility I
Page 79 and 80: Customizing the ^pButtons Utility s
Page 81 and 82: Performance Reports Created by ^pBu
Page 93 and 94: 9 Monitoring Performance Using ^mgs
Page 95 and 96: Column RemRrefs * RouLaS RemRLaS *
Page 97: Considering Seizes, ASeizes, and NS
Page 102 and 103: Monitoring Caché Mirroring Perform
Page 104 and 105: Caché History Monitor • SYS.Hist
Page 107 and 108: A Monitoring Caché Using BMC PATRO
Page 109 and 110: Caché PATROL Knowledge Modules Arg
Page 111 and 112: Caché Metrics Used with BMC PATROL
Page 113 and 114: Caché Metrics Used with BMC PATROL
Page 115 and 116: B Monitoring Caché Using SNMP This
Page 117 and 118: Caché MIB Structure 3. When you ed
Page 119 and 120: Caché MIB Structure The Caché sub
Page 121 and 122: Sample User-defined SNMP Monitor Cl
Page 123: Sample User-defined SNMP Monitor Cl
Page 126 and 127: Monitoring Caché Using WMI 3. Sele
Page 128 and 129: Monitoring Caché Using WMI %SYS>Do
Page 130 and 131: Monitoring Caché Using Web Service
show all

Caché Monitoring Guide - InterSystems Documentation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?