Configuring the Presentation Server in the high-availability and disaster recovery mode

Where you are in the Installation process

To configure the TrueSight Presentation Server in the high-availability and disaster recovery mode

Every installation of the Presentation Server is disaster-recovery ready. Therefore, you do not need any configuration on the primary TrueSight Presentation Server. 

You need to configure the recovery servers only. To do this, perform the following tasks:

• Before you begin
• Step A: Configure the primary computer on the recovery site
• Step B: Configure the secondary computer on the recovery site
• Back up folders regularly
• Apply patches and configuration changes 

Before you begin

• Ensure that TrueSight Presentation Server in installed in the high-availability mode at the primary site and the recovery site with the same database name. You must also ensure that both the primary and secondary computers are installed on the same platform and are using the same ports and operating system locale.

• 
  

  • Installing the Presentation Server in the high-availability mode using the wizard

  • Installing the Presentation Server in the high-availability mode silently

• Ensure that Remedy Single Sign-On configured at the primary site and the recovery site is using the same port number and is set with the same password. 
• On both, the primary site and the recovery site, stop the primary computer and the secondary computer.

Step A: Configure the primary computer on the recovery site

1. On the recovery site, primary computer, take a backup of the following folders. Ensure that you save them with different names.
   • Windows: 
     • %TRUESIGHTPSERVER_HOME%\truesightpserver\data
     • %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\elasticsearch\data
     • %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\cma
       
   • Linux: 
     • $TRUESIGHTPSERVER_HOME/truesightpserver/data
     • $TRUESIGHTPSERVER_HOME/truesightpserver/modules/elasticsearch/data
     • $TRUESIGHTPSERVER_HOME/truesightpserver/modules/cma
       

2. Go to the primary site. Copy the following files from the primary site, primary computer to the recovery site, primary computer:

   Note

   BMC recommends that you use any third-party file synchronization and backup software to copy these directories because traditional copying can result in an unexpected failure.

   • Windows:
     • %TRUESIGHTPSERVER_HOME%\truesightpserver\data
     • %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\elasticsearch\data
     • %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\cma
       
   • Linux:
     • $TRUESIGHTPSERVER_HOME/truesightpserver/data
     • $TRUESIGHTPSERVER_HOME/truesightpserver/modules/elasticsearch/data
     • $TRUESIGHTPSERVER_HOME/truesightpserver/modules/cma
       
3. On the recovery site, primary computer, perform these steps:
   1. (Linux only) Run this command as a non-root user: chmod 700 -R $TRUESIGHTPSERVER_HOME/truesightpserver/data
   2. Start the database by running this command: tssh process start database

   3. Verify if the database is up and running by running this command: tssh server status

      Steps to perform if the database server fails to start

      1. Run the following commands on the recovery TrueSight Presentation Server:
         
         • Windows:
           1. cd %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\pgsql\bin
           2. pg_resetxlog.exe "%TRUESIGHTPSERVER_HOME%\truesightpserver\data\pgsql"
         • Linux:
           1. cd $TRUESIGHTPSERVER_HOME/truesightpserver/modules/pgsql/bin
           2. ./pg_resetxlog "$TRUESIGHTPSERVER_HOME/truesightpserver/data/pgsql"
      2. If you see the following message, run this command: pg_resetxlog.exe -f "%TRUESIGHTPSERVER_HOME%\truesightpserver\data\pgsql"
         The database server was not shut down cleanly. Resetting the transaction log might cause data to be lost. If you want to proceed anyway, use -f to force reset.
      3. Start the database process by running this command: tssh process start database
   4. Change the host name by running this command: tssh dr configure <RecoveryPrimaryTSPSHostName>
   5. Stop the database by running this command: tssh process stop database
   6. Edit the pg_hba.conf file located at the following location.
      • Windows: %TRUESIGHTPSERVER_HOME%\truesightpserver\data\pgsql\
      • Linux: $TRUESIGHTPSERVER_HOME/truesightpserver/data/pgsql/
   7. In the pg_hba.conf file, add the following properties to provide the secondary computer, load balancer, and the database details and then save the file:
      • hostnossl replication <TSPSDatabaseUserName> <SecondaryHostName> trust
      • hostnossl replication <TSPSDatabaseUserName> <LoadBalancerName> trust
   8. Start the Presentation Server by running this command: tssh server start skipHACheck

   9. Set the Remedy Single Sign-On details by running the following commands:

      1. tssh properties set tspsProxyHosts "<RemedySSOHostName>,<RecoverySitePrimaryHostName>,<RecoverySiteSecondarHostName>,<loadbalancername>"

         In the above command, the following definitions apply:

         • <RemedySSOHostName> refers to the fully qualified host name of Remedy Single Sign-On.
         • <RecoverySitePrimaryHostName> refers to the recovery site, primary computer's fully qualified host name.
         • <RecoverySiteSecondarHostName> refers to the recovery site, secondary computer's fully qualified host name.
         • <loadbalancername> refers to the recovery site, load balancer name.

         Example:  tssh properties set tspsProxyHosts "RSSO.bmc.com,RecPrimaryComp.bmc.com,RecSec.bmc.com,LB.bmc.com"

      2. tssh properties set bmc.sso.servername <RemedySSOHostName>
      3. tssh properties reload

      Applies only if you are using a different load balancer in the production environment

      In the production environment, if you are using a different load balancer name than the one in the non-production environment, then in addition to the Remedy Single Sign-On details, you must also set the load balancer name. To do this, you run the following commands:

      1. tssh properties set loadbalancername <RecoveryLoadBalancerName>
      2. tssh properties reload

