Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Configuring the recovery BMC TrueSight Infrastructure Management Server (Sybase)

After you configure the remote event cells, you must configure the recovery BMC TrueSight Infrastructure Management Server.

For the Calbro Services example, this section explains steps required to configure the recovery BMC TrueSight Infrastructure Management Server, newyork.calbro.com, for disaster recovery.

Step 1: Stop the primary BMC TrueSight Infrastructure Management Server

To stop the primary BMC TrueSight Infrastructure Management Server, run the pw system stop command on the primary server.

Note

If both primary and secondary servers are on the same network, you must stop Infrastructure Management on the primary server before installing the software on the recovery server. After the recovery server is installed and configured, and then turned off with the pw system stop command, you can restart the primary server with the pw system start command.

If you forget to do this, the installation will fail with an error, because SAP SQL Anywhere Database does not allow two instances with the same name on the same network.

Step 2: Install BMC TrueSight Infrastructure Management Server on the recovery server

On the recovery server, install BMC TrueSight Infrastructure Management Server and provide the following parameters that you recorded when you installed BMC TrueSight Infrastructure Management Server on the primary server.

  • Installation location
  • SIM cell inputs
  • Admin cell inputs
  • Administrator information
  • Central Monitoring Repository destination directory

To enable Disaster Recovery Mode at the time of installation

  1. On the Configuration Tasks screen, select Disaster Recovery Mode.
  2. On the Configuring Disaster Recovery screen, enter the Hostname Alias <aliasName>.
     The default alias is pronet.

If you do not enable Disaster Recovery during installation, you can configure the alias after installation by running the pw system change hostname aliasName command.

For detailed information about the installation of BMC TrueSight Infrastructure Management Server, see the following topics:

Step 3: Edit the hosts files

On the recovery BMC TrueSight Infrastructure Management Server, edit the hosts file with an <aliasName> that is the same alias name as the one on the primary server.

  1. Open the hosts file, located in the following directory:
    • (Windows) \WINDOWS\SYSTEM32\drivers\etc
    • (UNIX) /etc

  2. In the hosts file, add an entry for the alias name set for the primary BMC TrueSight Infrastructure Management Server by using the following syntax:

    127.0.0.1 localhost <aliasName>

    ::1 localhost <aliasName> (for IPv6 systems)

For the Calbro Services example, <aliasName> refers to pronet, which was set as the primary BMC TrueSight Infrastructure Management Server.

Step 4: (Windows only) Set the startup type of Infrastructure Management services to manual

  1. On a command prompt, type services.msc, and press Enter.
  2. Access the properties of the following services, and set the Startup type to Manual.
    • Infrastructure Management Database Engine
    • BMC TrueSight Infrastructure Management Server

Step 5: Restart the computer with the recovery BMC TrueSight Infrastructure Management Server

Restart the computer with the recovery BMC TrueSight Infrastructure Management Server for the changes to take effect.

Step 6: Stop the recovery BMC TrueSight Infrastructure Management Server

  • (Windows) From the system icon tray, right-click the Infrastructure Management icon, and click Server Stop.
  • (Solaris) Access the pw command-line interface, and enter the pw system stop command.

Step 7: End additional processes

If the following processes are running on your computer, end the processes.

  • (Windows) Pproxsrv.exe and Pwtray.exe
  • (Solaris) Pproxsrv

Step 8: Copy the configuration files

Copy the entire \pw directory from the primary BMC TrueSight Infrastructure Management Server to the \pw directory of the recovery BMC TrueSight Infrastructure Management Server.

Note

BMC recommends that you use any third-party file synchronization and backup software to copy the \pw directory because traditional copying can result in any unexpected failure.

Step 9: Clear all the log files

On the recovery BMC TrueSight Infrastructure Management Server, navigate to the \pw\pronto\logs directory, and move all the log files to a backup directory.

Step 10: Start the recovery BMC TrueSight Infrastructure Management Server

  • (Windows) From the system icon tray, right-click the Infrastructure Management icon, and click Server Start.
  • (Solaris) Access the pw command-line interface, and enter the pw system start command.

Note

If you have problems with starting the service, ensure that the dbCmdLine.conf file is updated with the database name. The file is located in the pw\sybase directory (Windows) or the pw/sybase directory (Solaris).

Step 11: Validate the configuration

  1. Launch the operator console by using the alias name set for the primary BMC TrueSight Infrastructure Management Server in a browser.
     For the Calbro Services example, access the console through the following URL:

    http://pronet
  2. Validate the data by using the FlashCheck option.

     For more details about the FlashCheck option, see Examining current data (FlashCheck).

Step 12: Stop the recovery BMC TrueSight Infrastructure Management Server

  • (Windows) From the system icon tray, right-click the Infrastructure Management icon, and click Server Stop.
  • (Solaris) Access the pw command-line interface, and enter the pw system stop command.

Note

For any licensing issues or problems, contact BMC Customer Support.

Step 13: Restart the primary BMC TrueSight Infrastructure Management Server

To restart the primary BMC TrueSight Infrastructure Management Server, run the pw system start command.

Note

BMC recommends running the

pw alarmsync
command to synchronize the database and the impact management cell database after the recovery.

Related topic

Worksheet-for-configuring-a-disaster-recovery-system-for-Infrastructure-Management-Oracle

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*