IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Configure for high availability and disaster recovery
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Configure for Summarization and Pruning Agent high availability and disaster recovery
Connect the Summarization and Pruning Agent to the hub monitoring servers. When the Hot Standby option is used, the Summarization and Pruning Agent must be configured with the standby hub as the secondary monitoring server. However, there are some additional considerations for achieving high availability with the Summarization and Pruning Agent.
Only one Summarization and Pruning Agent may be running against a warehouse database. Thus, it is important to ensure that there is data integrity within the database and that there is no database deadlock between two competing agents. So, by default, only one Summarization and Pruning Agent must be installed and running.
As in the Warehouse Proxy Agent set up, you want to install a second Summarization and Pruning Agent that serves as a cold backup to the primary Summarization and Pruning Agent. By default, the backup Summarization and Pruning Agent is disabled. Write a situation that detects when the primary Summarization and Pruning Agent is down and automatically starts up the backup Summarization and Pruning Agent through a Take Action command.
Care must be taken in writing the Take Action command to ensure that only one Summarization and Pruning Agent is running at any given time. To ensure the two Summarization and Pruning Agents are not running at the same time, perform the following steps:
- Have the situation trigger only after the second or third missed heartbeat. Occasionally, there are temporary outages triggered by network problems or routine maintenance. You do not want the automated Take Action to occur during a temporary outage.
- When starting up the backup Summarization and Pruning Agent using a Take Action command, the primary Summarization and Pruning Agent must be disabled so that it does not accidentally restart until an administrator manually corrects the problem.
- Write up a documented procedure to ensure that only one of the Summarization and Pruning Agents is brought back online following a failover.
Parent topic:
Configure for high availability and disaster recovery