You can view the issues in the Health Report for your VMware Site Recovery SDDC. The following tables list the issues, their category, and what you can do to remediate them.

HMS_SITE_ISSUE

Issue Error Remediation
hmsConnectionIssue vSphere Replication Management Server could not establish connection to remote vSphere Replication Management Server at '...:8043' If you do not need the site pairing or the remote site no longer exists, break the pairing. Otherwise, to resolve the issue do the following:
  • Check if the remote site is in healthy status.
  • Check the network and firewalls on both sites.
  • Check the remote vSphere Replication Management Server status.
  • Reconnect the vSphere Replication pairing.
Other Issue N/A A CSSD ticket is created for any new errors. VMware Site Recovery support might contact you if customer action is required.

HMS_REPLICATION_ISSUE

Issue Error Remediation
rpoViolated rpoViolated See the vSphere Replication RPO Violations topic in the vSphere Replication Administration.
replicationNotActive replicationNotActive See the Monitor the Status of a Replication topic in the vSphere Replication Administration.
newDiskAddedIssue A new disk was added to a replicated virtual machine. Replication will be paused until the new disk is configured for replication. See The Replication Pauses When You Add a New Disk to the Source VM topic in the vSphere Replication Administration.
replicationForceStoppedIssue Replication '...' on the source site has been force-stopped. To resolve the issue, perform one of the following actions:
  • Force stop the replications from the target site.
  • If the source VM was deleted by mistake and you must restore the VM, perform a failover by using the Recover action in the Replications tab.
    • Recover action will be greyed out if the VM is part of a Site Recovery Manager Protection group. You must first remove the VM from the Protection group.
    • After the recovery, the VM is restored on the target site. You must force stop the replication from the target site.
replicationForceStoppedIssue Replication '... on the target site has been force-stopped. To resolve the issue, force stop the replications from the source site.
diskFileNameAlreadyExists Unable to complete the reconfiguration task at remote site for replication group ...'. Details: 'Disk file name ....vmdk' already exists.'" ... To resolve the issue, perform one of the following actions:
  • Delete the vmdk file with the file name from the error message at the remote site and perform a Reconfigure operation.
  • Reconfigure the replication, exclude the problematic disk and finish the reconfigure. Reconfigure the replication again, include the problematic disk and select seed, then finish the reconfigure operation.
sessionNotAuthenticated The session is not authenticated. You might observe the error if the disk move task is not complete and the reconfigure session timeouts. Retry reconfigure operation after waiting some time. If the error persists, contact VMware Site Recovery support.
Lock issue The storage for datastore path '[] ....vmdk' is locked. A CSSD ticket is created and VMware Site Recovery support will investigate the issue.
  • Collect log bundles from the on-premises site.
If the error is a result from a broken disk hierarchy, recreate the replication.
  1. Stop the replication with the option to retain the replica disks.
  2. Re-create the replication with seed disks.
  3. Wait for the initial sync to complete.
Other issues A CSSD ticket is created for any new errors. VMware Site Recovery support might contact you if customer action is required.

REPLICATION_FOLDER_ISSUE

Issue Error Remediation
Folder conflict Replication VM <vm_name> which target <vm_folder> is the same as placeholder VM folder <vm_folder> To resolve the issue, perform the following actions:
  1. Delete the placeholder VM from the vCenter Server inventory. This triggers the Missing placeholder VM error in the Site Recovery user interface.
  2. From the Site Recovery user interface, select the Re-create placeholder VM action. A placeholder VM is created in a new directory.

SRM_DATASTORE_CONFIG_ISSUE

Issue Error Remediation
datastore config issue

Cluster managed object ID: domain-c8

Missing configuration for placeholder datastore

 Configure placeholder datastore for the cluster used in the resource pool mapping.

RESOURCE_MAPPING_MISMATCH

Issue Error Remediation
cluster mismatch Replication datastore belongs to cluster Cluster-67-2, but resource mapping cluster is Cluster-67-1. To resolve the issue, perform one of the following actions:
  • Change the datastore of the replication to the resource mapping cluster.
  • Change the resource mapping cluster to the cluster which has the replication datastore.
disk in multi clusters VM disks's datastores do not belong to the same cluster, the clusters are: Cluster-67-2, Cluster-67-1 Change the datastore of all the replication disks to the same cluster.
DataStore not found No datastore is found for VM vmlb1db19p, VM moId vm-8346, replication id GID-a1d8126e-c0e7-4a66-a448-8c68133a9439 on VM disks Check if the datastore exists and change the replication to a valid datastore.
Resource pool not found Resource mapping object is not found for VM vm-29396 Check if the resource pool exists, and change the replication to a valid resource pool.