Replication freezes although the agent is still sending heartbeats to Acura

Challenge

Replication is stuck with a "Replicating" status in Acura Control Panel, although the agent's "Last seen" status is up-to-date and heartbeats are being sent.

      

Cause

A possible reason for such behavior might be that Acura and Hystax Cloud Agent don't have access to each other, so the replicated data can't be saved to the storage.

Solution

Make sure that Hystax Cloud Agent and Acura are in the same security group.

In case they are in different security groups, check whether the following ports are opened:

• for Acura:
  
• Ingress – tcp/443
  
• Ingress – tcp/4443
  
• Ingress – udp/12201
  

• for Hystax Cloud Agent:
  
• Ingress – tcp/80
  
• Ingress – tcp/3260
  
  
• for the replication agent:
  
• tcp/443
  
• tcp/udp/12201
  

• Related Articles

• How to replace Windows replication agent's config file in case a machine is shown offline in ACP

  Challenge A machine is shown offline in ACP, although the source instance is running and has been replicated successfully before. Cause The replication agent's config file might have become corrupted during an unexpected termination of the repman ...

• Replication agent is installed, but the machine doesn't appear in ACP

  Challenge After a new installation of the replication agent, the machine cannot be protected, however, it was protected in another cloud before that. Cause If a new agent is installed on the machine that has been protected before, configuration files ...

• Replication with VMware agent fails with the message: Backup creation failed with code 500

  Challenge  Replication with VMware agent fails with the following error message: "Backup creation failed with code 500, reason: Command '['umount', '/tmp/e9dc80e9-0a54-4991-9003-edeffd7e4920']' returned non-zero exit status 32" Cause In case of using ...

• Why Acura UI is not available after the deployment

  Challenge Acura UI is not available after the deployment. Cause Certain components of Acura take a longer time to start. Solution Make sure that at least 20 minutes have passed after the initial deployment of Acura as it might take this time for all ...

• "Module build for the currently running kernel was skipped" message in console during Replication agent's installation

  Challenge During the installation of a Linux replication agent (hlragent) with DKMS, the following message can be displayed in the console: Module build for the currently running kernel was skipped since the kernel source for this kernel does not ...