Invalid or inaccessible datastore error occurring in VMware Cloud Director Availability

Products

• VMware Live Recovery

Issue/Introduction

• After updates to the lookup service in the cloud site, replications that were previously functional are not synchronizing.
• Attempts to save the replication settings result in the following error:
  
  invalid or inaccessible datastore
  
  
• In the replicator log (/opt/vmware/h4/replicator/log/replicator.log), there are frequent errors when attempting to connect to the vCenter.
• The replicator lookup service configuration is no longer pointing to the local vCenter.

Environment

VMware Cloud Director Availability 4.7.3.x

Cause

The lookup service configuration dictates which local vCenter the replicator uses to manage replications. If a replicator is pointed to the incorrect vCenter, it can no longer manage the replications appropriately and replication traffic can fail.

Resolution

In order to return the configuration to the correct state, complete the following steps:

1. Point the replicator back to the correct vCenter:
   
   
   1. In the UI, adjust the lookup service on the replicator to point to the correct location, as detailed in the document below:
      
      Configure the services to accept the vCenter Server Lookup service certificate and optionally allow SSO
      
      
   2. Re-establish the credentials by repairing the replicator with the local manager, then repair the peer sites as detailed in the following document:
      
      Configure after changing the vCenter SSO credentials
      
      
2. Re-save the replication settings for each replication to force VMware Cloud Director Availability to update the replication in the underlying infrastructure:
   
   
   1. Navigate to the replication and edit the replication settings, as in the following:
      
      Edit replication settings
      
      
   2. Without making any changes to the settings, click APPLY.