After deploying or upgrading to a new version of VMware Live Recovery, the vCenter Server "Recent Tasks" pane is inundated with "Register vSphere Replication Server" tasks that fail repeatedly. This occurs even when replication is not in use or intended for the environment.
Symptoms include:
High frequency of failed registration tasks in vCenter with message "Register vSphere Replication Server"
Potential firewall blocks preventing the appliance from communicating with ESXi hosts.
Task noise impacting the ability to monitor other management operations.
VMware Cloud Foundation (VCF)
VMware Live Recovery (SaaS and On-Premise deployments of Live Recovery)
vSphere Replication
vCenter Server 8.x
The vSphere Replication Management Server (VRMS) is designed to automatically attempt registration of the replication service on all ESXi hosts within the vCenter inventory to ensure target site readiness.
To stop the automated registration tasks, you must exclude the hosts or datacenters from the replication inventory using vSphere tags.
Create and Assign the Exclusion Tag:
Log into the vSphere Client.
Navigate to the Datacenter, Cluster, or ESXi Host you wish to exclude.
Select Summary > Tags > Assign.
Create or assign a tag with the exact name: com.vmware.vr.disallowedHost.
Note: Applying this at the Datacenter level recursively excludes all contained hosts.
Restart Appliance Services:
Log into the VRMS Appliance Management Interface (AMI) at https://<REDACTED_IP>:5480.
Navigate to the Services tab.
Restart the HMS Service (vSphere Replication Management Service) to ingest the new tags (warning before the service restart: Restarting the HMS Service may briefly interrupt replication management operations. Review this action before proceeding).
Verify Resolution:
Monitor the vCenter Recent Tasks to confirm the registration attempts have ceased.