High availability deployment for TrueSight Operations Management
High availability (HA) is a redundancy operation that automatically switches to a standby server if the primary server fails or is temporarily shut down for maintenance. The following tables provide resources that you can use to locate planning, installation and configuration, upgrade, and troubleshooting a high-availability deployment.
Planning a high-availability deployment
Before downloading the installation files and deploying the TrueSight Operations Management components, review the planning guidelines and requirements.
Task | Resources |
---|---|
Plan to deploy Remedy Single Sign-On for high availability | |
Prepare to deploy the TrueSight Presentation Server component for high availability. | TrueSight Presentation Server high availability deployment Time taken for the standby node to become active When the standby node is unable to ping the active node, it can take approximately between 5-12 minutes to become active. |
Prepare to deploy the TrueSight Infrastructure Management components for high availability. | High-availability deployment and best practices for Infrastructure Management Considerations for a high-availability deployment of Infrastructure Management Network ports for a high-availability deployment of Infrastructure Management1 Supported platforms for High-availability cluster mode Failover and Failback recovery time The failover and failback time is the time taken by the server to become fully responsive and for the Infrastructure Management component status to be displayed as connected in the TrueSight console. The failover time is approximately between 10 -15 minutes and the failback time is approximately between 20 - 30 minutes. For more information, see Infrastructure Management Server high-availability architecture. |
Prepare to deploy the TrueSight App Visibility Manager component for high availability. | App Visibility Manager high-availability deployment |
Prepare to deploy the BMC Real End User Experience Monitoring Software Edition component for high availability. | High availability recommendations for Real End User Experience Monitoring Software Edition |
1 Application HA method |
Installing and configuring TrueSight Operations Management components for high availability
Task | Resources |
---|---|
Install and configure Remedy Single Sign-On. | Installing Remedy SSO in the high-availability mode using the TrueSight installer wizard Installing Remedy SSO in the high-availability mode using the TrueSight installer silently Installing Remedy SSO in the high-availability mode using the Remedy installer wizard Installing Remedy SSO in the high-availability mode using the Remedy installer silently |
Install and configure the TrueSight Presentation Server component. | Installing the Presentation Server in the high-availability mode using the wizard Installing the Presentation Server in the high-availability mode silently |
Install and configure the TrueSight Infrastructure Management component. | Application HA method Preparing to install Infrastructure Management in high availability cluster mode OS clustering method Preparing to install Infrastructure Management in high availability cluster mode |
Install and configure the TrueSight App Visibility Manager component. |
Upgrading TrueSight Operations Management a high-availability environment
Task | Resources |
---|---|
Upgrade TrueSight Presentation Server in an HA environment. | Upgrading the Presentation Server in the standalone mode silently |
Upgrade TrueSight Infrastructure Management in an HA cluster environment. | |
Upgrade App Visibility Server in an HA environment. | Upgrading the App Visibility server in the high-availability mode using the wizard Upgrading the App Visibility server in the high-availability mode silently |
Troubleshooting a high-availability deployment
Task | Resources |
---|---|
Troubleshoot the HA setup of Remedy Single Sign-On | |
Troubleshoot the HA setup of TrueSight Presentation Server | Troubleshooting a high-availability deployment |
Troubleshoot the HA setup of TrueSight Infrastructure Management | Troubleshooting an Infrastructure Management high-availability deployment |
Uninstalling
Task | Resources |
---|---|
Uninstall TrueSight Infrastructure Management in an HA environment. | Uninstalling Infrastructure Management in high-availability cluster mode |
Uninstall App Visibility Server in an HA environment. |
High-availability architecture diagrams
TrueSight Presentation Server
TrueSight Infrastructure Management
App Visibility Manager
Comments
Please add the failover timings for TSPS and TSIM HA somewhere in this section! Currently this information is not located in the correct areas of documentation. Example TSPS information is in the Troubleshooting section, which will never be viewed when planning for a deployment. Information can be found in below links.
For TSPS HA activities, you can refer the following doc link https://docs.bmc.com/docs/TSOperations/113/troubleshooting-a-high-availability-deployment-843620947.html
Please check the Note section: "The standby node if unable to ping the active node, takes approximately between 5-12 minutes to become active."
For TSIM HA activities, you can refer to the following doc https://docs.bmc.com/docs/TSInfrastructure/113/infrastructure-management-server-high-availability-architecture-774795954.html Please check the Note section: "Failover and failback time The failover and failback time is the time taken by the server to become fully responsive and for the Infrastructure Management component status to be displayed as connected in the TrueSight console. Failover time: 10 -15 min Failback time: 20 - 30 min"
Hello Barry McQuillan,
I have added two new notes as per our discussions. Closing this comment.
Log in or register to comment.