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
vSphere Replication 8.x
vSphere Replication 9.x
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.
service hms stop
cat /opt/vmware/hms/conf/embedded_db.cfg
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 vrmsdbNote: 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.
service hms start