Installing the Infrastructure Management server in the application high-availability and disaster recovery mode

This deployment is supported only with an Oracle database. Application high-availability has to be configured at both primary and recovery sites. Other configurations are not supported. 

You need to perform the following tasks to install the Infrastructure Management server in the application high-availability and disaster recovery mode:

• Overview
• Step A: To install the Infrastructure Management server at the primary site
• Step B: To install the Infrastructure Management server at the recovery site
• Step C: To perform post-install tasks after installing at the recovery site
• Troubleshooting installation issues
• Bringing up the recovery or primary site
• Next step in the Installation process

Overview

The following diagram provides an overview of the Infrastructure Management deployment in application high-availability and disaster recovery.

Step A: To install the Infrastructure Management server at the primary site

Review the Preparing to install Infrastructure Management topic and do the following:

1. Install the Infrastructure Management server on computer A. Ensure that you do the following:
   • Choose the disaster recovery option and Oracle as the database. 

   • Enter an alias name (For example, Alias1). 

     Note

     Ensure that the alias names contain only alphanumeric text and do not contain any special characters like hyphen( - ) and underscore( _ ).
     For example: alias name could be pronet, pronet2, or pronettsim.

   • Enter an Oracle user name and Oracle report user name that you created earlier (For example, db_user_pronet_tsim_a and db_user_report_tsim_a).

1. 
   

   • Installing the Infrastructure Management server in the standalone mode using the wizard.

   • Installing the Infrastructure Management Server in the standalone mode silently.

2. Install the Infrastructure Management server on computer B. Ensure that you do the following:
   • Choose the disaster recovery option and Oracle as the database. 
   • Enter a different alias name than computer A (For example, Alias2). 
   • Enter an Oracle user name and Oracle report user name that you created earlier (For example, db_user_pronet_tsim_b and db_user_report_tsim_b).

   • Installing the Infrastructure Management server in the standalone mode using the wizard.

   • Installing the Infrastructure Management Server in the standalone mode silently.

3. Configure application high-availability between computers A and B. See Step C in the topic Installing and configuring the Infrastructure Management server for application high-availability
   When you run the pw ha enable command, enter the alias name (For example, Alias1), instead of the host name.

Step B: To install the Infrastructure Management server at the recovery site

Do the following:

1. Choose the Oracle database option:
   • If us‌ing Oracle Data Guard — Do one of the following:
     • If your primary Oracle database can be accessed by the recovery site Infrastructure Management servers, use the primary Oracle database and users db_user_pronet_tsim_a_dr, db_user_pronet_tsim_b_dr, db_user_report_tsim_a_dr, db_user_report_tsim_b_dr while installing the recovery site Infrastructure Management servers. You do not need to stop the primary site Infrastructure Management servers.
     • If your primary Oracle database cannot be accessed by the recovery site Infrastructure Management servers, shut down the primary site Infrastructure Management servers. An Oracle DBA must switchover to make the standby Oracle database active. Use this active Oracle database instance and users db_user_pronet_tsim_a_dr, db_user_pronet_tsim_b_dr, db_user_report_tsim_a_dr, db_user_report_tsim_b_dr while installing the recovery site Infrastructure Management servers.
   • If not us‌ing Oracle Data Guard — Point to a dummy Infrastructure Management Oracle database by creating users as explained in Preparing to install Infrastructure Management.
2. Install the Infrastructure Management server on computer A_DR. Ensure that you do the following:
   • Choose the disaster recovery option and Oracle as the database. 
   • The installation path must be the same as that of the primary site server. 
   • Enter the alias name that you chose for computer A at the primary site (For example, Alias1). 
   • Enter an Oracle user name and Oracle report user name that you created earlier (For example, db_user_pronet_tsim_a_dr and db_user_report_tsim_a_dr).

   • Installing the Infrastructure Management server in the standalone mode using the wizard.

   • Installing the Infrastructure Management Server in the standalone mode silently.

