"Invalid or inaccessible datastore." On existing replications/Migrations in vCloud Availability 4.x

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• When creating a new replication, the task fails and you see a similar error:

Invalid or inaccessible datastore.

• In /opt/vmware/h4/replicator/log/replicator.log on the destination Replicator, you see an entry similar to:

com.vmware.vim.binding.hbr.replica.fault.StorageNotAccessible: Error for (datastoreUUID: "########-####-####-####-##########"), (diskId: "H4-########-####-####-####-##########"), 

(flags: on-disk-open): No accessible host for datastore '########-####-####-####-##########'; Code set to: Storage was not accessible.; Failed to find host to establish nfc connection; Failed to open disk, couldn't create NFC session; Set error flag: on-disk-open; Failed to open replica (/vmfs/volumes/########-####-####-####-##########/C4-########-####-####-####-##########/VM_NAME.vmdk); Failed to open active Disk (GroupID=H4-ID) (DiskID=H4ID); Can't create replica state (GroupID=H4-ID) (DiskID=H4ID); Cannot activate group. Loading disks from database (GroupID=H4-ID) ;

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

Cloud Director Availability 4.x

Cause

Unclear to the cause.

Resolution

Confirm that the Datastores are accessible and valid then delete replications with the error and recreate them.