Bringing up the recovery or primary Presentation Server in high-availability and disaster recovery mode

This section explains the steps you must perform to bring up the recovery or primary Presentation Server after a disaster.

Related topics

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

Bringing up the recovery site Presentation Servers after a disaster

Before you begin, if you applied product patches or made changes to configuration files at the primary site, ensure that you do the same at the recovery site.

Perform the following steps to bring up the recovery site Presentation Servers.

Step 1: Copy the configuration files

If no storage replication system is used, copy the following folders from the primary site, primary Presentation Server or backup location to the recovery site, primary Presentation Server.

On Linux, ensure that you use the same non-root user credentials that was used for installing the Presentation Server.

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


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.

Step 2: Start the database on the recovery site Presentation Server

On both primary and secondary Presentation Servers, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh process start database

Step 3: Verify that the database is running

On both primary and secondary Presentation Servers, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh server status

If the database server fails to start, do the following:

  1. Run following command on the recovery TrueSight Presentation Server:

    cd %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\pgsql\bin
    pg_resetxlog.exe "%TRUESIGHTPSERVER_HOME%\truesightpserver\data\pgsql"
  2. (Optional) You might see the following message:

    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.

    If you see this message, run the following command:

    pg_resetxlog.exe -f "% TRUESIGHTPSERVER_HOME %\truesightpserver\data\pgsql"
  3. Start the database process by running the following command:

    tssh process start database

Step 4: Modify the host name on the recovery site Presentation Servers

On both primary Presentation Server, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh dr configure <Primary DNS HostName>

On the secondary Presentation Server, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh dr configure <Secondary DNS HostName>

Step 5: Update the database replication file (required for 11.3.01 only)

On the primary Presentation Server, edit the %TRUESIGHTPSERVER_HOME%\truesightpserver\data\pgsql\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

Step 6: Start the recovery site Presentation Servers

On both primary and secondary Presentation Servers, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh server start skipHAcheck

Step 7: Synchronize events with Infrastructure Management

On the primary Presentation Server, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder to obtain the component name:

tssh component list

On the primary Presentation Server, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder to synchronize events with Infrastructure Management. Use the component name that you obtained.

tssh event sync {Component Name}


Bringing back the primary site Presentation Servers

Before you begin, if you applied product patches or made changes to configuration files at the recovery site, ensure that you do the same at the primary site.

After you fix the primary site Presentation Servers, you can switch the operations from the recovery site back to the primary site.

Step 1: Copy the configuration files

If no storage replication system is used, copy the following folders from the recovery site, primary Presentation Server or backup location to the primary site, primary Presentation Server.

On Linux, ensure that you use the same non-root user credentials that was used for installing the Presentation Server.

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


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.

Step 2: Start the database on the primary site Presentation Server

On both primary and secondary Presentation Servers, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh process start database

Step 3: Verify that the database is running

On both primary and secondary Presentation Servers, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh server status

If the database server fails to start, do the following:

  1. Run following command on the recovery TrueSight Presentation Server:

    cd %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\pgsql\bin
    pg_resetxlog.exe "%TRUESIGHTPSERVER_HOME%\truesightpserver\data\pgsql"
  2. (Optional) You might see the following message:

    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.

    If you see this message, run the following command:

    pg_resetxlog.exe -f "% TRUESIGHTPSERVER_HOME %\truesightpserver\data\pgsql"
  3. Start the database process by running the following command:

    tssh process start database

Step 4: Modify the host name on the primary site Presentation Servers

On the primary Presentation Server, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh dr configure <Primary DNS HostName>

On the secondary Presentation Server, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh dr configure <Secondary DNS HostName>

Step 5: Update the pg_hba file (required for 11.3.01 only)

On the primary Presentation Server, edit the %TRUESIGHTPSERVER_HOME%\truesightpserver\data\pgsql\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


Step 6: Start the primary site Presentation Servers

On both primary and secondary Presentation Servers, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh server start skipHAcheck

Step 7: Synchronize events with Infrastructure Management

On the primary Presentation Server, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder to obtain the component name:

tssh component list

On the primary Presentation Server, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder to synchronize events with Infrastructure Management. Use the component name that you obtained.

tssh event sync {Component Name}

Was this page helpful? Yes No Submitting... Thank you

Comments