Symptoms
When attempting to create a new replication, the task fails and you see an error similar to:
Invalid or inaccessible datastore.
In the /opt/vmware/h4/cloud/log/cloud.log file on the destination Cloud Replication Management Appliance, you see messages similar to:
2022-11-18 15:32:55.420 DEBUG - [UI-e2ac62b3-bf63-4f60-aa9a-86f797e351a4-r111-Qt-2K] [job-43] c.v.h.c.s.DatastoreManagementService : Unable to find datastore aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee2022-11-18 15:32:55.420 ERROR - [UI-e2ac62b3-bf63-4f60-aa9a-86f797e351a4-r111-Qt-2K] [job-43] com.vmware.h4.jobengine.JobExecution : Task f6cac164-c639-472b-b8f7-687b2a38352f (WorkflowInfo{type='start', resourceType='vmReplication', resourceId='C4-1be42cc3-8763-4db9-e23e-b5b336e11837', isPrivate=false, resourceName='null'}) has failedcom.vmware.h4.replicator.api.exceptions.DatastoreFault: Invalid or inaccessible datastore...
When you attempt to manually create an independent disk within Cloud Director using the same storage policy, you see two entries in the Cloud Director Tenant Portal.This issue occurs if the replication destination is a Cloud Director site.This issue occurs if the Cloud Director Storage Policy is backed by clustered datastores.
Cause
This issue occurs when a standalone datastore was moved into a storage cluster in the destination Cloud Director site and the record for the standalone datastore was not removed from the Cloud Director database. Thus, the identifier for the individual datastore can be returned to Cloud Director Availability upon creation of the independent disk and subsequent calls to the Cloud Director API for information regarding the datastore return invalid information.
Resolution
In order to correct this behaviour, the original datastore record must be removed from Cloud Director.To confirm and resolve this issue, contact VMware Support, select the version of VMware Cloud Director that is in use, and note this Article ID (90531) in the problem description. For more information, see How to Submit a Support Request.
