6.5

Table 3- 1. System Status
DescriptionIconStatus
File and registry replication is in the process of stopping and all protected
applications may be closing down.
Not replicating
The system is in the process of performing a switchover.Switching active server
VMware Channel connections have been established between the two servers.Connecting to peer
server
VMware Channel connections have been lost between the two servers.Disconnecting from peer
server
File replication is in the process of being stopped and, optionally, all protected
applications may be closing down.
Stopping replication
The replication process is starting and protected applications are optionally starting.Starting replication
The Heartbeat service is initializing on the active server and starting protected
applications.
Starting as active server
The Heartbeat service is stopping. The Heartbeat service is shutting down, and will
no longer participate in replication. Optionally, protected applications may be
stopped.
Heartbeat service
shutting down
The passive server has lost connection to the active server. If this condition persists
for the failover timeout, and failover is permitted between the pair of servers, then
a failover will occur.
Lost active server
A failover has occurred,Active following failover
The Heartbeat service cannot be contacted on the server.Server not responding
When viewing the status of the passive server, the status of the le system and registry are displayed graphically.
The following tables list possible synchronization statuses and their meanings.
Table 3- 2. File System and Registry Status
DescriptionIconStatus
Fully synchronized.Synchronized
There are les that are currently unchecked. A full system check did not complete.Unchecked
Not synchronized.Out-of-Sync
Displayed when the Heartbeat service is starting up or shutting down.Uninitialized
The registry is currently in the process of synchronization.Checking
Not synchronized.Error
When the vCenter Server Heartbeat pair establishes a connection, it triggers a le synchronization and
verication process to ensure all protected les on both servers are identical. The process checks each 64K
block of each protected le and performs a checksum to determine whether the blocks dier. If the blocks are
the same, the block is marked as synchronized. If the blocks dier, then the block is replicated to the passive
server and then marked as synchronized. The le verication and synchronization process is nished after all
blocks of all stipulated les are marked as synchronized.
30 VMware, Inc.
Administrator Guide