Replicating a virtual machine fails with the error: VR server localhost.localdom has no hosts through which to access destination datastore

Products

• VMware Live Recovery
• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• You cannot replicate a virtual machine from PROD to DR or vice versa
• vSphere replication fails
• In the hms.log file on the VRMS server at the protected site, you see entries similar to:

ERROR hms.job [hms-jobs-main-thread-21] (..job.impl.ConfigureReplicationPrimaryImpl) | Configure replication failed
com.vmware.vim.binding.hms.fault.datastore.NoSupportedHostsConfigured:
server = localhost.localdom
inherited from com.vmware.vim.binding.hms.fault.datastore.NoSupportedHosts:
datastore = datastore2,
group = TestHDD
inherited from com.vmware.vim.binding.hms.fault.InaccessibleDatastoreFault:

inherited from com.vmware.vim.binding.hms.fault.HmsMethodFault:
originalMessage = null
inherited from com.vmware.vim.binding.hms.fault.datastore.NoSupportedHostsConfigured: VR server localhost.localdom has no hosts through which to access destination datastore 'datastore2' in group 'TestHDD'.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

Environment

VMware vSphere ESXi 5.0
VMware vCenter Server 5.0.x

Cause

This issue occurs if the hosts are incorrectly tagged as Unsupported by the VRMS appliance. This issue occurs due to a HBR generic error at the ESXi level.

Resolution

To resolve this issue:

1. Connect to the VRMS database at the Recovery Site using SQL Management Studio.
2. Right-click the VRMS database and click New Query.
3. Run this query to determine if any hosts are marked as Unsupported:
   
   
   • To query hosts that are not associated with a VR server:
     
     select * from HostEntity h where state=4 and not exists (select * from HbrHostEntity where h.vcMoId=HbrHostEntity.vcHost_vcMoId)
     
     
     
   • To query hosts that are associated with a VR server:
     
     select * from HostEntity h where state=4 and exists (select * from HbrHostEntity where h.vcMoId=HbrHostEntity.vcHost_vcMoId)
     
     
     
   • This query returns a host ID. You can use the vCenter MOB to identify the host using the host ID.

   
   

4. Run this query to perform a cleanup:
   
   

   • To clean up Unsupported records for hosts that are not associated with a VR server:
     
     delete from HostEntity where state=4 and not exists (select * from HbrHostEntity where vcMoId=HbrHostEntity.vcHost_vcMoId)
     

   
   

   • To change the state of hosts that are tagged as Unsupported and associated with a VR server to ACTIVE:
     
     update HostEntity set state=1 where state=4 and exists (select * from HbrHostEntity where vcMoId=HbrHostEntity.vcHost_vcMoId)
     

   
   

5. Restart the VRMS server at the Recovery site.

6. Re-enable HBR for the virtual machine.

Note: The above resolution only applies if the vSphere Replication Appliance is using an external supported database.

For information on the Embedded vSphere Replication Database, see VMware vCenter Site Recovery Manager 5.1 Documentation Center.

Additional Information

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

Impact/Risks:
When you remove the host from the vCenter Server inventory, all host performance graphs and data is lost.