6.5

4 On the server to make passive, start the Server Conguration wizard, and conrm the passive server. Do
not change the identity (Primary or Secondary).
5 Restart the passive server. All protected application services stop.
6 Start vCenter Server Heartbeat on both servers.
Synchronization Failures
When you start vCenter Server Heartbeat, a full system check occurs to verify the following:
■
All protected registry keys and values from the active server are present on the passive server
■
All protected le and folder structures from the active server are present on the passive server
After the full system check completes, the File System Status and the Registry Status display as Synchronized.
However, the File System Status or the Registry Status can also display as Out of sync or Synchronized and
busy processing. Some typical scenarios are described with possible causes and workarounds.
Services Running on the Passive Server
Services running on a passive server is not normal behavior and can prevent synchronization.
Problem
File System Status is Out-of-sync or Synchronized and busy processing.
Cause
A service running on the passive server opens a protected le for exclusive access. If vCenter Server Heartbeat
attempts to update this opened le, the Apply component logs the following error message:
[N29]The passive VMware vCenter Server Heartbeat server attempted to access the file: {filename}.
This failed because the file was in use by another application. Please ensure that there are no
applications which access protected files running on the passive.
Note This occurs if the vSphere Client is left running on the passive server.
Services that keep les locked on the passive server are:
■
Protected application services
■
File level anti-malware tool services
Note vCenter Server Heartbeat periodically checks for and stops any services running on the passive server.
Solution
Until the le is closed on the passive server, vCenter Server Heartbeat reports the le status and the File System
Status as Out-of-sync.
1 Set Protected Application services to Manual on both servers and verify that they are not running on the
passive server.
2 Set Recovery Actions to Take No Action. You can set this from the Service Control Manager (SCM) for the
Protected Application services. Otherwise, the SCM restarts the Protected Application services.
3 Verify that le level anti-malware protection is not part of the protected set as the le level anti-malware
and the corresponding services are running on both machines.
86 VMware, Inc.
Administrator Guide