Protection group is missing datastore from consistency group 'Test.###.###.###.#####'

Products

• VMware Live Recovery

Issue/Introduction

The datastore spans across two extents corresponding to two different devices.

The newly added extent was not part of the consistency group 'Test.###.###.###.#####'

Environment

VMware Site Recovery Manager 8.0
VMware Live Site Recovery 9.0

Cause

When a datastore spans multiple extents, SRM treats the entire datastore as a single entity within a datastore group.

Since the new extent of the datastore was not a part of the consistency group it shows as not-protected.

If the datastore is not part of a consistency group, it's possible that the VMs on it are not part of a coherent replication group, potentially leading to inconsistencies during recovery.

Resolution

Please contact the storage vendor to make sure the affected LUNs are part of the same consistency group.

Edit the Protection group to verify the devices are detected.

A single datastore spans two extents corresponding to partitions of two different devices.

The two extents must be in a single consistency group and the SRA must report consistency group information from the array in the device discovery stage. 

Additional Information

A Consistency Group is a storage instance which contains one or more LUNs within a storage system.

Consistency Groups are treated as a single entity when they are replicated. That means a single replication session is created for the entire Consistency Group no matter how many LUNs it contains.

The entire group is affected by the operation when pausing or resuming replication on a Consistency Group or adding or removing LUNs.

If this is a protection group based out of storage array replication, this datastore should be part of a consistency group within the storage array to group a specific set of volumes and VMs.

Ensure this datastore has VMs in it and is not part of another protection group.