VMware vCenter Server Heartbeat - vCenter Server Heartbeat Synchronization Stops at a File which Rolled Over and No Longer Exists on the Passive Server

Follow

Summary

This Knowledge Base article provides information about vCenter Server Heartbeat synchronization stopping at a file that was rolled over and does not exist anymore.


More Information

Symptom

When viewing the Data: Replication page of the vCenter Server Heartbeat Console, the synchronization progress stops on a file from the C:\Program Files\VMware\Infrastructure\Inventory Service\Data\Log directory and fails to progress further.

Cause

Synchronization has stopped because a log file in the C:\Program Files\VMware\Infrastructure\Inventory Service\Data\Log directory was rolled over and is no longer present on the passive server.

Resolution

Exclude the C:\Program Files\VMware\Infrastructure\Inventory Service\Data\Log directory using the procedure below:

  1. Navigate to the Data: File Filters page of the vCenter Server Heartbeat Console.
  2. Click Add Exclusion Filter .
  3. Enter C:\Program Files\VMware\Infrastructure\Inventory Service\Data\Log\** into the Pattern field.
  4. Click OK .


Applies To

All Versions


Related Information

vCSHB-Ref-2278

KBID-2278

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.