Update MC2 Installation on Disaster Recovery Environments

Owned by Pamela Totas (Deactivated)
Last updated: Jun 12, 2024
2 min read

The MC2 Installation may be updated on the Disaster Recovery (DR) Environments by copying some of the configuration files and binaries. 

This document assumes that:

  1. The ORACLE SID (database name) in PROD and DR, as specified in the eagle/cfg/db_connection.ini and as returned by 'select max(name) as DBNAME from v$database', is the same in PROD and DR.

  2. The full path to eagle/estar is the same in PROD and DR.

Some of the configuration files will have to be manually updated.

The following steps should be taken to install MC2 on DR:

  1. Make sure MC2 is not running in DR

  2. Rename the .jar files as .jar.bkp in the following folders in DR:

eagle/estar/tpe/servers/eaglemc2s/*.jar
eagle/estar/tpe/servers/kafkaservice/*.jar

3. Copy from the main environment to DR the following files:

eagle/estar/tpe/servers/eaglemc2s/*.jar
eagle/estar/tpe/servers/eaglemc2s/*.so
eagle/estar/tpe/servers/kafkaservice/*.jar
eagle/estar/tpe/cfg/plugin_mc2.ini
eagle/estar/tpe/cfg/tpeserver.ini
eagle/estar/tpe/cfg/msgservice.ini
eagle/estar/tpe/servers/msgservice/libmc2plugin.so
eagle/estar/tpe/servers/plugins/plugin_mc2.so

4. This initial step may be done on the first installation of MC2 in DR.  It is not necessary on all MC2 upgrades:

Copy the estar/tpe/cfg/kafkaservice/kafka/brokerID file from PROD to DR.

Copy the estar/tpe/cfg/kafkaservice/zookeeper/zoo_XXX/zoo.cfg (ignore any zoo_XXX.bkp.* folders) from PROD to DR. Change the server host names in zoo.cfg in DR, for example:

server.213=inno-a04.eagleinvsys.com:20533:20534
server.212=inno-a03.eagleinvsys.com:20533:20534
server.211=inno-a02.eagleinvsys.com:20533:20534
server.210=inno-a01.eagleinvsys.com:20533:20534

The number after server.### must match the content of the estar/tpe/cfg/kafkaservice/kafka/brokerID file on the server. In the example above, the estar/tpe/cfg/kafkaservice/kafka/brokerID will have 213 in inno-a04.eagleinvsys.com.

Copy the estar/tpe/cfg/eaglemc2s/redis/*.* files from PROD to DR. In the file sentinel.conf, locate the line 'sentinel monitor', for example:

sentinel monitor eglml03 10.80.220.210 20438 3

Change the IP address only to point to one of the servers in DR. The sentinel.conf on all servers in the region should point to only one server, which should be the server with the lowest numeric IP address.

Remove from sentinel.conf all lines after line 

# Generated by CONFIG REWRITE
5. Remove the old content of the following folders in DR (or rename the folders) and copy the new content from the PROD environment:

eagle/estar/tpe/servers/redis/*
eagle/estar/tpe/java
eagle/estar/tpe/pypy
eagle/estar/tpe/3rdparty

Steps 2 to 5 should be executed on every server in the DR environment.

6. The following steps affect shared folders and should be executed in only one of the environments

7. Remove the old content of the following folders or files in DR (or rename the folders) and copy the new content from the PROD environment:

estar/tpe/dynamic/pyrules
estar/tpe/dynamic/metadata/bind
estar/tpe/dynamic/metadata/core
estar/tpe/dynamic/metadata/vendor
estar/tpe/dynamic/metadata/iws
estar/tpe/dynamic/mc2/redis.version
estar/tpe/dynamic/mc2/streamtypes
estar/tpe/dynamic/mc2/eaglejms/*

In Eagle v17R2 environments and later, copy the processguard_custom.xml to DR:

eagle/eaglemgr/config/processguard_custom.xml

In earlier versions of Eagle (13.1.2BK, 2015R2), copy the eagle/eaglemgr/config/processguard.xml to DR.

8. Make sure the starsecurity.ini changes done in PROD to enable MC2 SOAP and REST endpoints are replicated in DR.