RecoverPoint/SRM: Failover or Test Failover operations fail with volume/VMFS not found errors

Summary: Site Recovery Manager(SRM) failover or test failover fails with errors "Cannot find VMFS volume for datastore" or similar Volume/VMFS not found.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Attempt to Failover or run Site Recovery Manager(SRM) test Failover.

SRM Failover or Test failover fails due to volumes/VMFS not found.

Example errors in SRM logs:
  
2017-05-21T14:20:53.757+03:00 [53540 error 'AbrRecoveryEngine' opID=773f5494:dd26:ffe2] Dr::Providers::Abr::AbrRecoveryEngine::RecoverVmfsDatastore: Cannot find VMFS volume for datastore 'ds:///vmfs/volumes/57c9acfd-5ead583e-ada6-0017a477xxxx/': (dr.storageProvider.VmfsRecoverySpec) {


2017-05-21T14:20:53.761+03:00 [193968 verbose 'AbrRecoveryEngine' opID=773f5494:dd26:ffe2] FailDeviceGroups: Failing group
2017-05-21T14:20:53.761+03:00 [193968 verbose 'AbrRecoveryEngine' opID=773f5494:dd26:ffe2] GroupCallbackHandler::FailGroup: Failing group 'vm-protection-group-xxxxxx'
2017-05-21T14:20:53.761+03:00 [193968 verbose 'Replication' opID=773f5494:dd26:ffe2] Dr::Replication::EntityOperationJoinerBase<class Dr::TypedMoRef<class Dr::Replication::ProtectionGroup,void>,void>::EntityFailed: Received a failure update for protection group Id=[dr.replication.VmProtectionGroup:bcf4f9b1-2063-4d9a-b773-93be06xxxxxx:vm-protection-group-xxxxxx], error=
--> (dr.storageProvider.fault.DatastoreRecoveryFailed) {
-->    faultCause = (dr.storageProvider.fault.RecoveryVmfsVolumeNotFound) {
-->       faultCause = (dr.storageProvider.fault.RecoveryDeviceNotFound) {
-->          faultCause = (vmodl.MethodFault) null, 
-->          device = "60:06:01:60:0C:F0:3D:00:0E:29:21:28:xx:xx:xx:xx", 
-->          msg = ""
-->       }, 
-->       device = (string) [
-->          "60:06:01:60:0C:F0:3D:00:0E:29:21:28:x:xx:xx:x"
-->       ], 
-->       msg = ""
-->    }, 
-->    protectedName = "General", 
-->    protectedUrl = "ds:///vmfs/volumes/57c9acfd-5ead583e-ada6-0017a4770xxx/", 
-->    msg = ""
--> }



Manually mounting the target devices without SRM appears to work.

Cause

In some scenarios, the time it takes the devices to be seen on the ESXi nodes is longer than the default Timeout.
This issue requires a second scan, or a delay prior to the scan.

Resolution

Resolution:

Change the ESXi/SRM parameters for Storage discovery.
These can be changed to different numbers, depending on the environment. Larger environments with more LUNs or ESXi hosts may require longer Timeouts, retries or delays.

  1. Open the vSphere Web client.
  2. Right-click the SRM site that you want to modify and select Advanced Settings.
  3. Click StorageProvider.
  4. Check/Edit parameters:
    • storageProvider.hostRescanDelaySec - Default is 0, Attempt changing to a number between 20 and 180
    • storageProvider.hostRescanRepeatCnt - Default is 1, Attempt changing to a number between 2 and 3
    • storage.commandTimeout - Default is 300, Attempt increasing to 600 or 900

Similar information can be found in Broadcom articles, for example KB 383166.

Affected Products

RecoverPoint, RecoverPoint CL, RecoverPoint EX

Products

RecoverPoint SE
Article Properties
Article Number: 000065070
Article Type: Solution
Last Modified: 09 Oct 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.