The following procedures explain how to install the BMC TrueSight Infrastructure Management Server in HA mode on primary and secondary servers:
Install the BMC TrueSight Infrastructure Management Server on the primary server.
Install the BMC TrueSight Infrastructure Management Server on the secondary server.
Note
Infrastructure Management is not supported on VMware with VMWare Fault Tolerance (FT) as Infrastructure Management high availability support.
The following are the prerequisite tasks that you must perform before installing Infrastructure Management in HA mode:
Ensure that the cluster name does not contain an underscore (_).
You can manually install the BMC TrueSight Infrastructure Management Server on the primary server. Automatic Failover is handled by the Microsoft Cluster Server software.
To install the BMC TrueSight Infrastructure Management Server on the primary server on Microsoft Windows:
install.cmd -J INSTALL_TYPE=PRIMARY
After installing the BMC TrueSight Infrastructure Management Server on the primary server, perform the following steps:
Installing the BMC TrueSight Infrastructure Management Server on the secondary server
The following procedure explain how to install the BMC TrueSight Infrastructure Management Server on the secondary server. Automatic Failover is handled by the Microsoft Cluster Server software.
To install the BMC TrueSight Infrastructure Management Server on the secondary server on Microsoft Windows:
Open the command prompt with the Run as administrator option. Access the <installerLocation>\Windows\TSIMServer\Disk1 directory (where installerLocation is a directory where you have downloaded installer files) and run the following command:install.cmd -J INSTALL_TYPE=SECONDARY
On the Configuring Firewall Rules page, perform one of the following tasks, and click Next. You must configure firewall rules to allow BMC TrueSight Infrastructure Management processes to communicate through the firewall.
Note
If you turn on the firewall when Remote Desktop Protocol is running, the Remote Desktop Protocol session may get disconnected if Remote Desktop Protocol is blocked by the firewall.
The Windows Firewall inbound rules are configured. An error message appears if you have not started the Windows Firewall.
Note
Ensure that you start the Windows Firewall before you configure the Windows Firewall rules. For more information about starting the Windows Firewall, see To start Windows Firewall.
When the BMC TrueSight Infrastructure Management Server installation is complete, you can choose View Logs to open the installation logs. The installer creates all BMC TrueSight Infrastructure Management services and registry entries.
Run the pns.reg file located at installationDirectory\pw\pproxy\PNS\security. If you do not run this file, during a failover, existing policy configurations are not applied on the BMC PATROL Agent and policy creation and update fails.
Create dependencies for the BMC TrueSight Infrastructure Management Server cluster resource.
pw system stop
command.Go to Start > All Programs > Administrative Tools > Failover Cluster Manager and click on the cluster name.
Scroll down to the Cluster Core Resources section, right-click PnService, and click Properties.
pw system start
command.Restart both the primary and secondary servers.
Notes
After the BMC TrueSight Infrastructure Management Server is installed on both the primary and secondary servers, a “PnService” resource is created on the cluster.
If this resource is not created automatically, you may receive warnings. To create the resource, perform the following steps:
(Windows Server 2008) cluster.exe resource
PnService
/ONLINE /WAIT:
5
00
powershell.exe Start-ClusterResource -Name PnService -Wait 500
If the services are not running on the secondary server and the ProServices.log file contains warnings for database connections, perform the following:
Navigate to the following registry paths and change the dbservice engine name to storm_<logicalclusterName>
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI
Open the mcell.dir file located in the installationDirectory\pw\server\etc directory and change the cluster name to storm_<logicalclusterName> for pncell and Admin cell.
Related topics
Installing the BMC TrueSight Infrastructure Management Server in HA mode on Linux/Solaris