VMware VCENTER SERVER 4.0 - GETTING STARTED UPDATE 1 Specifications download pdf (Page 184)

Reference Guide

184 VMware, Inc.

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 file 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.

Symptom

File System Status is Out of sync or Synchronized and busy processing.

Cause

A service running on the Passive server opens a protected file for exclusive access. If vCenter Server Heartbeat

attempts to update this opened file, 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.

Services that keep files locked on the passive server are:

 Protected application services

 File level antivirus tool services

Resolution

Until the file is closed on the passive server, vCenter Server Heartbeat reports the file status and the File System

Status as Out of sync.

To resolve the Out of sync status

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 file level antivirus is not part of the protected set as the file level antivirus and the

corresponding services are running on both machines.

VMware Channel Incorrectly Configured

If the VMware Channel is not properly configured, it cannot initiate the handshake to establish

communications through the VMware Channel connection.

Symptom

Failure to establish the VMware Channel connection prevents a full system check, thereby leaving the File

System Status and Registry Status as Out of sync.

OTE This occurs if the vSphere Client is left running on the passive server.

OTE vCenter Server Heartbeat periodically checks for and stops any services running on the passive server.

1 2 ... 179 180 181 182 183 184 185 186 187 188 189 ... 203 204

No comments

VMware VCENTER SERVER 4.0 - GETTING STARTED UPDATE 1 Specifications Page 184