Modify the Primary Data Center for Replication

Before you set up the secondary data center, configure the primary data center for OpenSearch replication across clusters.

OpenSearch, a search and analytics engine embedded in the Omnissa Access virtual appliance, is used for auditing, reports, and directory sync logs.

Prerequisites

You have set up a Omnissa Access cluster in the primary data center.

Procedure

Make these changes in all the nodes in the primary data center cluster.

1. Add the load balancer FQDN of the secondary data center cluster to the /usr/local/horizon/conf/runtime-config.properties file of each node in the primary data center cluster.

   1. Edit the /usr/local/horizon/conf/runtime-config.properties file.

      vi /usr/local/horizon/conf/runtime-config.properties

   2. Add this line to the file:

      analytics.replication.peers=https://LB\_FQDN\_of\_second\_cluster

2. Restart the Omnissa Access service on all the nodes.

   service horizon-workspace restart

3. Verify that the cluster is set up correctly by running the following command on all the nodes in the cluster.

   curl 'http://localhost:9200/_cluster/health?pretty'

   The command, which verifies OpenSearch health, should return a result similar to the following.

   {
     "cluster_name" : "horizon",
     "status" : "green",
     "timed_out" : false,
     "number_of_nodes" : 3,
     "number_of_data_nodes" : 3,
     "discovered_master" : true,
     "active_primary_shards" : 90,
     "active_shards" : 180,
     "relocating_shards" : 0,
     "initializing_shards" : 0,
     "unassigned_shards" : 0,
     "delayed_unassigned_shards" : 0,
     "number_of_pending_tasks" : 0,
     "number_of_in_flight_fetch" : 0,
     "task_max_waiting_in_queue_millis" : 0,
     "active_shards_percent_as_number" : 100.0
   }
   

What to do next

To verify that the cluster in the primary data center is set up correctly, review the dashboard in the console Monitor > Resiliency page .