Process to migrate existing TrueSight Capacity Optimization(TSCO) environment to new database with minimal data loss

Version 1
    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


    APPLIES TO:

    TSCO 9.X,10.X,11.X and 20.X



    QUESTION:

    How to move existing TSCO environment to a new Oracle instance.

    How to move the data from the existing instance to the new one?

    This needs to be performed by Database Admin, or need an ETL or custom SQL for it? 
     


    ANSWER:

    When migrating TSCO to a new database instance, DBA needs to work on the database instance side.

    DBA needs to create an export copy of the TSCO Database Instance on the new database server (including all users, roles, tables, tablespaces, views, stored procedures, triggers, and all other database objects associated with the TSCO database users (BCO_OWN, BCO_DASH, BCO_REP).  

    Once this is done and the new database instance is up and running,Run the TSCO setup.sh in Reconfigure mode and point TSCO Primary Application Server to the new database instance.  
    https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000032008

    Repeat re-configuration on all the other TSCO servers in the environment.

    Con's for this Activity:

    -The DBA needs to create the copy of the TSCO database instance: the main problem is the downtime during the creation of the copy of the DB and the end of reconfiguration.

    -In this time frame, the ETL will not work and data will not imported in TSCO: this is something that needs to be considered, when TSCO will be up and running on the new DB.

    -Understand if there are data gaps and plan (if needed) a data recovery in order to close these gaps.

    -To avoid data gaps and no data imports,discuss with DBA and see what the downtime will be for the migration.

    -Which ETLs are running in environment?  Is it mostly daily ETLs (like the BPA vis parser ETL) or vCenter Extractor Service ETLs?  The vCenter Extractor Service ETLs are the biggest problem in relation to data loss because there is no recovery execution for them (if the ETL isn't running it isn't importing data).

    -One option is to run a vCenter History Extractor ETL in the new environment to recover whatever data wasn't imported during the migration.

    There are probably two ways to accomplish,what will give varying levels of an exact copy:

       
    1. Import the last full backup into the new database instance. This will result in data loss from the point of the last full backup to the time the copy finishes and you are able to reconfigure TSCO to point to the new database instance.  This could be a significant period (1 to 2 days) of missing data.
    2.  
    3. Import the last full backup plus the incremental backup to the new instance.  This will result in less data loss but I believe is a more involved process on the DBA side.
      

      

     


    Article Number:

    000202356


    Article Type:

    FAQ/Procedural



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