HAA Active Active Setup

News Knowledge Base
1

How to setup HAA Active Active (2 Geo locations)?

  1. Installation of HA Add-On Software: Execute the below commands
  1. Create HA Add-On Cluster
  • In the web browser on the host machine, go to https://localhost:8443 to see the HAA Software web console
  • Note: Depending on the browser used, a certificate error might be seen. But a safe continuation to the web console is possible
  • Click Setup to start the node configuration steps
  • In the Node Configuration settings, enter a cluster FQDN such as cluster.local. Then click Next button
  • Enter the license key, if there is one. If not, click the Next button to use the trial version
  • Click OK to acknowledge the replacement of the HTTPS SSL/TLS certificate on the node and proceed through the browser warning
  1. Add Remaining Nodes to HA Add-On Cluster
  2. Once the clusters have been created, follow these steps to join any additional nodes
  3. Repeat Install HA Add-On Software on each node in the cluster
  • Navigate to the RS management UI using the address: https://:8443 . For example, if the node is installed on a machine with the 10.10.25.192 IP address, navigate to https://10.10.25.192:8443
  • Click Setup. The Node Configuration page appears
  • Open the Cluster Configuration tab and
    • select the Join cluster radio button
    • in the IP address of a node in the cluster field, enter the IP address of any node in the cluster
    • in the Verify cluster admin credentials fields, enter the email and password used when creating the cluster
  • Click Next. The node is added to the cluster and the management UI appears
  • Repeat Steps for HAA cluster in the Second Data Center/Site
  1. DNS Configuration for HA Add-On (Windows DNS Server): The cluster name will be a prefix of an existing zone in DNS. For example, if the existing zone is example.com, the cluster name would be redislabscluster.example.com

The steps to create the DNS setting are as follows,

  1. Create the delegation
  • Right-click on the higher-level zone (example.com), and create a New Delegation
  • In the New Delegation Wizard, the Delegated Domain Name would be redislabscluster (in this example)
  • Add a new Name Server with Add…
  • In the Server FQDN field, enter the IP address of node1 and click Resolve. This is OK for now; it can be changed later
  1. Create the IP address records for the nodes in the cluster in the higher-level zone
  • Right-click on the higher-level zone (example.com), and select New Host (A or AAAA)...
  • Name field would be node1.redislabscluster in this example (note: not fully qualified). Also enter the IP address for node1. Each node will be defined by the node number and IP that appear in the Redis Labs “rladmin status” command line utility
  • Repeat for node2 and node3, creating their A records as well
  1. Configure the NS record
  2. Click on the delegated zone, and right-click on the Name Server record to get its properties
  • Click Edit… and type the FQDN for node1 in the Server FQDN field, node1.redislabscluster.example.com (in this example)
  • Click Resolve, then click OK, then click Apply. If asked to delete the old glue record (the one with the IP address only), click Yes
  • Repeat the process for node2 and node3 by clicking Add and adding the FQDN for node2 and node3 in the Name Server Record
  1. Refresh the zone
  • Note for Win 2008 DNS Manager: The A records may disappear from the DNS Manager GUI once the zone is refreshed. In case troubleshooting is required, check C:\Windows\System32\dns\ to verify that the A-records and NS records exist
  1. It may take a few minutes, but once the DNS change is propagated, it should be possible to ping each node and the newly created database by FQDN
  2. Joining HA Add-on Clusters
  • After logging in to cluster1.local, select the Redis database and deployment type Geo-Distributed. Then click Next
  • In create database, click the show advanced option and
    • For the database name, enter: database1
    • For the endpoint port number, enter: 12000
    • In the participating clusters list, add the address and admin credentials for
  • In the Database clustering option
    • Clear the Database clustering option to use only one shard so that the Multi-key commands limitations do not apply.
  • Note: Enabling or disabling database clustering after the CRDB is created is not possible.
  • Click Activate to create the CRDB.
  • After the CRDB is created, cluster 1 can be visited at https://localhost:8443 and cluster 2 at https://localhost:8445.
  • Make sure that each cluster has a CRDB member database with the name database1.
1 Like