Running a recovery task using a planned migration fails with the error: Unable to find a placeholder datastore for the host/cluster Failed to unregister protected VMs
search cancel

Running a recovery task using a planned migration fails with the error: Unable to find a placeholder datastore for the host/cluster Failed to unregister protected VMs

book

Article ID: 338957

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Symptoms:
  • Running a recovery task fails.
  • You see errors similar to:

    • Unable to find a placeholder datastore for the host/cluster Failed to unregister protected VMs.
    • Prepare Protected Site VMs for Migration Error - Unable to find a placeholder datastore for the host/cluster xxx.xxx.xxx.xxx. Unable to find a placeholder datastore for the host/cluster xxx.xxx.xxx.xxx Failed to unregister protected VMs.


Environment

VMware vCenter Site Recovery Manager 5.0.x

Cause

This issue can occur due to these reasons:
  • Placeholder datastore is not configured in the protected site.
  • A placeholder datastore is not created.
  • SRM is not aware of all the clusters in the production site.
  • The placeholder datastore mapping on either the protected or DR site is not configured.

Resolution

If you have multiple clusters configured with the same placeholder datastore, you can see all clusters listed in the Configured Datastore tab. Ensure that all the clusters are listed in the Placeholder tab. If they are not restart the SRM service and refresh the information.
To resolve this issue, verify and configure the placeholder datastore on the Protected (production) site and the DR site.
To configure placeholder on the Protected or DR site:
  1. Log in to the vCenter Server using the vSphere Client.
  2. Select Site recovery from Solutions and Applications.
  3. Select the Production or Primary Site.
  4. Select the Placeholder datastore tab.
  5. If all clusters are configured with the same placeholder datastore, clusters are not listed in the Placeholder tab:

    • Restart the SRM service.
    • Refresh the vCenter SRM screen

  6. If a production placeholder datastore does not exist, configure a placeholder datastore for the production site as well as the DR site. Both sites need a placeholder datastore. For more information, see Configure a Placeholder Datastore section from the Creating Site Recovery Manager Placeholders and Mappings.


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box

Powered by Wolken Software