Unable to Perform 'Sync Now' on VMs – DeltaAbortedException error
Article ID: 401640
Updated On:
Products
Issue/Introduction
Symptoms:
- VMs report "
RPO violation and Not Active state" -
Manual sync attempts on affected VMs fail with replication errors.
-
Reconfiguring the VM completes successfully but gets stuck in incremental sync and again shows RPO violation with "
No Instance' in 'Last Instance Sync Point' field" -
Intermittent replication sync activity is seen, but sync fails repeatedly.
-
From ESXi vmkernel.log on both source and destination hosts shows repeated “
Broken pipe” errors.
Environment
VMware Live Site Recovery 9.x
vSphere Replication 8.x
Cause
Although the sync task is completed successfully by the secondary VR, frequent network disconnections result in a large number of incoming and outgoing log entities accumulating. As a result, the source HMS is unable to receive updates on the replication status in a timely manner, which leads to the sync task being aborted.
In source site /opt/vmware/hms/logs/hms.log, you will see the event "com.vmware.hms.replication.sync.DeltaAbortedException"
Caused by: com.vmware.vim.vmomi.client.exception.ConnectionException: https://172.17.xx.3:8043 invocation failed with "org.apache.http.conn.HttpHostConnectException: Connect to 172.17.xx.xx:8043 [/172.17.xx.3] failed: Connection refused (Connection refused)"
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:265) ~[vlsi-client-8.8.0.jar:?]
... 84 more
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to 172.17.xx.xx:8043 [/172.17.xx.xx] failed: Connection refused (Connection refused)
2025-06-17 01:59:43.395 ERROR com.vmware.hms.replication.sync.ReplicationSyncManager [hms-sync-progress-thread-4] (..replication.sync.ReplicationSyncManager) [operationID=78cf1166-b779-4359-b735-7c2b0da756ea-HMS-12719,sessionID=B813AD77] | Completing sync operation because of error: {OnlineSyncOperation, OpId 78cf1166-####-####-####-7c2b0da756ea-HMS-######, GroupMoId=GID-8b35f5f9-####-####-####-b1d96bcf6b65, ExpInstSeqNr=1148500, TaskMoId=HTID-6adb40c5-####-####-####-ad9 49f5cb96a, InstanceId=4ec221ef-####-####-####-58eb6ac752e1(retry:1), OpState=started, VcVmMoid=vm-26634, createInstanceRetryCount=2, fullSyncOngoing=false, operationId=null}com.vmware.hms.replication.sync.DeltaAbortedException: nullIn the target site hms event log, you will see the below event stating sync completed.
2025-06-17 01:58:12.534 DEBUG com.vmware.hms.eventlog.delivery.HmsEventSite [hms-eventlog-commons-thread-0] (..eventlog.delivery.EventSite) [operationID=f9bf2569-cdae-4915-83a6-0ced50007f94-HMS-EVENT] | pushEventsToHmsEventSite-565363cc-f136-44c9-b3ca-6826104d3bfc@1816021029: 0 - target site is up to date
Resolution
It is advised to investigate and mitigate frequent network outages occurring between the primary and disaster recovery (DR) sites. These disruptions are directly contributing to replication inconsistencies and failures, including issues such as sync task interruptions and accumulated event logs.
workaround:
Take a snapshot of the VR appliance at the site where the Site Recovery UI reports the issue.
Take the SSH to VR appliance.
Stop the HMS service by running:service hms stop
Access the VRMS database:/opt/vmware/vpostgres/current/bin/psql -U vrmsdb
(DB password is located in /opt/vmware/hms/conf/embedded_db.cfg)
Check event counts using:
select count(*) from outgoingeventlogentity;
select count(*) from incomingeventlogentity;
Delete old records based on current epoch time (add three zeroes to the epoch timestamp):
DELETE FROM incomingeventlogentity WHERE timestamp < <converted_epoch_time>;
DELETE FROM outgoingeventlogentity WHERE timestamp < <converted_epoch_time>;
Start the HMS service:service hms start
Reload the Site Recovery UI and verify that the "Last Instance Sync Point" displays the correct date and time for each replicating VM.
Feedback
