RecoverPoint: Top Services Topics

This document contains the list of Top Services Topics for RecoverPoint, identified by EMC Support as the most trending topics for the month of  October 2019:


It is recommended that you also check for important information such as advisories (ETAs, ESAs), and other key resources on the Support by Product pages on the EMC Online Support portal.


RecoverPoint: full sweep following a change of CG configuration

CG enter full sweep after changing any setting


 

RecoverPoint for Virtual Machines: Splitter process is not starting on ESX host (uncontrollable Splitter)

Uncontrollable Splitter - KDriver is stuck during startup therfore its getting killed after 150 seconds by its watchdog mechanism



RecoverPoint for Virtual Machines: Replication process restarts causing deadlocks

We can see journal volume error and the Deadlock in the Log (Replication)2019/05/14 16:05:10.581



RecoverPoint for Virtual Machines: Journal Corruption - Full Sweep & Journal Loss - Leading to Inconsistency

Due to a known issue, journal corruption can occur, leading to a loss in journal integrity, a full sweep, or data inconsistency on the target LUN



RecoverPoint: Unable to Execute SYMAPI Commands Successfully with VMAX3 Snap Based Replication

The symapi storapid.log file will show log prints similar to:/usr/emc/API/symapi/log/storapid.log  



RecoverPoint Classic : Reboot Regulation due to Assertion failed: false Line 626 File Fetcher_AO_IMPL.cc PID: 19712 Info: Over size element. Logically unreachable.

Replication process crash due to a race condition that occurs at the thread level in the Fetcher component


 

Recoverpoint for Virtual Machine: Unable to protect VM Error This VM cannot be protected because its ESX Cluster cannot be registered

Customer attempt to protect a VM failed on the last step of RP4VM Plugin Protect Wizard



KVSS fails to create bookmark

KVSS fails to create bookmark; the given reason is VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER


 

Snap not replicating after hitting "no RPA can use array manager for array"

CG suddenly stops replicating



RecoverPoint: VMAX V2: Removing a protected VMAX device causes RPA reboot regulation

A VMAX V2 protected devices is removed before its Replication set or Consistency group is removed. This causes the RPAs in reboot regulation




Note: Please click “Follow” at the top right of this screen (when logged in) to receive update notifications.