RecoverPoint for VMs: Groups in error or paused by system state.

Summary: RecoverPoint for Virtual Machines Consistency Groups(CG) are in a paused by system or error state.

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.

Symptoms

Control logs show stale entries of a few hosts which Virtual Machines(VMs) is no longer running on.
 
Log References as follows:
2025/08/20 20:44:33.516 - #2 - 14607/13941 - LogCollector-LC: Log collector entry(1787-1):
Log collector entry(1787-1): TS Finished computing BestBoxReasons. GroupCopy(1209606866 SiteUID(0x5839d555d073078e) 0) Copies are not linked - cannot transferLog collector entry(1787-1): TS Finished computing distTarget. distTargetStateID=DIST_TARGET_LOCKED(problematicHDLCs= (badHDLCs=[(hostID=ESX_IOFILTER 0x1534eff53fbb5e36,gUDeviceID=0x5c81425d6f37bb49)=>(state=HDLC_UNAVAILABLE_DIRTY, reason=Splitter may be writing directly to storage without splitting to All RPAs),(hostID=ESX_IOFILTER 0x1534eff53fbb5e36,gUDeviceID=0x88b9f8def54f9748)=>(state=HDLC_UNAVAILABLE_DIRTY, reason=Splitter may be writing directly to storage without splitting to All RPAs),(hostID=ESX_IOFILTER 0x1587a16205e56833,gUDeviceID=0x5c81425d6f37bb49)=>(state=HDLC_UNAVAILABLE_DIRTY, reason=Splitter may be writing directly to storage without splitting to All RPAs),(hostID=ESX_IOFILTER 0x15a785f29b0a12be,gUDeviceID=0x5c81425d6f37bb49)=>(state=HDLC_UNAVAILABLE_DIRTY, reason=Splitter may be writing directly to storage without splitting to All RPAs),(hostID=ESX_IOFILTER 0x15a785f29b0a12be,gUDeviceID=0x88b9f8def54f9748)=>(state=HDLC_UNAVAILABLE_DIRTY, reason=Splitter may be writing directly to storage without splitting to All RPAs)],badStatesCached=VectorSet(HDLC_UNAVAILABLE_DIRTY)),bViolentlyClose= 0,bWithHistory= 0) Reason=side defined as source SiteUID(0x5839d555d073078e)6. Affected versions: RP4VM 6.x.

Cause

Control has stale entry of few hosts on which the Virtual Machine(VM) was no longer running. The stale entry is due to vMotion operations. 
During the vMotion operation, the VM-related information has been cleaned from the volume_info_t data structure.
While cleaning this data structure, there is a condition to check the volume state which has to be in detaching mode. 
Since it is not in a detaching mode, the clean-up would be skipped. 
Due to this stale entry on control the transfer, the state was stuck in a closed state. 
Since transfer state could not reset to open, the pipe could not open between the cluster causing the group to remain in pause by system state.

Resolution

Workaround:

  1. Restart the splitter of the host for which there were stale entries in the control log.
  2. Disable the snapshots on the protected virtual machines.


Resolution:
The issue is addressed in RecoverPoint for Virtual Machines 6.0.3.1(6.0 SP3 Patch1).
To determine whether an upgrade is appropriate for your environment, contact the Dell Technologies Customer Support Center or your service representative and reference this solution ID.

Videos


Affected Products

RecoverPoint, RecoverPoint for Virtual Machines
Article Properties
Article Number: 000382058
Article Type: Solution
Last Modified: 19 يناير 2026
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.