How to configure custom replication agent settings when adding a new customer in the ACP

Custom settings for a replication agent when creating a new customer in ACP

Task

When a replication agent is downloaded from the ACP, it is injected with the current network information vital for connecting to the Acura instance and discovering machines for the given customer.  Depending on the actual layout, Acura may be located behind a proxy server or may have a different endpoint IP for each customer. This will require additional configuration, and applying custom settings for the replication agents will be essential for organizing an operational environment.

Solution

Providing custom replication agent settings is available for every new customer that is being added to the ACP. Tick the checkbox next to Use custom replication agent settings to access the following fields.



Alert
Custom agent settings can be modified, but redeploying or changing the settings of already deployed agents may be required.

Replication agent endpoint IP is an IPv4 address or DNS name that will be used by the replication agents to connect, send data, and make REST API calls to Acura.
Replication agent endpoint certificate is required if a proxy server is present between the components to ensure the security of the HTTPS connection. Input should be an SSL certificate in PEM format for the replication endpoint IP (proxy server).
Replication agent endpoint port is the port used by replication agents to send data.
Replication agent logging address is a custom IPv4 address or DNS name for sending logs. Replication agents downloaded for the customer will use this IP as the Logstash IP. This field typically contains the same address as the Replication agent endpoint IP.
Replication agent logging port is the port used by replication agents to send logs. This field typically contains the same address as the Replication agent endpoint port.


    • Related Articles

    • How to change network settings of an Agent in VMware

      Challenge Hystax VMware Agent (HVRAgent) is deployed as a virtual machine to a source ESXi host. It uses DHCP for its single NIC by default. However, these default settings might not work in case the source VMware infrastructure doesn't have DHCP or ...

    • Configuring a new network interface for the Acura instance

      Challenge Use TUI to set up a new network interface. Please refer to the KB article below if you are looking to perform this operation for an Acura (version 4.2 or newer) deployment in VMware: How to change network settings of an Acura instance in ...

    • Enabling debug logging for the Hystax Linux Replication Agent (HLRAgent)

      Task Turn on debug logging to perform advanced troubleshooting of Hystax Linux Replication Agent (HLRAgent) Solution Stop the HLRAgent service with the following command: sudo service hlragent stop Enable debug logs, set the value ...

    • Renaming the cloud agent image in Hystax Acura

      Task Change the name of the cloud agent image Solution "Hystax_CATI" is the default Cloud Agent image name used while we deploy Hystax Acura. Sequence of steps on an already deployed Acura: Rename the Cloud Agent image. Create a new customer, ...

    • Enabling debug logs for the Hystax Windows Replication Agent (HWRAgent)

      Task Turn on debug logging to perform advanced troubleshooting for Hystax Windows Replication Agent (HWRAgent). Solution HWRAgent is running as two separate processes - HWRAgent service and Replication Manager (Repman_x64.exe), so you need to turn on ...