5.5

QuickStart Guide
22 VMware, Inc.
Actions
Results
The Secondary server provides the expected functionality of the Primary server.
Exercise Two
This exercise follows Exercise One. The objective is to take a working active server (Secondary) and
synchronize it with the passive (Primary). This exercise also demonstrates that all the correct services stopped
when the Primary server became passive.
Starting Conditions
vCenter Server Heartbeat is running on the Secondary Server, which is active. vCenter Server Heartbeat is not
running on the Primary server and is set to passive without starting vCenter Server Heartbeat.
Local users are aware that the service is unavailable for the duration of this exercise.
Actions
Results
Both machines are resynchronized. All the data changed on the Secondary machine while the Primary was not
running vCenter Server Heartbeat is updated onto the Primary machine. The Secondary (active) machine
continues to provide service.
Table 3-1. Exercise One Actions
Machine Activity Result
Primary Shut down vCenter Server Heartbeat. Select Stop VMware vCenter
Server Heartbeat and all protected applications, then click OK.
vCenter Server Heartbeat stops all
monitored services and exits.
With vCenter Server Heartbeat shut down, on the Primary server, go
to Start > All Programs > VMware > VMware vCenter Server
Heartbeat > Configure Server
to launch the Configure Server
wizard. In the wizard, change the Primary server’s role to passive.
Primary server becomes passive
Start vCenter Server Heartbeat. Then shut down Heartbeat and
select Stop VMware vCenter Server Heartbeat and all protected
applications, and then click OK.
This activates the network filter
hiding the Primary server from the
network.
Secondary Go to Start > All Programs > VMware > VMware vCenter Server
Heartbeat > Configure Server to launch the Configure Server
wizard. In the wizard, change the Secondary server’s role to active.
Then start vCenter Server Heartbeat.
The Secondary server starts as the
active server.
Client Compares application functional status to the predefined criteria for
availability and performance.
Secondary server behaves as the
Primary server.
Table 3-2. Exercise Two Actions
Machine Activity Result
Primary Start vCenter Server Heartbeat. vCenter Server Heartbeat starts. The vCenter Server
Heartbeat Console shows the connection from the
Secondary (active) to Primary (passive).
Wait for both the Registry and the File System to
become Synchronized. Access the vCenter Server
Heartbeat logs and confirm that no exception errors
occurred during synchronization.
Data replication resumes from the Secondary server
back to the Primary server. Both the File System &
Registry status become Synchronized.