InfoScale™ 9.0 Cluster Server Administrator's Guide - Windows
- Section I. Clustering concepts and terminology
- Introducing Cluster Server
- About Cluster Server
- About cluster control guidelines
- About the physical components of VCS
- Logical components of VCS
- Types of service groups
- Agent classifications
- About cluster control, communications, and membership
- About security services
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Getting started with VCS
- Administering the cluster from the command line
- About administering VCS from the command line
- Stopping the VCS engine and related processes
- About managing VCS configuration files
- About managing VCS users from the command line
- About querying VCS
- About administering service groups
- Modifying service group attributes
- About administering resources
- About administering resource types
- About administering clusters
- Configuring resources and applications in VCS
- About configuring resources and applications
- About Virtual Business Services
- About Intelligent Resource Monitoring (IMF)
- About fast failover
- How VCS monitors storage components
- About storage configuration
- About configuring network resources
- About configuring file shares
- About configuring IIS sites
- About configuring services
- Before you configure a service using the GenericService agent
- About configuring processes
- About configuring Microsoft Message Queuing (MSMQ)
- About configuring the infrastructure and support agents
- About configuring applications using the Application Configuration Wizard
- Adding resources to a service group
- About application monitoring on single-node clusters
- Configuring the service group in a non-shared storage environment
- About the VCS Application Manager utility
- About testing resource failover using virtual fire drills
- Modifying the cluster configuration
- Section III. Administration - Beyond the basics
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- Customized behavior diagrams
- VCS behavior for resources that support the intentional offline functionality
- About controlling VCS behavior at the resource level
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- VCS event notification
- VCS event triggers
- List of event triggers
- Controlling VCS behavior
- Section IV. Cluster configurations for disaster recovery
- Connecting clusters–Creating global clusters
- VCS global clusters: The building blocks
- About global cluster management
- About serialization - The Authority attribute
- Prerequisites for global clusters
- Setting up a global cluster
- Configuring replication resources in VCS
- About IPv6 support with global clusters
- About cluster faults
- About setting up a disaster recovery fire drill
- Test scenario for a multi-tiered environment
- Administering global clusters from Cluster Manager (Java console)
- Administering global clusters from the command line
- About global querying in a global cluster setup
- Administering clusters in global cluster setup
- Setting up replicated data clusters
- Connecting clusters–Creating global clusters
- Section V. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- VCS agent statistics
- Troubleshooting and recovery for VCS
- VCS message logging
- Handling network failure
- Troubleshooting VCS startup
- Troubleshooting service groups
- Troubleshooting and recovery for global clusters
- VCS utilities
- VCS performance considerations
- Section VI. Appendixes
- Appendix A. VCS user privileges—administration matrices
- Appendix B. Cluster and system states
- Appendix C. VCS attributes
- Appendix D. Configuring LLT over UDP
- Appendix E. Handling concurrency violation in any-to-any configurations
- Appendix F. Accessibility and VCS
- Appendix G. Executive Order logging
About application monitoring on single-node clusters
Cluster Server (VCS) lets you configure HA for applications in single-node deployments, which do not involve any clustering of nodes. This feature is termed application monitoring on single-node clusters. The LLT, GAB, and fencing mechanisms are not involved, because there are no other nodes to communicate with or to monitor. In such a deployment, if a fault occurs with an application configured for HA, it is not failed over to any other node, but restarted on the same node. If an application is unable to come online or to recover after the predefined restart attempts, VCS uses the heartbeat mechanism to inform VMware of the application state.
VCS integrates with the underlying virtualization infrastructure to provide application HA. For example, VMware provides virtual machine (VM) monitoring capabilities through the vSphere Guest SDK. The SDK enables applications to heartbeat with VMware, and when a failure occurs, VMware takes the appropriate corrective action, like restarting or moving the VM.
Application monitoring on single-node clusters involves the following components:
The AppMonHB agent, which integrates with the application and with VMware. It monitors the application states, and if the application is unable to come online or to recover from a failure, it uses the heartbeat mechanism to inform VMware of the state. Additionally, if the VM is in an unhealthy state, AppMonHB cannot heartbeat with VMware, which indicates that corrective action is required. VMware may then restart the VM or move it, according to the virtualization configuration in your environment. AppMonHB is designed to wait for a predefined, customizable duration before taking any corrective action in case a fault occurs in any of the critical service groups. If the faulted service groups come online within this duration, no corrective action is taken.
For details, refer to the Cluster Server Bundled Agents Reference Guide - Windows.
The ConfigAppMonHB utility, which lets you configure the AppMonHB agent and the VCSAppMonRes resource. It also ensures that the feature is enabled on single-node deployments only. However, make sure that you do not enable the feature in a multi-node cluster; doing so may have unpredictable and undesirable effects.
See Configuring application monitoring on a single-node cluster.
See Verifying whether application monitoring is enabled on the single-node cluster.
See Unconfiguring application monitoring on a single-node cluster.
See About reviewing and troubleshooting the configuration and monitoring activities.