RecoverPoint for VMs: Target VMs Do Not Operate Well in Testing or Failover

Summary: RecoverPoint for Virtual Machines "Test a copy" or "Failover" operations are not fully successful. Target Virtual Machines (VMs) guest operating systems do boot up fully or show errors. This article is specific to RecoverPoint for Virtual Machines 6.x because of the log outputs, but similar issues can occur in previous versions as well. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

RecoverPoint for Virtual Machines operations Test a Copy and Failover bring up the VMs operating system so the user can test them.

In this case, it was noted that Windows VMs were stuck in a boot-up loop. The VM Console shows the Windows logo, and a dotted circle spinning continuously.

In the vmware.log of the target VM, the following prints may show connectivity issues:

2025-08-13T13:26:53.882Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - IfSendIoIofIp_s_SplitComm_write_CB: IO 0xb4f282dff0 to kbox ended with timeout. socket: 0xb537d21550, ip: xx.xx.xx.xx:5042
2025-08-13T13:26:53.882Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - IfSendIoIofIp_s_SplitComm_write_CB: Moving socket state from CONNECTED to CLOSING. socket: 0xb537d21550, ip: xx.xx.xx.xx:5042
2025-08-13T13:26:53.882Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - IfSendIoIofIp_s_send_message_by_params: invalid socket. socket state: CLOSING, socket: 0xb537d21550, ip: xx.xx.xx.xx:5042
2025-08-13T13:26:53.882Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - s_io_send: failed to send message by send params. msgId: 42, socket: 0xb537d21550, ip: xx.xx.xx.xx:5042
2025-08-13T13:26:53.882Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - IoIof_ToKbox_s_send_io: ConnectionBase_io_send failed
2025-08-13T13:26:58.883Z In(05) vthread-61411180 - VTHREAD 779507209984 "vthread-61411180" wid 61411180
2025-08-13T13:26:58.883Z In(05) worker-61410791 - [61410772/2111805184]: RPS:#0 - s_check_connectivity: check connectivity failed, socket state is CLOSING. socket: 0xb537d21550, ip: xx.xx.xx.xx:5042, connType: e_CONNECTION_TYPE_IP_REGULAR
2025-08-13T13:26:58.883Z In(05) worker-61410791 - [61410772/2111805184]: RPS:#0 - PathRpa_s_check_and_log_path: path(0xb537c1cbf0), state(OK), check connectivity failed. Moving path to SPL_PATH_TO_DISCONNECT
...
2025-08-13T13:29:33.891Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - IfSendIoIofIp_s_SplitComm_write_CB: IO 0xb4f282f580 to kbox ended with timeout. socket: 0xb537e34ac0, ip: xx.xx.xx.xx:5042
2025-08-13T13:29:33.891Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - IfSendIoIofIp_s_SplitComm_write_CB: Moving socket state from CONNECTED to CLOSING. socket: 0xb537e34ac0, ip: xx.xx.xx.xx:5042
2025-08-13T13:29:33.891Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - IfSendIoIofIp_s_SplitComm_write_CB: IO 0xb4f282fcb0 to kbox ended with timeout. socket: 0xb537e34ac0, ip: xx.xx.xx.xx:5042
2025-08-13T13:29:33.891Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - IfSendIoIofIp_s_SplitComm_write_CB: IO 0xb4f282f130 to kbox ended with timeout. socket: 0xb537e34ac0, ip: xx.xx.xx.xx:5042
2025-08-13T13:29:33.891Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - IfSendIoIofIp_s_SplitComm_write_CB: IO 0xb4f282ece0 to kbox ended with timeout. socket: 0xb537e34ac0, ip: xx.xx.xx.xx:5042
2025-08-13T13:29:33.891Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - IfSendIoIofIp_s_send_message_by_params: invalid socket. socket state: CLOSING, socket: 0xb537e34ac0, ip: xx.xx.xx.xx:5042
2025-08-13T13:29:33.891Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - s_io_send: failed to send message by send params. msgId: 105, socket: 0xb537e34ac0, ip: xx.xx.xx.xx:5042
2025-08-13T13:29:33.891Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - IoIof_ToKbox_s_send_io: ConnectionBase_io_send failed
2025-08-13T13:29:38.892Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - s_check_connectivity: check connectivity failed, socket state is CLOSING. socket: 0xb537e34ac0, ip: xx.xx.xx.xx:5042, connType: e_CONNECTION_TYPE_IP_REGULAR
2025-08-13T13:29:38.892Z In(05) worker-61410848 - [61410772/2113926912]: RPS:#0 - IfSendIoIofIp_s_send_message_by_params: invalid socket. socket state: CLOSING, socket: 0xb537e34ac0, ip: xx.xx.xx.xx:5042
2025-08-13T13:29:38.892Z In(05) worker-61410848 - [61410772/2113926912]: RPS:#0 - s_io_send: failed to send message by send params. msgId: 106, socket: 0xb537e34ac0, ip: xx.xx.xx.xx:5042
2025-08-13T13:29:38.892Z In(05) worker-61410924 - [61410772/2116028160]: RPS:#0 - PathRpa_s_check_and_log_path: path(0xb537c1c7d0), state(OK), check connectivity failed. Moving path to SPL_PATH_TO_DISCONNECT
2025-08-13T13:29:38.892Z In(05) worker-61410848 - [61410772/2113926912]: RPS:#0 - IoIof_ToKbox_s_send_io: ConnectionBase_io_send failed
2025-08-13T13:30:03.893Z In(05) worker-61410848 - [61410772/2113926912]: RPS:#0 - s_trigger_refresh_kboxes_locked: Failed to create CommandRefreshKboxes
2025-08-13T13:30:07.071Z In(05) vmx - GuestRpcSendTimedOut: message to toolbox timed out.
2025-08-13T13:30:33.896Z In(05) worker-61410791 - [61410772/2111805184]: RPS:#0 - IfSendIoIofIp_s_SplitComm_write_CB: IO 0xb4f282fb40 to kbox ended with timeout. socket: 0xb537e21d60, ip: xx.xx.xx.xx:5042
2025-08-13T13:30:33.896Z In(05) worker-61410791 - [61410772/2111805184]: RPS:#0 - IfSendIoIofIp_s_SplitComm_write_CB: Moving socket state from CONNECTED to CLOSING. socket: 0xb537e21d60, ip: xx.xx.xx.xx:5042
2025-08-13T13:30:33.896Z In(05) worker-61410791 - [61410772/2111805184]: RPS:#0 - IfSendIoIofIp_s_SplitComm_write_CB: IO 0xb4f282f410 to kbox ended with timeout. socket: 0xb537e21d60, ip: xx.xx.xx.xx:5042
2025-08-13T13:30:33.896Z In(05) worker-61410791 - [61410772/2111805184]: RPS:#0 - IfSendIoIofIp_s_SplitComm_write_CB: IO 0xb4f282f2a0 to kbox ended with timeout. socket: 0xb537e21d60, ip: xx.xx.xx.xx:5042
2025-08-13T13:30:33.896Z In(05) worker-61410791 - [61410772/2111805184]: RPS:#0 - IfSendIoIofIp_s_send_message_by_params: invalid socket. socket state: CLOSING, socket: 0xb537e21d60, ip: xx.xx.xx.xx:5042
2025-08-13T13:30:33.896Z In(05) worker-61410791 - [61410772/2111805184]: RPS:#0 - s_io_send: failed to send message by send params. msgId: 126, socket: 0xb537e21d60, ip: xx.xx.xx.xx:5042
2025-08-13T13:30:33.896Z In(05) worker-61410791 - [61410772/2111805184]: RPS:#0 - IoIof_ToKbox_s_send_io: ConnectionBase_io_send failed

Cause

For normal replication state on the target site, the splitter does not send traffic to the RecoverPoint Appliances (RPAs). During Test a Copy or Failover operations, all the write operations from the VMs require acknowledgment from the RPAs.

A network configuration issue is preventing the splitter to RPA communications, causing the target VM writes to fail and the OS to not boot up correctly.

Resolution

Resolve the network configuration issues between the ESXi hosts and the RecoverPoint Appliances. Validate correct VMkernel Adapters are configured, and if they do not exist, add them.

Follow the "Creating VMkernel ports" section on page 116 of the RecoverPoint HTML5 Administrator's Guide.

For IP Splitter troubleshooting, see article Troubleshooting IP Splitter connectivity issues. (Login as a registered Dell Support user may be required to view this article.)

Affected Products

RecoverPoint
Article Properties
Article Number: 000359255
Article Type: Solution
Last Modified: 04 Dec 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.