Step B: Configure the secondary computer on the recovery site

1. On the recovery site, secondary computer, take a backup of the following folders. Ensure that you save them with different names.
   • Windows: 
     • %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\elasticsearch\data
       
   • Linux: 
     • $TRUESIGHTPSERVER_HOME/truesightpserver/modules/elasticsearch/data

2. Go to the primary site. Copy the following files from the primary site, secondary computer to the recovery site, secondary computer:

   Note

   BMC recommends that you use any third-party file synchronization and backup software to copy these directories because traditional copying can result in an unexpected failure.

   • Windows:
     • %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\elasticsearch\data
   • Linux:
     • $TRUESIGHTPSERVER_HOME/truesightpserver/modules/elasticsearch/data
3. On the recovery site, secondary computer, perform these steps:
   1. Start the Presentation Server by running this command: tssh server start
   2. Change the host name by running this command: tssh dr configure <RecoverySecondaryTSPSHostName>
   3. Stop the Presentation Server by running this command: tssh server stop
   4. Edit the pg_hba.conf file located at the following location.
      
      • Windows: %TRUESIGHTPSERVER_HOME%\truesightpserver\data\pgsql\
      • Linux: $TRUESIGHTPSERVER_HOME/truesightpserver/data/pgsql/
   5. In the pg_hba.conf file, add the following properties to provide the primary computer, load balancer, and the database details, and then save the file:
      • hostnossl replication <TSPSDatabaseName> <PrimaryHostName> trust
      • hostnossl replication <TSPSDatabaseName> <LoadBalancerName> trust
   6. Start the Presentation Server by running this command: tssh server start

Synchronizing the primary and recovery sites

To ensure that the primary and recovery sites are in sync, perform the following tasks:

Back up folders regularly

Ensure that you regularly backup the following folders on the primary site and copy it over to the recovery site:

• %TRUESIGHTPSERVER_HOME%\truesightpserver\data
• %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\cma
• %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\elasticsearch\data

On Linux, it is possible to backup the folders while the Presentation Server processes are running. On Windows, do one of the following:

• Use a Windows or third-party utility to backup the folders. Traditional copying while the Presentation Server processes are running might result in an error.
• Stop the Presentation Server processes and then backup the folders.

Apply patches and configuration changes 

If you apply product patches or make changes to configuration files at the primary site, ensure that you do the same at the recovery site.

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 Presentation Server in high-availability and disaster recovery mode 

Next step in the Installation process

Now that you have successfully configured disaster recovery for the Presentation Server, install the other TrueSight components as per your license entitlements. For instructions, see Installation process.