Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

VMware vCenter Server Site Recovery Manager test failover fails with the error: Unable to recover datastore (1008283)

Details

  • Site Recovery Manager (SRM) test failover fails
  • Cannot perform SRM test failover
  • You see this error:

    Error: Unable to recover datastore
  • The vmware-dr.log file shows an error similar to this:

    [#7]},
    [#7]reason = (vmodl.MethodFault) null,
    [#7]msg = "",
    [#7]}
  • The vmware-dr.log file shows an error similar to:

    [2010-03-22 12:30:54.472 07456 warning 'SecondarySanProvider'] Failed to prepare shadow vm for recovery: (dr.san.fault.RecoveredDatastoreNotFound) {
    [#2]    dynamicType = <unset>,
    [#2]    faultCause = (vmodl.MethodFault) null,
    [#2]    datastore = (dr.vimext.SanProviderDatastoreLocator) {
    [#2]       dynamicType = <unset>,
    [#2]       primaryUrl = "sanfs://vmfs_uuid:4ba32868-c2b59bc2-8e91-0024e82f80a3/",
    [#2]    },
    [#2]    reason = (vmodl.MethodFault) null,[#2]    msg = "",

Solution

This issue might occur under one of these circumstances:

  • The storage array is unable to discover the snapshots of failed-over LUNs during SRM test and recovery.
  • Two instances of the same datastore occur on the Disaster Recovery site. The datastores have the same data, but different names. When you perform a rescan of the HBA on the DR site, one of the datastores disappears.  
To resolve this issue:

Note: This resolution applies only to iSCSI and FC datastores.

  1. Ensure that SRM is configured to see your storage array. For more information, see Site Recovery Manager test failover with iSCSI LUNs fails with the error: failed to recover datastore (1010240).

  2. Some storage arrays require a second rescan to discover the snapshots of failed-over LUNs. To enable an additional rescan:
    • On SRM 4.x, use the Advanced Settings > SanProvider dialog to set the hostRescanRepeatCnt parameter.

    • On SRM 5.0.1, use the Advanced Settings > StorageProvider dialog to set the hostRescanRepeatCnt parameter.

      Note      : The hostRescanRepeatCnt parameter is not available in SRM 5.0. It was introduced in SRM 5.0.1

    • On SRM versions prior to 4.0, edit the vmware-dr.xml file and set the host rescan count value to 2:

      Note: The vmware-dr.xml file is located in these directories depending on the operating system of SRM server. For 64-bit, the location is C:\Program Files(x86)\VMware\VMware Site Recovery Manager\config. For 32-bit, the location is C:\Program Files\VMware\VMware Site Recovery Manager\config.
      1. Open the vmware-dr.xml file using a plain text editor.
      2. Add the <hostRescanRepeatCnt> element within the <SanProvider> element.

        Note: The <hostRescanRepeatCnt> element is available with SRM 1.0 Update 1 and later.

      3. Set the value of <hostRescanRepeatCnt> to 2. For example, the <SanProvider> element must be similar to this:

        <SanProvider>
        .
        .
        <hostRescanRepeatCnt>2</hostRescanRepeatCnt>
        .
        .
        </SanProvider>

      4. Restart the SRM server.
For more information, see:

This Article Replaces

1019839

Update History

06/15/2010 - Updated log entries in Symptoms

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 16 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 16 Ratings
Actions
KB: