Replication Paused by System

[Cherry251]

Observed an issue when doing test failovers. The CG status displayed" Paused by System" and the following error was shown: ERROR: One or more links of group CG_TEST are set to replicate snaps and an error occurred in the snap-based replication process. The following errors were received from the storage: Link = TEST_PROD>TEST_Copy, error = [RPC failed at server.  snapset_not_found]

I had to disable and enable CG so that replication continued normally.

What could be the reason? The system is RP with XIO.

[m_makadmeh]

Hello,

Please check KB463933 (EMC Article Number 000463933😞

RecoverPoint/XtremIO: ERROR: [RPC failed at server. snapset_not_found]

Article Content                                                                                                                                                                                                                                                                                                                             

Issue	Replication will stop and go into Error state causing a DRU (Data Replication Unavailable). Consistency Groups replication will go into Error state. RecoverPoint GUI and CLI (get_events_log) will show (events and command get_system_status -n) following: ERROR: One or more links of group <group_name> are set to replicate snaps and an error occurred in the snap-based replication process. The following errors were received from the storage: Link = prod<name> -> copy<name>, error = [RPC failed at server.  snapset_not_found]
Cause	Due to a code bug in RecoverPoint 4.1 SP2 Patch 2 (4.1.2.2), RecoverPoint's snapshot clean-up tool may delete the current working snap causing replication to go into an error state.
Change	Upgrade to RecoverPoint 4.1 SP2 Patch 2 - 4.1.2.2
Resolution	Resolution: EMC engineering is currently investigating this issue in RecoverPoint 4.1.2.2. A permanent fix is still in progress. Contact the EMC Customer Support Center or your service representative for assistance and reference this solution ID.
Notes (Employees and Partners)	Note: For more information, consult Bugzilla defect number 125418, 122249. Bugzilla access is only available to authorized Customer Service Representatives.

[Idan]

Hi,

Indeed this is a known issue which was fixed.

Couple of comments

1) It was fixed at 4.1.2.3 and 4.4

2) If an upgrade is planned, it's highly recommended to go to RP 4.4.1.1 and XtremIO 4.0.4-41 (XtremIO 4.0.2-80 is currently recommended if RP isn't active on that XtremIO array)

Hope that helps,

Idan Kentor

RecoverPoint Corporate Systems Engineering

idan.kentor@emc.com

[Cherry251]

Idan,

We are at RP 4.1 SP2 P3. How come we are still observing this issue? XIO is at 4.0.2-80.

[Idan]

Hi there,

Well, there are two similar errors so it's possible that you're facing the one fixed in 4.4.

To confirm, we'll need to review the logs so I'll recommend opening a SR.

Take a look at my note above on the versions to upgrade to if indeed an upgrade would be planned.

Regards,

Idan

[sd_storage]

Hi Idan, 

This error is also in RP version 5.1 SP2 P1 .

[Idan]

It also depends on the XIOS version. Please raise an SR with support for us to further investigate.

Regards,

Idan

[sd_storage]

Thanks Idan , yes its due to old XIO version .