Replicating VMs shows 'No Instance' in 'Last Instance Sync Point' field

Products

• VMware Live Recovery

Issue/Introduction

In Site Recovery UI, under 'Replication' tab, all the VMs fail to show 'Last Instance Sync Point'.
It shows 'No instance' instead of the Date and time of the last sync.
Site Recovery UI at the other site may show the Date and time correctly for 'Last Instance Sync Point' field.

Environment

vSphere Replication 8.x
vSphere Replication 9.x

Cause

This is a cosmetic error that is observed when HMS (VR Management service) does not have memory resources to create more threads.

This is because of incoming and outgoing event logs consuming all resources.

Resolution

a) Take snapshot of the VR appliance at the site where the Site Recovery UI reports this issue.

b) Login to the VR appliance SSH as root.

c) Stop hms service running command:
# service hms stop

d) Edit the hms configuration file: /opt/vmware/hms/conf/hms-configuration.xml
Change the value for hms-eventlog-maxage to the following:
<hms-eventlog-maxage>10800</hms-eventlog-maxage>

e) Edit the /etc/systemd/system.conf file
Change the value for #DefaultTasksMax to DefaultTasksMax=infinity

f) Login to the VRMS DB using following command:

# /opt/vmware/vpostgres/current/bin/psql -U vrmsdb

(Get the password DB password from the file : /opt/vmware/hms/conf/embedded_db.cfg)

g) Check the count of the events in the tables outgoingeventlogentity and incomingeventlogentity using following two commands:

> select count(*) from outgoingeventlogentity

> select count(*) from incomingeventlogentity

h) Check the current epoch time first - https://www.epochconverter.com/
You must add 3 zeroes to this number (Example: 1712583312000)

e.g.
DELETE from incomingeventlogentity WHERE timestamp < 1712583312000;
DELETE from outgoingeventlogentity WHERE timestamp < 1712583312000;  

i) Start the hms service:
# service hms start

j) Reload Site Recovery UI to check the 'Last Instance Sync Point'. It should show the correct date and time for 'Last Instance Sync Point' for each of the Replicating VMs.

(Perform this operations on other VR appliance as well if it exhibits the similar behaviour).