RecoverPoint for VMs：目標 VM 在測試或容錯移轉中無法順利運作

Summary: 虛擬機器的 RecoverPoint「測試複本」或「容錯移轉」作業未完全成功。目標虛擬機器 （VM） 客體作業系統無法完全開機或顯示錯誤。 由於記錄輸出，本文是虛擬機器 6.x 專用的 RecoverPoint，但先前的版本中也可能發生類似問題。

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 「 測試複本與 容錯移轉」會帶出 VM 作業系統，讓使用者進行測試。

在此情況下，注意到 Windows 虛擬機器卡在開機迴圈中。VM 主控台會顯示 Windows 標誌，以及連續旋轉的虛線圓圈。

在 vmware.log 在目標虛擬機器中，以下列印可能會顯示連線問題：

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

針對目標網站上的一般複寫狀態，分割器不會將流量傳送至 RecoverPoint 裝置 （RPA）。在測試複本或容錯移轉作業期間，VM 的所有寫入作業都需要 RPA 確認。

網路組態問題造成分割器無法與 RPA 通訊，導致目標虛擬機器寫入失敗，且作業系統無法正確開機。

Resolution

解決 ESXi 主機和 RecoverPoint 裝置之間的網路組態問題。驗證正確 VMkernel 適配器已配置，如果適配器不存在，請添加適配器。

請遵循「 建立 VMkernel 「ports」一節，網址為「 RecoverPoint HTML5 系統管理員指南」第 116 頁。

如需 IP 分割器故障診斷，請參閱文章故障診斷 IP 分割器連線問題。（可能需要以已註冊的 Dell 支援使用者身分登入才能檢視本文。）

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.