SRM Array Pairs: Unable to find a matching consistency group

[DH99]

HPE Community:
I'm running Nimble to support VMware and Site Recovery Manager.
I'm reconfiguring my SRM disaster recovery groups after decommissioning some old servers and implementing some new ones.

I can't add a new server to an existing Protection Group, error is "Unable to find a matching consistency group at the remote site for the local consistency group". I've never seen this before. 

This error is in this community once: https://community.hpe.com/t5/array-setup-and-networking/srm-array-pairs-unable-to-find-a-matching-consistency-group/m-p/6981759#M160

Using the recommendations in that page, I confirmed the new volume of the new server is using "unrestricted access" and allows "multiple initiator access" as all of our datastores do. I ran another snapshot and replication with the nsw volume configuration, and get the same results in Site Recovery Manager.

I have also posted in VMware's Community page as well, but wanted to reach out to the HPE Nimble Community, in case I'm missing something in the Nimble configuration.

I'm using HF20's running v6.0.0.500 on both sides.

[Mahesh202]

Hi DH99

I understand that you are encountering an issue with adding a new server to an existing Protection Group in HPE Nimble storage while configuring your SRM disaster recovery groups. The error message you mentioned, "Unable to find a matching consistency group at the remote site for the local consistency group," indicates that there is a mismatch or inconsistency between the local and remote consistency groups.

In this case, it would be beneficial to involve both the HPE Nimble Tech Support and VMware communities for assistance, as the problem could potentially lie in either the Nimble storage configuration or the SRM setup.

To troubleshoot the issue further, I recommend taking the following steps:

Verify SRM Configuration: Double-check your SRM configuration, including the protection groups, consistency groups, and replication settings, to ensure they are correctly configured and aligned with your new server and storage configurations.
Review Replication Status: Confirm that the replication between the local and remote Nimble storage systems functions properly. Check the replication status, replication schedules, and any potential errors or warnings in the Nimble management interface.
Check SRM Compatibility: Ensure that the version of SRM you are using is compatible with the version of Nimble storage you have deployed. Check the compatibility matrices provided by both VMware and HPE to verify the supported combinations.

I would also suggest you have a look at the below link

URL: https://infosight.hpe.com/app/login?logout&redirectTo=/InfoSight/media/kb/active/htr1455131693412.pdf

I hope this helps.!!

Regards
Mahesh.

[DH99 · Accepted solution]

Hi Mahesh -
Thanks for replying. I opened support tickets with VMware and HPE Nimble, and Nimble Tech Support was able to point me in the right direction. I reconfigured a datastore, rescanned my ESX storage, and was able to identify and add the new server to the appropriate VM Protection Group..

Thanks!

D

[Mahesh202]

Hi DH99

That's great to hear that HPE Nimble Tech Support was able to assist you in resolving the issue. Reconfiguring the datastore and rescanning the ESX storage to add the new server to the correct VM Protection Group is a logical step in ensuring proper data protection and integration with the HPE Nimble storage.

If you have any further questions or need assistance with anything else, feel free to ask.

Regards
Mahesh.