iSCSI connection issue occurs when using a VirtIO network device

Details

An iSCSI connection issue has been confirmed when a virtual guest running ActiveImage Protector uses a VirtIO (paravirtualized) network device. 

 Affected features:

• HyperBack (KVM/Proxmox backup source)
• HyperRecovery (KVM/Proxmox recovery target)
• vStandby (KVM/Proxmox standby replica target)
• HyperStandby (KVM/Proxmox target host)
• Virtualization (Linux KVM/Proxmox target host)
• Virtualization adapter (KVM/Proxmox hypervisor)
• Image Target Server (Hyper-V iSCSI target creation)

Symptoms:
During task start or execution, the iSCSI-connected device may disconnect, causing the job to fail.

Example:
HyperRecovery task failure may appear in the task log:
AIP install path\logs\VMRestore\QUICKSHOT_RESTORE_AGENTLESS_Quick_XXXX\XXXXXXXXX.log

05/29/2026 03:20:22.393 Restore_WriteVolume: WriteFile(3E4,6521159680 ,33554432,) error(433)
05/29/2026 03:20:22.393 ##### Pipe line encounter ERROR: 105, last error code:433, 99505 Level = ERROR[0]
...
05/29/2026 03:20:52.225 {IDS_STRING3018}Exit Code: -701

This issue occurs during iSCSI connections and is not specific to our product. As a result, we are unable to provide a fix.

Workaround

Please change the virtual guest’s network device from VirtIO to E1000 and try the feature again.

If the issue causes the hypervisor Web UI to become inaccessible, you can restore access by restarting the network service from the hypervisor console (e.g., Proxmox). 

systemctl restart networking

Target Product

- ActiveImage Protector 2022

58527930022937