![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 2205639.1 : MaxRep: Cannot create a Protection Plan after reinstalling the MaxRep Software
In this Document
Created from <SR 3-13571779210> Applies to:Pillar Axiom Replication Engine (MaxRep) - Version 3.0 to 3.0 [Release 3.0]Information in this document applies to any platform. SymptomsAfter reinstalling the MaxRep Software, a Protection Plan cannot be created if the LUNs were previously used prior to the software being reinstalled. Those LUNs will have a blue storage icon. The issue can be verified in the MaxRep User Interface (UI), click "Protect" tab -> click "View Oracle Storage". In the main page under Oracle Storage LUN Explorer check if the LUNs that were previously used by a protection plan have a blue storage icon.
CauseThe FS1-2 stores a record of the MaxRep Appliance GUID in the LUN parameters, after reinstalling the MaxRep software and registering the MaxRep the GUID changes. SolutionThe solution is to clear the Write Splits on the LUNs impacted that show the blue storage icon. In the MaxRep UI navigate to "Settings" tab -> click "Toolkit for MaxRep". In the main page select "Clear Write Splits" and click "Next >>". Then select the LUNs with the blue storage icon to Clear the Write splits. After successfully Clearing the Write splits on the LUNs create the protection plan. References<BUG:25029315> - MAXREP RESYNC DOES NOT WORK AFTER SOFT UPDATE FROM 3.0.2 TO 3.0.3 - 3.0.4Attachments This solution has no attachment |
||||||||||||||||||
|