Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-79-1531140.1
Update Date:2015-01-18
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  1531140.1 :   Pillar Axiom: MaxRep PCP_EVT_REPL_INSUFFICIENT_RETENTION_SPACE  


Related Items
  • Pillar Axiom Replication Engine (MaxRep)
  •  
  • Pillar Axiom Volume Replicator Appliance
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Axiom>SN-DK: MaxRep-2x
  •  




In this Document
Purpose
Details
 Purpose
 Troubleshooting Steps


Applies to:

Pillar Axiom Volume Replicator Appliance - Version Not Applicable and later
Pillar Axiom Replication Engine (MaxRep) - Version 2.0 to 2.0 [Release 2.0]
Information in this document applies to any platform.

Purpose

 Provide steps for system administrators to resolve PCP_EVT_REPL_INSUFFICIENT_RETENTION_SPACE events.

If you still have questions after reading this article,  go to the  My Oracle Support Community - Pillar Axiom Storage System

Details

Purpose

Event PCP_EVT_REPL_INSUFFICIENT_RETENTION_SPACE is an indication that the MaxRep replication engine has reached its limit for the maximum amount of data that can be stored on the retention LUN on the target MaxRep engine for a particular protection plan. Replicated data gets stored in the retention LUN to allow for the MaxRep engine to rollback the target LUN to historic points in time if necessary. All of this historic data gets stored in the retention LUN of MaxRep engine at the target location of the replication pair. Depending upon the length of time the historic data is maintained, and the change rate of the source LUN in a replication pair, the amount of data stored on the retention LUN can be quite large. A MaxRep can reach its retention space limit for two reasons:

  1. A protection plan has reached is allowable limit of retained data as defined in the protection plan creation process.
  2. The retention LUN has reached its maximum capacity.

Troubleshooting Steps

  1. Log into the MaxRep Engine UI
  2. Select the “Monitor” tab and select the protection plan on “Protection Health” window.
  3. In the “Disks/Volumes/LUNs Replication” table, select “Details.”
  4. Review the Retention Settings “Disk Space Threshold” percentage.
  5. If the percentage listed is at or near 100%, the fault is valid. If the fault is valid, proceed to options below.  If the “Capacity Utilization” is significantly less than 100%, then the fault is NOT valid. If the fault is not valid, lease contact the TSC.

If the fault is valid there are three options to resolve the issue:

  1. Modify the retention settings for the Protection Plan to retain data for a shorter period of time or increase the allowable retention amount.
  2. Modify the retention settings for the protection plan to utilize sparse bookmarks in order to reduce the amount of data being stored on the retention LUN. See the MaxRep User’s Guide for additional information on the proper utilization of MaxRep sparse bookmarks feature.
  3. Add additional retention LUN space.If you wish to increase the retention LUN space available for protection plans to utilize, follow the steps listed below to promote the DraftSR into a formal Service Request.

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback