Monitoring, Version 6.2
The hub monitoring server is a highly reliable component, and many users choose to run with a single hub monitoring server and use backup and restore operations to ensure that they have minimum downtime in case of a hardware failure. Other users require higher availability and less downtime and employ multiple hub monitoring servers to achieve either a high availability (HA) environment, disaster recovery (DR) environment, or a combination (high availability and disaster recovery) environment. The following section describes some of the strategies used to achieve the desired level of availability and downtime.
If you have a smaller environment and do not want to invest in additional hardware, you can set up a single hub monitoring server. Because the hub monitoring server is very reliable, there is no need to purchase any additional hardware. You can expect some downtime when patching the hub monitoring server. There are times when the monitoring server must be recycled. If you use one hub, it is important that you use a good backup and restore strategy. You can install the hub in a virtualized environment such as VMWare so that you can quickly bring up an identical virtual operating system to replace the original. In addition, there is a VMWare HA option coming with release 3.0.x which automates the start of a failing image on a different node.
If you want to achieve high availability, you have two options. The first option is to implement the Hot Standby feature that is built into the monitoring server. Extensive large scale testing has taken place to ensure that Hot Standby is a robust solution. The second option is to implement an operating system cluster. Extensive testing has been performed with some operating system clusters. The first two supported clustering options are Windows® Cluster and High Availability Cluster Multi-Processing (HACMP).
The main difference between the clustering options is the scripts to control the automated control of resources within the cluster. In this sense, Tivoli Monitoring is cluster-ready for other clustering solutions.
For detailed steps for configuring Clustering search the following text strings to find solutions in Tivoli® Open Process Automation Library (OPAL):
You can find more information about using a z/OS® hub monitoring server by searching for "moveable HUB TEMS z/OS" or navigation code "1TW10TM1W" in the Tivoli Open Process Automation Library (OPAL).
See the IBM Tivoli Monitoring Installation and Setup Guide for instructions on configuring the Hot Standby option, and for a detailed clustering scenario.
[ Top of Page | Previous Page | Next Page | Contents | Index ]