Linux Versions
Just ensure that port 28774 communication is not being blocked on Linux units.
On the EM Server
In EM, browse to the stuck server and click on Data Restore if it is there after making the changes for VFBA.exe or port 28774 (On Linux units).
Below is an example of what the logs will look like if the port is closed… Take note of the PENDING state:
2021-09-20 00:00:42 (GMT+0530) UpdatePI Verbose Starting failback agent: {./vfba -x -start 2021-09-01T11:38:11Z -end 2021-09-01T11:40:28Z -drives C:\ -port 28774}
2021-09-20 00:00:43 (GMT+0530) UpdatePI Verbose Failback agent started, pid=4952. Retrieving port…
2021-09-20 00:00:43 (GMT+0530) UpdatePI Verbose Failback agent started successfully, pid=4952, port=28774
2021-09-20 00:00:43 (GMT+0530) UpdatePI Verbose Emit Failback status: READY (202)
2021-09-20 00:00:48 (GMT+0530) UpdatePI Verbose Received request to stop_agent
2021-09-20 00:00:48 (GMT+0530) UpdatePI Verbose WorkerThread awake action=stop_agent, currentAction=start_agent
2021-09-20 00:00:48 (GMT+0530) UpdatePI Verbose Terminating failback agent process with code 15, pid=4952
2021-09-20 00:00:49 (GMT+0530) UpdatePI Verbose WorkerThread awake action=none, currentAction=stop_agent
2021-09-20 00:00:49 (GMT+0530) UpdatePI Verbose Verifying the failback agent exited
2021-09-20 00:00:49 (GMT+0530) UpdatePI Verbose Failback agent exited. Emit status: FAILBACK_NONE (200)
2021-09-20 00:00:49 (GMT+0530) UpdatePI Verbose Emit Failback status: NONE (200)
2021-09-20 00:00:53 (GMT+0530) UpdatePI Verbose Received request to start_agent
2021-09-20 00:00:53 (GMT+0530) UpdatePI Verbose WorkerThread awake action=start_agent, currentAction=none
2021-09-20 00:00:53 (GMT+0530) UpdatePI Verbose Emit Failback status: PENDING (201)
Below is an example of what the logs will look like if the port is open…
2021-09-21 19:07:15 (GMT+0530) UpdatePI Verbose Emit Failback status: PENDING (201)
2021-09-21 19:07:15 (GMT+0530) UpdatePI Verbose Starting failback agent: {./vfba -x -start 2021-09-21T13:40:28Z -end 2021-09-21T13:42:04Z -drives C:\ -port 28774}
2021-09-21 19:07:15 (GMT+0530) UpdatePI Verbose Failback agent started, pid=7004. Retrieving port…
2021-09-21 19:07:15 (GMT+0530) UpdatePI Verbose Failback agent started successfully, pid=7004, port=28774
2021-09-21 19:07:15 (GMT+0530) UpdatePI Verbose Emit Failback status: READY (202)
In some cases it may be necessary to “whitelist” ExacqVision Enterprise Manager, Server and Client software along with vfba.exe within any used Antivirus configuration.
Additional Information:
- logs may show the following on failover/failback:
list request failed with error 35 or 15. Aborting operation
This indicates an inbound and outbound rule is needed on the spare server on port 28774.Curl 35 error - A problem occurred somewhere in the SSL/TLS handshake. This could be certificates (file formats, paths, permissions), passwords, and others.
Curl 15 error - "An internal failure to lookup the host used for the new connection."