6.3

VMware, Inc. 29
Chapter 3 Installation Verification
Actions
Results
Both machines become resynchronized. All the data changed on the Secondary machine while vCenter Server
Heartbeat was not running on the Primary server has been updated onto the Primary machine and the
Secondary (active) machine continues to provide service. This exercise demonstrated that data changes
occurring on the Secondary server while vCenter Server Heartbeat was not running on the Primary server are
successfully replicated to the Primary server when vCenter Server Heartbeat is restarted on the Primary
server.
Switchover Exercise
This exercise demonstrates the ability to switch the functionality and operations of the active server on
command to the other server in the pair using the vCenter Server Heartbeat Console. Perform this exercise
only after successfully completing the Failover Simulation and Data Replication Exercises.
Notify any local users that the service will be unavailable for the duration of the exercise.
Starting Conditions
Using the System Tray icon, verify that the Secondary server is active (S/A) and servicing clients. On the
Primary server, verify that the server is passive using the System Tray icon status (P/—). On the Secondary
server, launch the vCenter Server Heartbeat Console and select the Data: Replication tab. Verify that both the
File System and Registry status are Synchronized.
Actions
Table 3-2. Data Replication Exercise Actions
Machine Activity Result
Primary Right-click on the System Tray icon and select Start
VMware vCenter Server Heartbeat.
vCenter Server Heartbeat starts. Launch the vCenter
Server Heartbeat Console. Select the Server:
Summary tab to show the connection from the
Secondary (active) to Primary (passive).
Select the Data: Replication tab and wait for both the
File System and the Registry status to display
Synchronized. Access the vCenter Server Heartbeat
logs and confirm that no exception errors occurred
during the synchronization process.
Data replication resumes from the Secondary server
back to the Primary server. Both the File System &
Registry status become Synchronized.
Table 3-3. Switchover Exercise Actions
Machine Activity Result
vCenter Server
Heartbeat Console
Click on the Server: Summary tab. Select the
Primary server icon and click Make Active.
The vCenter Server Heartbeat Console Server:
Summary page displays the applications
stopping on the active server. Once all
applications are stopped, the active server
becomes passive and the passive server
becomes active. The Console shows the
applications starting on the newly active
server.
Both the File System and Registry status are
Synchronized.
Any Confirm application performance and
availability meets previously defined criteria.
Verify that client applications are running as
expected after the switchover process.
Services continue to be provided as before the
switchover occurred. You may need to refresh
or restart some client applications as a result of
a switchover.