SRM SRA discoverDevices Fails: Storage Virtual Machine (SVM) Name Not Found

Products

• VMware Live Recovery

Issue/Introduction

The discoverDevices operation in VMware Site Recovery Manager (SRM) fails with the following explicit error string:

Operation Failed: SRA command 'discoverDevices' failed. Storage Virtual Machine (SVM) name not found in storage system. Please provide valid Storage Virtual Machine (SVM) name.

This issue occurs when SRM attempts to associate replicated NetApp storage devices with vSphere datastores using the Storage Replication Adapter (SRA) for ONTAP Tools for VMware vSphere (OTV). Despite the SRA successfully discovering the devices, SRM fails to correlate them with the mounted datastores in vCenter.

Environment

• VMware Site Recovery Manager (SRM): 8.x, 9.x
• ONTAP Tools for VMware vSphere (OTV): 9.x
• Storage Protocol: NFS

Cause

This failure is caused by a literal, case-sensitive string mismatch between the SRM Array Manager configuration and the vSphere datastore mount parameters.

When SRM correlates replicated storage, it compares the StoragePort ID (returned by the SRA) against the remoteHost (NFS Server) attribute used to mount the datastore on the ESXi host. SRM requires an exact character-for-character match. Correlation will fail if there is any variation in:

• Character Casing: e.g., testhostname.test.org vs. TESTHOSTNAME.TEST.ORG.
• Network Identity: e.g., using an IP address in the Array Manager but an FQDN for the ESXi mount.
• Protocol Discrepancy: A structural difference between how the storage system was added to OTV and the connection parameters supplied in the SRM Array Manager.

Resolution

To resolve this issue, you must align the SRM Array Manager parameters to identically match the ESXi host's mount string.

1. Identify the Mount String: In the vSphere Client, navigate to the Storage view. Select the affected NFS datastore and go to the Configure tab. Under General, note the exact string (FQDN or IP) and character casing used for the NFS Server (remoteHost) attribute.
2. Edit Array Manager: In the Site Recovery Manager interface, navigate to Array Based Replication > Array Managers.
3. Update Connection Parameters: Select the source array manager and edit the connection settings. Modify the NFS IP (or Opaque) fields to match the spelling and casing identified in Step 1 exactly.
4. Verify OTV Configuration: Ensure the storage system was added to ONTAP Tools for VMware vSphere (OTV) using the same identity (FQDN or IP) and casing.
5. Rerun Discovery: Perform a Discover Devices operation for the array pair. SRM should now successfully correlate the devices and populate the replicated datastores list.

Additional Information

For more information on configuring multi-site topologies, refer to the Broadcom technical documentation on Connect the Site Recovery Manager sites in a shared recovery site configuration