6.3

VMware, Inc. 29
Chapter 2 vCenter Server Heartbeat Implementation
Latency
Latency has a direct effect on data throughput. Latency on the link should not fall below the standard defined
for a T1 connection.
Heartbeat Diagnostics can assist in determining the available bandwidth, required bandwidth, and server
workload. For more information about Heartbeat Diagnostics, contact VMware Professional Services.
Antivirus Recommendations
Consult with and implement the advice of your antivirus (AV) provider, as VMware guidelines often follow
these recommendations. Consult the VMware knowledge base for up to date information on specific AV
products.
Do not use file level AV to protect application server databases, such as MS SQL Server databases. The nature
of database contents can cause false positives in virus detection, leading to failed database applications, data
integrity errors, and performance degradation.
VMware recommends that when implementing vCenter Server Heartbeat, you do not replicate file level AV
temp files using vCenter Server Heartbeat.
The file level AV software running on the Primary server must be the same as the software that runs on the
Secondary server. In addition, the same file level AV must run during both active and passive roles.
Configure file level AV to use the management IP address on the passive server for virus definition updates.
If this is not possible, manually update virus definitions on the passive server.
Exclude the following VMware directories from file level AV scans (C:\Program Files\VMware\VMware
vCenter Server Heartbeat\ is the default installation directory):
 C:\Program Files\VMware\VMware vCenter Server Heartbeat\r2\logs
 C:\Program Files\VMware\VMware vCenter Server Heartbeat\r2\log
Any configuration changes made to a file level AV product on one server (such as exclusions) must be made
on the other server as well. vCenter Server Heartbeat does not replicate this information.
Deployment Options Summary
Table 2-1 provides all possible deployment options described in this section.
Table 2-1. Installation Options
Network Node Configuration Clone Technique Component
LAN WAN
Identical
Nodes
Non-identical
Nodes Pre-Clone
Install
Clone
vCenter
Server
w/SQL Local
vCenter Server
w/SQL Remote
vCenter
Server Only
V2VXXXXX XXX
P2VXXXXXXXXX
P2PXXX XXXX