Unable to edit a "Not configured" protection group with "Operation Error: Mapping for resourcePool 'Resource Name' missing in resource mappings"

Products

• VMware Site Recovery Manager 8.x
• VMware Live Recovery

Issue/Introduction

• An existing consistency group is updated with adding replicated LUNs and datastores are added to an existing datastore group accordingly. 
• An existing array-based replication protection group with the datastore group gets status changed to "Not configured". 
• Unable to edit the protection group. 
• The performed edit operation fails with the following error:  
  
Operation Error: Mapping for resourcePool '<Resource Name>' missing in resource mappings". 
  
  
  
  
• There are resource pool mappings for virtual machines deployed on replicated datastores. 
• The existing protection group was created on SRM 8.3.0 or earlier. 

Environment

VMware Site Recovery Manager 8.x
VMware Live Site Recovery

Cause

VLSR / SRM checks at least one parent resource pool mapping of replicated datastore exists.
Otherwise, editing array-based replication port group fails with the resource pool mapping missing error.
This behavior change was introduced since SRM 8.3.1. 

Therefore, editing an array-based replication protection group created on SRM 8.3.0 or earlier with resource pool mapping(s) will encounter the resource pool mapping missing error.

Resolution

Create a parent resource pool mapping as a cluster mapping and then edit the protection group. 

Additional Information

Create Array-Based Replication Protection Groups
Unable to create a protection group with "Operation Error: Mapping for resourcePool '<Resource Name>' missing in resource mappings"