6.6
Table Of Contents
- vCenter Server Heartbeat Administrator's Guide
- Contents
- About This Book
- Introduction
- vCenter Server Heartbeat Monitoring
- Supported vCenter Server Heartbeat Clients
- vCenter Server Heartbeat Console
- vSphere Web Client Plug-in
- vSphere Client Plug-in
- Server Monitoring
- Network Monitoring
- Application Monitoring
- Performance Monitoring
- Monitoring Data Replication
- Managing vCenter Server Heartbeat
- Server Configuration Wizard
- Managing Heartbeat Settings
- Managing Application Protection
- Managing Services
- Managing Tasks
- Managing Rules
- Managing Plug-ins
- Managing Data Protection
- Maintaining vCenter Server Heartbeat
- vCenter Server Heartbeat Diagnostics
- Collecting Diagnostic Logs
- Two Active or Two Passive Nodes
- Synchronization Failures
- Registry Status is Out-of-Sync
- Channel Drops
- Performance Issues
- Passive Node 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
Changing the Order of Services
The exact order in which services start and stop is influenced by a number of key factors:
■
The order of applications specified by plug-ins determines which services are started first.
■
Services can have dependencies which must be respected. For example, if service B is listed after service
A under the User-Defined group, and service A depends on Service B, Service B starts first.
■
Multiple applications using the same service (the same service can appear under more than one sponsor).
The service starts when the first application to reference it starts.
■
The order of stopping services is the reverse for starting services.
Procedure
◆
To modify the order in which the services start and stop, use the Up and Down arrows.
Remove a Service
Procedure
1 Select the service to remove in the Applications: Services page.
2 Click Remove.
A confirmation message is displayed.
3 Click Yes.
The service is removed from the protected list.
Managing Tasks
Tasks are a generalization and extension of start, stop, and monitor scripts with task types determined by when
the tasks run. Task types include the following:
■
Network Configuration – Run when applications start and is intended to launch dnscmd or DNSUpdate.This
task can launch a batch script containing multiple dnscmd commands. Network Configuration tasks are
the only types of task that can vary between the Primary and Secondary nodes.
■
Periodic – Run at specific configurable intervals
■
Pre/Post Start – Run before and after services start on the active node
■
Pre/Post Stop – Run before and after services stop on the active node
■
Pre/Post Shadow – Run before and after the Data Rollback Module creates a shadow copy on the active
node (Not available in this release)
■
Rule Action – A configurable task run in response to a triggered rule or when a service check fails
Tasks can be defined and implemented by plug-ins, users, or can be built-in tasks defined by vCenter Server
Heartbeat. User defined tasks are implemented as command lines, which can include launching a batch script.
Examples of built-in tasks include monitoring a protected service state on the active and passive nodes. An
example of a plug-in-defined task is the discovery of protected data and services for a particular application.
The vCenter Server Heartbeat Applications:Tasks page provides a list of tasks and associated status information,
and includes features to quickly manage tasks.
58 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide