Specifications

Reference Guide
28 VMware, Inc.
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.
Installation Options Checklist
Verify the prerequisites:
Server architecture:
___ P2P
___ P2V
___ V2V
Cloning technology option:
___ Pre-Clone Install
___ Install Clone
Application components to protect:
___ vCenter Server with SQL Server on same host
___ vCenter Server with SQL Server on separate host
___ vCenter Server only
Network environment type:
___ LAN
___ WAN
Table 2-1. Installation Options
Network Clone Technique Component
LAN WAN Pre-Clone InstallClone
vCenter Server w/SQL
Local
vCenter Server w/SQL
Remote vCenter Server Only
V2V X X X - X X X
P2V X X X X X X X
P2P X X - X X X X