ViPR Controller: VMware Site Recovery Manager (SRM) failover fails with Error: "Failed to recover datastore"

Implementation of VMware SRM failover

The user is unable to perform a VMware Site Recovery Manager (SRM) fail-over using RecoverPoint (RP).
VMware SRM sent the fail-over command directly to RP.

VMware Site Recovery Manager (SRM):

4. Create writable storage snapshot    Error - Some virtual machines in the protection group '<protection group>' could not be recovered Failed to recover datastore '<datastore name>'. VMFS volume residing on recovered devices '"<WWN of volume>"' cannot be found. Recovered device '<WWN of volume>' not found after HBA rescan. Failed to recover datastore '<datastore name>'. VMFS volume residing on recovered devices '"<WWN of volume>"' cannot be found. Recovered device '<WWN of volume>' not found after HBA rescan.    2019-02-13 22:05:44 (UTC 0)    2019-02-13 22:06:23 (UTC 0)    00:00:39

4.1. Protection Group <protection group>    Error - Failed to recover datastore '<datastore name>'. VMFS volume residing on recovered devices '"<WWN of volume>"' cannot be found. Recovered device '<WWN of volume>' not found after HBA rescan. Failed to recover datastore '<datastore name>'. VMFS volume residing on recovered devices '"<WWN of volume>"' cannot be found. Recovered device '<WWN of volume>' not found after HBA rescan. Some virtual machines in the protection group 'protection group' could not be recovered

The cause of the issue is that the target LUNs were not exported to the target cluster.

Workaround:

• To facilitate an SRM failover, ensure that the target LUNs must be exported to the target cluster in advance.
• This allows the volumes to be seen by the ESXi hosts during the re-scan.
• This can be accomplished using the "Export Volume to a Host" catalog item in the VIPR Controller.