3. Install the Infrastructure Management server on computer B_DR. Ensure that you do the following:
   • Ensure that you choose the disaster recovery option and Oracle as the database. 
   • The installation path must be the same as that of the primary site server. 
   • Enter the alias name that you chose for computer B at the primary site (For example, Alias2). 
   • Enter an Oracle user name and Oracle report user name that you created earlier (For example, db_user_pronet_tsim_b_dr and db_user_report_tsim_b_dr).

   • Installing the Infrastructure Management server in the standalone mode using the wizard.

   • Installing the Infrastructure Management Server in the standalone mode silently.

4. Configure application high-availability between computers A_DR and B_DR. See Step C in the topic Installing and configuring the Infrastructure Management server for application high-availability
   When you run the pw ha enable command, enter the alias name (For example, Alias1), instead of the host name.

Step C: To perform post-install tasks after installing at the recovery site

1. Run the pw sys stop command to stop the secondary Infrastructure Management server processes at the primary site.
   Ensure that all internal processes are stopped by using the pw process list command.

1. Run the pw sys stop command to stop the primary Infrastructure Management server processes at the primary site.
   Ensure that all internal processes are stopped by using the pw process list command.

1. Take a backup of the installationDirectory/pw/ folder on both computers at the primary site. 
2. Run the pw sys stop command to stop the secondary Infrastructure Management server processes at the recovery site.
   Ensure that all internal processes are stopped by using the pw process list command.

1. Run the pw sys stop command to stop the primary Infrastructure Management server processes at the recovery site.
   Ensure that all internal processes are stopped by using the pw process list command.

1. Move the installationDirectory/pw/ folder on both recovery site computers to another location.
2. Restore the backup of the installationDirectory/pw/ folder from computer A to A_DR and from computer B to B_DR. Ensure that you have the correct permissions if you are using an archive and extracting the folders.
3. Clear all log files on the recovery TrueSight Infrastructure Management servers. Navigate to the \pw\pronto\logs directory, and move all log files to a backup directory.

4. At the recovery site, run the pw dbconfig set command on both primary and secondary Infrastructure Management servers to point to the active Oracle database:

   pw dbconfig set -database oracle -host Primary_Oracle_hostname:1521 -sid ORA12C -username db_user_pronet_tsim_a -password <password> -repusername db_user_report_tsim_a -reppassword <password>
5. Verify that the recovery site is functional:
   1. At the primary site, run the pw sys stop command to stop the secondary Infrastructure Management server processes.
      Ensure that all internal processes are stopped by using the pw process list command.
   2. At the primary site, run the pw sys stop command to stop the primary Infrastructure Management server processes.
      Ensure that all internal processes are stopped by using the pw process list command.
   3. At the recovery site, run the pw sys start command to start the primary Infrastructure Management server processes.
      Ensure that the primary server has successfully started by running the pw license list command.

1. 1. At the recovery site, run the pw sys start command to start the secondary Infrastructure Management server processes.
      Ensure that the secondary server has successfully started by running the pw license list command. 
2. Run the pw sys stop command to stop the secondary Infrastructure Management server processes at the recovery site.
   Ensure that all internal processes are stopped by using the pw process list command.

1. Run the pw sys stop command to stop the primary Infrastructure Management server processes at the recovery site.
   Ensure that all internal processes are stopped by using the pw process list command.

1. At the primary site, run the pw sys start command to start the primary Infrastructure Management server processes.
   Ensure that the primary server has successfully started by running the pw license list command. 
2. At the primary site, run the pw sys start command to start the secondary Infrastructure Management server processes.
   Ensure that the secondary server has successfully started by running the pw license list command.

Troubleshooting installation issues

If you face issues during installation, see Troubleshooting-an-Infrastructure-Management-deployment.

Bringing up the recovery or primary site

To bring up the recovery or primary site, or to verify the disaster recovery configuration, see Bringing up the recovery or primary TrueSight Infrastructure Management Server in application high-availability and disaster recovery mode

Next step in the Installation process

Step 5 Phase B — Now that you have successfully installed the Infrastructure Management Server, you must install the Integration Service and Remote Cell.