Disaster Recovery Best Practices for TrueSight Capacity Optimization (TSCO)

Version 10
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Capacity Optimization


    COMPONENT:

    Capacity Optimization 11.5.01


    APPLIES TO:

    10.x ,11.x 20.02



    QUESTION:

    Best Practice for the creation of a DR recovery site for TrueSight Capacity Optimization


    ANSWER:

    This are basic guidelines for consideration,when planning and designing of disaster recovery (DR) strategy to support application resiliency.

    - Select appropriate commercial tool that meet organizational requirements to implement the DR strategy.

    Note: These Best Practice are valid only for the TSCO servers.

    For TrueSight Presentation Server (TSPS) and for Remedy Single Sign-on (RSSO) please refer to the products documentation.

    General rule

       1. The hostnames need to be the same in both the environment (production and DR).

    Reason: The hostnames are written in TSCO configuration properties (stored on files or on DB) and the hostname are used in order to communicate internally or with the DB.

    Please refer to this documentation page to understand the communication between the servers
    https://docs.bmc.com/docs/display/btco115/Communication+ports+and+protocols


    2. The main rule for the DR recovery for TSCO,keep in sync the file systems of the TSCO servers and content of the DB instances between the active nodes and the DR ones.

    The idea is making a synchronization at least once a day, but the frequency can be increase according with the size of the data to synchronize and environment performance (network and hardware)

    Quick hints, Divded by server functionality
      

    Application Server (AS)

    For the application server, a sync between the deployment folder of the production server (default /opt/bmc/BCO) with the same path of the DR server is enough. 
    A specific consideration (see after) is for the repository folder  

    Repository

      
       
    • On AS machine: if the FileSystem (FS) is on the Application Server as local folder (shared with other AS), need to synchronize this folder as reported in Application Server paragraph
    •  
    • On a remote folder: if the repository is on a remote folder (like on a NAS), need to create a remove folder in the same way and keep in sync between production and DR
      

    ETL Engine (EE):

       The considerations are the same for the AS. Remember that all the routes to the data sources (e.g. route to the vCenters) need to be opened  

    Database (DB)

        If want to create DB for the DR site, this DB need to be an exact copy of the production one and this DB need to be in sync with the production one. A misalignment between the production and DR database can cause a data gap if there is a node switch.
    Also, some configuration properties are stored in the DB and this is another reason for the need of a synchronization.

    One of this property is the connection string to the database and, for this reason, also the service name need to be the same between production and DR.

      
      

     


    Article Number:

    000330301


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles