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 process.
Solution
Replacing a faulty config file is necessary.
1) Check the current config at [ProgramData]\Hystax\acura\repman.conf for any visible discrepancies. It might be an empty file if corrupted.
2) Download a new installation package for the Windows replication agent.
This will be a .zip archive containing a .msi installer and the repman.conf file next to it.
3) Stop the hwragent service on the machine and make sure that there are no repman processes running. Terminate the existing ones if present.
4) Replace the old configuration file with the new repman.conf from the archive.
5) Start the hwragent service once again and after a few minutes check whether the machine has become online in ACP.
The machine should have a green circle next to its name to indicate that it is properly discovered.
Related Articles
Replication agent is installed, but the machine doesn't appear in ACP
Challenge A replication agent is installed, but the machine is not discovered in Acura. Solution 1) If a new agent is installed on the machine discovered in Acura before, configuration files from the previous installation might still be in use as ...
Why Windows replication fails with Hystax VMware Replication Agent - quiesce failure
Challenge Replication fails when a Windows machine is being replicated with Hystax VMware Replication Agent with the following error message: "Backup creation failed with code 500, reason: An error occurred while quiescing the virtual machine. See ...
Connectivity check for a machine shown offline in ACP
Challenge A source machine has a replication agent installed but it is shown in an offline state in ACP, although the machine has been properly discovered before. Solution One of the possible ways to check the connection to Acura is to use the telnet ...
VMware agent replication error: "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 ...
Repman process exits unexpectedly indicating a status code in logs
Challenge Repman process, as a part of the internal agent service, fails and exits with a certain status code. Cause After installing an internal agent on your VM, there should be 2 new services running in the background: repman and hlragent/hwragent ...