VPLEX: Mis-aligned RP-enabled Consistency Groups

Summary: How to identify and resolve mis-aligned RecoverPoint consistency groups (CG) from the VPlexcli.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

After running the health check from the VPlexcli, notice the mis-aligned RP-enabled consistency groups:

RecoverPoint:
-------------
Cluster    Total        Unhealthy    Total       Unhealthy   Total        Mis-aligned  Total           Unhealthy
Name       RP Clusters  RP Clusters  Replicated  Replicated  RP-enabled   RP-enabled   Registered      RP Storage
                                     Virtual     Virtual     Consistency  Consistency  RP Initiators/  Views
                                     Volumes     Volumes     Groups       Groups       Storage Views
---------  -----------  -----------  ----------  ----------  -----------  -----------  --------------  ----------
cluster-1  2            0            0           0           23           3            16/2            0

Run the command rp validate-configuration from the VPlexcli in order to obtain the CG names that are mis-aligned. You see the following information indicating an issue with the CG:

Validating that RecoverPoint enabled VPLEX consistency groups are aligned with RecoverPoint consistency groups        ERROR
3 consistency group(s) are not aligned:


         VPlexcli:/> rp validate-configuration         

         3 consistency group(s) are not aligned:
         Test_WIN_CG
         Test_ESX_CG
         Test_SUN_CG
Go to the CG context and then into the RecoverPoint context to view the virtual volumes: 
VPlexcli:/clusters/cluster-1/consistency-groups/Test_WIN_CG> ll

Attributes:
Name                  Value
--------------------  ---------------------------------------------------------
active-clusters       []
cache-mode            synchronous
detach-rule           -
operational-status    [(cluster-1,{ summary:: ok, details:: [] })]
passive-clusters      []
read-only             false
recoverpoint-enabled  true
storage-at-clusters   [cluster-1]
virtual-volumes       [device_VNX1234_ABCDEFGHIJKL_LUN16_272_1_vol,
                      device_VNX1234_ABCDEFGHIJKL_LUN17_272_1_vol,
                      device_VNX1234_ABCDEFGHIJKL_LUN20_272_1_vol]
visibility            [cluster-1]


Contexts:
Name          Description
------------  -----------
advanced      -
recoverpoint  -


VPlexcli:/clusters/cluster-1/consistency-groups/Test_WIN_CG> cd recoverpoint/    <---- go into this context to view the virtual-volumes

VPlexcli:/clusters/cluster-1/consistency-groups/Test_WIN_CG/recoverpoint> ll

Name                               Value
---------------------------------  -----------------------------------------------------------------------------------------------------------------
active-replicating-rp-cluster      []
preferred-cluster                  []
protection-type                    [Remote Replication]
recoverpoint-information           [(device_VNX1234_ABCDEFGHIJKL_LUN16_272_1_vol,TEST_WIN_CG,10.116.93.15,Remote
                                   Replica),
                                   (device_VNX1234_ABCDEFGHIJKL_LUN17_272_1_vol,TEST_WIN_CG,10.116.93.15,Remote
                                   Replica),
                                   (device_VNX1234_ABCDEFGHIJKL_LUN20_272_1_vol,TEST_WIN_CG,10.116.93.15,Remote
                                   Replica),]
vplex-rp-cg-alignment-indications  [Virtual Volumes in this VPlex consistency group exist in different RecoverPoint consistency groups:
                                   OLD_TEST_WIN_CG and TEST_WIN_CG
vplex-rp-cg-alignment-status       error
Notice that the vplex-rp-cg-alignment-indications that the virtual-volume exists in two different CG which is not allowed: 
vplex-rp-cg-alignment-indications  [Virtual Volumes in this VPlex consistency group exists in different RecoverPoint consistency groups:
                                   OLD_TEST_WIN_CG and TEST_WIN_CG.
You may also see the warning: 
'device_CLARiiON1234_LUN8989_1_vol' is not in a RecoverPoint consistency group and is not being protected.

Advise customer to add this device(s) to a RecoverPoint consistency group.

Cause

  • Configuration issue where virtual volumes in a VPLEX consistency group exist in different RecoverPoint consistency groups, or a virtual volume is in a VPLEX CG, but not in a RecoverPoint CG.
  • The VPLEX virtual-volume should only be in one RecoverPoint CG. The user must remove the virtual-volume from the CG on RecoverPoint.
  • For the alignment issue showing that the virtual-volume is in an RP-enabled VPLEX CG, but not in a RecoverPoint CG, the user must put the VPLEX virtual-volume into a RecoverPoint CG, or remove the virtual volume from the VPLEX CG

Resolution

  • Provide this information to the user.
  • Request that the user addresses the CG configuration issue.

Affected Products

VPLEX Series

Products

VPLEX Series, VPLEX VS2
Article Properties
Article Number: 000171216
Article Type: Solution
Last Modified: 02 Jul 2025
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.