Disaster recovery considerations

When setting up a disaster recovery (DR) plan for a datacenter, you can plan DR for your BMC TrueSight Capacity Optimization deployment.

Recovered entities

There are two categories of recovered entities, according to how they are identified by the BMC TrueSight Capacity Optimization connectors that discover them:

  • Entities that are recovered at the secondary site using the same identifiers as they had at the primary site: The secondary BMC TrueSight Capacity Optimization deployment can automatically recover these entities.
  • Entities that are recovered at the secondary site using different identifiers: The secondary BMC TrueSight Capacity Optimization deployment recognizes these entities as new entities. You can either manually reconcile these recovered entities, or you can accept these entities as new, which results in a disruption in your analyses and models at the time of the disaster.

Recovering BMC TrueSight Capacity Optimization

This procedure describes how to recover BMC TrueSight Capacity Optimization.

Before you begin

  • Set up a secondary, passive BMC TrueSight Capacity Optimization deployment at the recovery site.
  • Recover the environment from the primary site.

To recover BMC TrueSight Capacity Optimization

  1. Back up the following sets of BMC TrueSight Capacity Optimization data:
    • Data in the data warehouse (DWH): Back up the Oracle database using data storage resources at the recovery site. Plan for recovery using standard Oracle procedures at the recovery site.
    • Data in the shared repository: The shared repository is a single NFS-mounted directory accessible from the BMC TrueSight Capacity Optimization application server. Back up this directory using data storage resources at the recovery site. Plan for recovery as with any file system.
  2. Bring up the secondary BMC TrueSight Capacity Optimization deployment and connect it to the secondary DWH and the secondary repository at the recovery site. When BMC TrueSight Capacity Optimization services are up and running on all BMC TrueSight Capacity Optimization nodes in the secondary BMC TrueSight Capacity Optimization deployment, you can resume Using.
  3. Recover the remote ETL Engine servers. When recovering remote ETL Engine servers, they fall into the following categories, depending on the entities they were managing:
    • If the managed entities were lost in the disaster, then you must recover these entities at the secondary site. For information about recovered entities, see Recovered entities.
    • If the managed entities were not lost in the disaster and the remote ETL Engine Server that was managing them continues to run, the disaster disrupts communication between the remote ETL Engine Server and the primary BMC TrueSight Capacity Optimization deployment. To recover remote ETL Engine Servers in this category, do the following steps:
      1. Shut down the remote ETL Engine Server.
      2. Manually reconfigure the remote ETL Engine Server to connect to the secondary BMC TrueSight Capacity Optimization deployment by using the BMC TrueSight Capacity Optimization installation program to upgrade the remote ETL Engine server. On the Connect with existing BMC TrueSight Capacity Optimization Server page, select WAN Connection, and then type the following information:
        • Data Hub Server Address: Type the address of the Data Hub in the secondary BMC TrueSight Capacity Optimization deployment.
        • Data Hub Port: Type the port of the Data Hub in the secondary BMC TrueSight Capacity Optimization deployment.

Related topic

High availability considerations

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

Comments