VLSR - DeltaAbortedException error while performing sync task

Products

• VMware Live Recovery

Issue/Introduction

Replication status will show up as OK on one side but have missing last instance sync point or it will show up with all information on the other side but show as not active
Configuring a replication will show up as Initial Sync and then move to Not Active but will show as OK on the target site

Environment

vSphere Replication 8.x
vSphere Replication 9.x

Cause

The issue occurs when the vSphere Replication Appliance management service "HMS" cannot create more threads to process events or there is a lack of memory. When more and more events are in pending status the incoming/outgoing replication status is shown inconsistent. 

Resolution

1. Snapshot both Protected and Recovery vSphere replication management appliance
2. Log in via SSH or console as Admin user and perform sudo to root
3. Stop the HMS service:

   service hms stop

4. Obtain the vrmsdb postgres password

   cat /opt/vmware/hms/conf/embedded_db.cfg

5. Run the following command to clear out all tasks and event prior to the last hour on both sides

   epochtime=`date +%s`000 && conditiontime=$((epochtime-3600000)) && echo "DELETE from incomingeventlogentity WHERE timestamp < $conditiontime;DELETE from outgoingeventlogentity WHERE timestamp < $conditiontime; " | /opt/vmware/vpostgres/current/bin/psql -U vrmsdb

   Note: This command takes the current timestamp, converts into epoch format and adds 000 to convert to milliseconds (This is how the event logs are stored) It then connects to the database and removes all entries from both incoming and outgoing.
6. Start the HMS service:

   service hms start

7. Close all browsers and re-launch the vSphere replication interface - VM status should now be consistent in the outgoing and incoming replication tabs