How to continue using Acura after changing its public IP address

How to continue using Acura after changing its public IP address

Challenge

Acura requires a new public IP, and the replications should continue working as before.

Solution 

This article covers the process from the start, so skip to #2 if you have already configured a new IP.

#1 To change Acura's public IP:
  1.       Go to ACP and select “Settings” from the menu.
      
  1.       Go to the “Cluster settings” tab. Update the “Hystax Acura Control Panel Public Address” field and save.
      

#2 Now that Acura has a new public IP address, the replication agents on the source machines have to be adjusted accordingly for the replications to continue. 
If you are using an external replication agent, simply download and reinstall it or alternatively update its settings.
  1. Open the instance VM console or establish an SSH connection to the agent. 
  2. Select the “Agent options” menu.
            
  1. Select the “Edit controller addresses” menu.
            
  1. Choose the option “Update all addresses at once”.
            
  1. Enter the controller public IP address and select “OK”.
            
  1. Restart the instance or select “1 Restart agent services” from the “Agent options” menu for the changes to take effect.
There are two ways to update internal agents:
  1. Reinstall the agents. For that, remove the existing replication agents and delete the old config files manually:
  1. For Windows Replication Agent:
C:\ProgramData\Hystax
If you can't see this folder, make sure that hidden files and folders are displayed and delete it. Terminate all repman or WinCBT procceses that might be left running.
After that, download a new agent installer from Acura and install the agent.

  1. For Linux Replication Agent:
sudo rm -rf /etc/hystax
After that, download a new agent installer from Acura and install the agent.

Acura will automatically inject the agent with the valid SSL certificate and IP address before the download.
Alert
If you choose to reinstall the agents, the source machines will require new full replications.
  1. Update agent configs with the new certificate and the new public IP. This can be done in a semi-automatic manner with the help of our script. 
    1. Download the file:
      1. For Windows Replication Agent: hwragent-update-cert-and-ip.cmd
      2. For Linux Replication Agent: hlragent-update-cert-and-ip.sh
    2. Update the certificate: open the file and replace the existing certificate with a valid one.
    3. Launch the script: run the script on the appropriate machine.
    4. Verify replication:
    5. The machines will be detected by Acura, and replication will proceed.
Idea
If you choose to update the config files, the existing replication data will be maintained allowing incremental replications to follow.