6.5
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Introduction
- Configuring vCenter Server Heartbeat
- Server Protection
- Checking the Server Pair Status
- Monitoring the Status of Servers
- Configuring Heartbeat Settings
- Network Protection
- Application Protection
- Applications: Summary Tab
- Resetting the Application Health Status
- Viewing Application Status
- Setting the Application Timeout Exception
- Remove an Application
- Manually Stop and Start Applications
- Configuring Applications
- Application Maintenance Mode
- Reviewing the State of an Application
- Reviewing the Applications Log
- Filtering Application Log Entries
- Applications: Services Tab
- Applications: Tasks Tab
- Applications: Plug-ins Tab
- Applications: Summary Tab
- Status and Control
- About vCenter Server Heartbeat Console
- Working with Groups
- Working with Pairs in vCenter Server Heartbeat Groups
- Reviewing the Status of vCenter Server Heartbeat Groups and Pairs
- Exiting vCenter Server Heartbeat Console
- Shutting Down Windows Without Stopping vCenter Server Heartbeat
- Controlled Shutdown
- vSphere Web Client Plug-in
- Uninstalling vCenter Server Heartbeat
- Performance Protection
- Data Protection
- Alerts and Events
- Troubleshooting
- Two Active or Two Passive Servers
- Synchronization Failures
- Registry Status is Out-of-Sync
- Channel Drops
- Performance Issues
- Passive Server Does Not Meet Minimum Hardware Requirements
- Hardware or Driver Issues on VMware Channel NICs
- Firewall Connection
- Channel Fails to Connect After Configuring Firewall Ports
- Incorrect VMware Channel Configuration
- VMware vCenter Server Heartbeat Packet Filter Is Enabled on the Channel NIC(s)
- Subnet or Routing Issues
- MaxDiskUsage Errors
- Application Slowdown
- Glossary
Passive Server Has Less Available Space than Active Server
Inadequate available disk space on the passive server can cause replication to cease.
Problem
Replication stops with the following error:
[N27]Failed to write information for the file: {filename} to the disk. Either the disk is full or
the quota (for the SYSTEM account) was exceeded.
Cause
The passive server has less available disk space than the active server, preventing updates from being replicated
to the passive server. The quantity of updates from the active server exceeds the passive server's available disk
space.
Solution
◆
Free up some additional disk space on the passive server. Do not delete data from the protected set to
prevent data loss in the event of a switchover. You could update the disk subsystem on the passive server.
After allocating space, start replication.
Registry Status is Out-of-Sync
The Registry can be reported as Out-of-sync when one or more Registry keys fail to synchronize.
Registry Security Issues
Inability to access the registry prevents replication of the registry.
Problem
vCenter Server Heartbeat is unable to read, sync, or replicate the registry.
Cause
If a protected registry key has permissions that deny Write access to the System account, this can prevent
vCenter Server Heartbeat from synchronizing or replicating it.
Solution
◆
Change the permissions on the aected registry key to grant the System account Full Control.
88 VMware, Inc.
Administrator Guide