Cannot replicate to datastore cluster - The datastore with managed object ID '' was not found

Products

• VMware Live Recovery

Issue/Introduction

After upgrading to version 9.0.1, configuring replication by selecting a datastore cluster fails with the error: "Operation Failed: The datastore with the managed object ID was not found."

Environment

vSphere Replication 9.0.1

Cause

The spec received was pointing to datastore with empty name (not null). This leads to the issue.

hms.log

Failed to configure replication 'GID-xxxx-xxxx-xxxx-xxxx-xxxxxxxxx' with spec: (hms.VcReplicationSpec) {...vms = (hms.VcReplicationVmSpec) [(hms.VcReplicationVmSpec) {configFileLocation = (hms.ExtendedDatastorePath) {datastore = ManagedObjectReference: type = Datastore, value = , serverGuid = null,path = VM_Name,...},...disks = (hms.Disk) [(hms.Disk) {destination = (hms.ExtendedDatastorePath) {datastore = ManagedObjectReference: type = Datastore, value = , serverGuid = null,path = VM_Name,fileName = VM_Name.vmdk,dsCluster = ManagedObjectReference: type = StoragePod, value = group-xxxxx, serverGuid = xxxx-xxx-xxxx-xxxx-xxxxxxxxxx...com.vmware.vim.binding.hms.fault.datastore.DatastoreNotFound: Datastore could not be accessed from any host.at com.vmware.hms.replication.GroupSpecValidator.validateHostVisibilityOnDatastores(GroupSpecValidator.java:1424) ~[hms.jar:?]at com.vmware.hms.replication.GroupSpecValidator.validateVmDatastores(GroupSpecValidator.java:1356) ~[hms.jar:?]at com.vmware.hms.job.impl.PrimaryVc2VcConfigureReplicationWorkflow.validateGroupSpec(PrimaryVc2VcConfigureReplicationWorkflow.java:149) ~[hms.jar:?]at com.vmware.hms.job.impl.ConfigureReplicationPrimaryBaseWorkflow.go(ConfigureReplicationPrimaryBaseWorkflow.java:173) ~[hms.jar:?]

Resolution

• The issue has been addressed in version 9.0.2.
• To resolve the problem, please upgrade to vSphere Replication version 9.0.2.
• Make sure that  ESXi version is compatible with VR 9.0.2

 https://interopmatrix.broadcom.com

 

NOTE: If you still notice the issue after upgrading to vSphere Replication, please contact Broadcom Support