MaxRep: Sentinel Resync Required

Asset ID:	1-72-2016718.1
Update Date:	2018-01-22
Keywords:

Solution Type Problem Resolution Sure

Solution 2016718.1 : MaxRep: Sentinel Resync Required

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 3.0 and later
Information in this document applies to any platform.

Symptoms

This type of event is reported in the event log in the GUI, or can be found in the events_summary.txt file within the logs after they are extracted

Example of the Event:

Hostname: TEST-FS1
Product Type: FS1_2
Summary:Sentinel Resync Required

Fault event description: Sentinel resync required
unknownMessage Payload Data:
event-parameter

     callhomeLogName = AK00265557-150527180326-150527180542-PCP_EVT_REPL_SENTINEL_RESYNC_REQUIRED-e-01-02.tar
     ReplicationResyncEvents.ReplicationResyncInfo.dstHostGuid = c20e951c-8833-4b2d-a0fd-562518848090
     ReplicationResyncEvents.ReplicationResyncInfo.srcHostGuid = dedf9864-6f87-4d55-a446-fdd91dc663b0
     ReplicationResyncEvents.ReplicationResyncInfo.amethystGuid = c20e951c-8833-4b2d-a0fd-562518848090
     ReplicationResyncEvents.PMIIpAddress2.Addr46.addr46 = -2006800192, 1409633216, 32609, 24
     ReplicationResyncEvents.PMIIpAddress2.inFamily = AF_INET
     ReplicationResyncEvents.ReplicationResyncInfo.errorMessage = Resync required for replication pair VOLUME1-MAXREP1 [/dev/mapper/36000b08414b30303236353535360000d] -> VOLUME2-MAXREP2 [/dev/mapper/36000b08414b303032363535353700016] for Plan [TEST].
     ReplicationResyncEvents.applianceSerialNumber = 1415NM200N
     ReplicationResyncEvents.ReplicationResyncInfo.dstVolumeGuid = "/dev/mapper/36000b08414b303032363535353700016
     ReplicationResyncEvents.ReplicationResyncInfo.srcVolumeGuid = "/dev/mapper/36000b08414b30303236353535360000d

Cause

There are many reasons why this error is reported.

In this particular case, the retention volume was full.

Solution

1. Manually resync the Protection Plan. In this example, the Plan name is TEST.

Resync required for replication pair VOLUME1-MAXREP1 [/dev/mapper/36000b08414b30303236353535360000d] -> VOLUME2-MAXREP2 [/dev/mapper/36000b08414b303032363535353700016] for Plan [TEST].

2. Two options in regards to the retention volume:

Add another retention LUN to increase the available space for retention data. Some of the existing Protection Plans will have to be deactivated with the "Clean CDP Retention logs" box ticked, and modified to point to the new retention LUN.
Decrease the amount on data being retained by reducing the retention interval or activating sparse retention.

3. If resync'ing the volume does not resolve the issue, please collect a new log bundle and contact Oracle Support.

For further details, please refer to the Oracle MaxRep for SAN Documentation Library, Release 3.0 on the Oracle Help Center Storage Documentation page.

References

<NOTE:2012064.1> - MaxRep: Disk usage on retention folder /retention1 now at X%, alert threshold is configured at Y%

Attachments

This solution has no attachment