Page tree
Skip to end of metadata
Go to start of metadata

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

After a disaster, you can configure any other instance of Presentation Server as a recovery server. 

Note

You must ensure that both primary and recovery servers are installed on same platform and using the same ports and operating system locale.

Perform the following steps to configure the recovery TrueSight Presentation Server:

Step 1: Stop the recovery TrueSight Presentation Server

To stop the recovery TrueSight Presentation Server, run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh server stop

Step 2: Copy the configuration files

Using any third-party file synchronization and backup software, copy the following folders from the primary TrueSight Presentation Server to the respective directory of the recovery TrueSight Presentation Server:

On Windows:

  • $TS_HOME\data

  • $TS_HOME\modules\elasticsearch\data
  • $TS_HOME\conf

 

On Linux:

  • $TS_HOME/data
  • $TS_HOME/modules/elasticsearch/data
  • $TS_HOME/conf

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 3: Start the database on the recovery TrueSight Presentation Server

Run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh process start database

Step 4: Modify the host name on the recovery TrueSight Presentation Server

Run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh dr configure <Secondary DNS HostName>

Step 5: Stop the database on the recovery TrueSight Presentation Server

Run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh process stop database

Step 6: Start the recovery TrueSight Presentation Server

Run the following command from the <Presentation Server installation directory>\truesightpserver\bin folder:

tssh server start
Describes how to configure a Presentation Server installation for disaster recovery

 

5 Comments

  1. In case we do the above DR configuration  what will happen to SSO configuration , 

    Will users able to login to Presentation if the SSO in the primary site is down or what will be the configuration for SSO in this case , 

    Do I need to install the separate SSO node in DR and how I will replicate the configuration on SSO.

    Already BMC Customer support has said it that ASSO HA is not supported .

     

    1. I am not sure why you are saying ASSO is not supported with TSOM  - it is as mentioned in other threads that it is.

       

      If anyone in BMC Support says it is not then please refer them back to these articles and myself if needed.

      Load balancer requirements and guidelines for Atrium Single Sign-On high availability

      https://communities.bmc.com/docs/DOC-47196

      There are also FAQ: 000134312and 000138821 that can be used to supplement the ASSO question.

       

      On the DR question I would suggest logging a Support call if not already. As reference in the document on communities there are references to similar questions that may or may not be useful to you.

       

       

       

       

  2. Hi Michael 

    Thanks for your comments 

    I have a response from BMC Customer support on 

    Case: 00359996 - Queries about ASSO HA

    Also the documentation  page 

    Re: Installing BMC Atrium Single Sign-On as a High Availability cluster 

    It is written the same way .

    Customer Support said you install it in HA mode but we wont support .

    "Going forward if you apply ASSO HA and face any issues you will need to prove that the issue occurs on a non HA system before logging a case for ASSO with BMC Support."

    For DR I raised a case , answer was no DR solution available , you may install the node 1 in PROD site A  and node 2 in  DR site for DR scenarios., which in turn is said on another case that it is not supported.

    Regards

    Abhay



  3. Question : When I am setting up Presentation server  DR as per above information , is the configuration of the SSO getting copied on the DR site , 

    Can I install a separate ASSO on  DR and configure the same with DR Presentation server ,

    What will be the issues 

    Any document suggesting the configuration

  4. To Support Disaster Recovery for TSPS, SSO should be install as cluster with LB..We have following properties related to SSO in TSPS and we can point different SSO.

    From TSPS,

    C:\Program Files\BMC Software\TrueSightPServer\truesightpserver\bin>tssh propert
    ies list |findstr sso
    |  bmc.sso.username                                          amadmin
                                                                          |
    |  bmc.sso.password                                          f39/f39/f39/fwAAAAh
    AHIKOCgTqTQAAABDv3P+9UTTwbBBvd8R/3X22AAAAFOQQbQWpAeauPtU8MZ6b/ErQeHCG |
    |  bmc.sso.port                                              8443
                                                                          |
    |  bmc.sso.servername                                        xxx-yyy-000000.bmc.
    com                                                                   |


             
    In case of moving from standalone SSO to Cluster with LB ,Execute the below command to set the SSO Server hostname property
                  
    tssh properties set bmc.sso.servername <LB HostName>
                  
    Similarly the port name change, same command can be used as above.

    Also we may use the same password for the migration and later change the username/password from the Administration-> Atrium SSO page.