RecoverPoint: CGs in error and RPAs down in RecoverPoint systems using same Unity array

摘要: Replication of Consistency Groups failing and RecoverPoint Appliances (RPAs) entering Reboot Regulation on multiple RecoverPoint systems using the same Unity array.

本文适用于 本文不适用于 本文并非针对某种特定的产品。 本文并非包含所有产品版本。
查看其他资源

症状

Replication issues start on multiple RecoverPoint Systems using the same Unity array after creating a new Consistency Group (CG) or adding Journal Volumes on existing CGs.

From System (CLI) Events: 
  Topic:                GROUP
  Scope:                DETAILED
  Level:                ERROR
  Event ID:             4040
  Summary:              Journal error
  More information:     Full sweep to be performed.

  Topic:                GROUP
  Scope:                ADVANCED
  Level:                INFO
  Event ID:             4075
  Summary:              Journal available

  Topic:                GROUP
  Scope:                NORMAL
  Level:                WARNING
  Event ID:             4082
  Summary:              The dirtying action took place either due to a user action (e.g. group was enabled or journal volumes changed) or due to a system fatal error.
  There will be only one full sweep on this link in the next synchronization, regardless of the number of times the link's copies are marked as dirty until the synchronization starts.
  More information:     The copy marked all of its replication volumes as dirty.



From Replication Logs: 
2022/09/07 23:27:48.185 - #0 - 16558/16380 - Stream: errno=0 Assertion failed: false Line 2142 File /home/builderv/ReleaseBuilds/rel-hydra_patch1/src/kashya_infra/stream/Stream.inl PID: 16380 Info: Trying to get head from a stream without open it first
END OF LOGGER

2022/09/07 20:40:31.781 - #0 - 7714/7467 - Stream: errno=0 Assertion failed: false Line 2149 File /home/builderv/ReleaseBuilds/rel-hydra_patch1/src/kashya_infra/stream/Stream.inl PID: 7467 Info: Stream must be recovered or init before get head
END OF LOGGER

2022/09/07 21:39:29.335 - #0 - 13316/12743 - NO TOPIC: errno=0 Assertion failed: 0 Line 89 File SerializableQueueElement.cc PID: 12743 Info: NO INFO
END OF LOGGER

原因

This problem occurs when multiple RPAs from different RecoverPoint systems are writing to the same Journal Volumes.  When this occurs, the Journal history for both CGs becomes corrupted and initiates a full sweep to ensure data consistency. This also triggers the Replication process restarts which lead to Reboot Regulation on the RPAs.

解决方案

Resolution:
Ensure that each Consistency Group contains unique Journal Volumes in all RecoverPoint Systems. (Admin CLI command "get_group_volumes" can be helpful in identifying the Journal volumes used across each system.)

  1. On impacted CGs, navigate to the target copy's Journal tab.
  2. Click "Edit Journals" button, select new Journal Volume to add to the CG and clear the problem Journal Volume.

其他信息

Documented in "Dell EMC RecoverPoint Deploying with Midrange Storage Technical Notes" Page 7 under Limitations:
Unlike VNX, Unity does not have storage groups. Therefore, all volumes are visible to all RPA clusters, including volumes that have already been protected by other RPA clusters. Ensure that you protect only unprotected volumes. If you protect a volume that is already protected:
  • Replication does not start
  • The link state indicates Paused by system
  • An error indicates that the volumes are already protected
  • Data corruption may occur if the selected volume is a journal volume in a different RPA cluster

受影响的产品

RecoverPoint, RecoverPoint CL, RecoverPoint EX, RecoverPoint SE
文章属性
文章编号: 000203635
文章类型: Solution
上次修改时间: 22 9月 2025
版本:  6
从其他戴尔用户那里查找问题的答案
支持服务
检查您的设备是否在支持服务涵盖的范围内。