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
Configuring application monitoring on a single-node cluster
The ConfigAppMonHB
utility lets you configure HA for applications in single-node cluster deployments, which includes the application service groups and the AppMonHB agent resources.
At the vCenter level, make sure that:
The vSphere HA > VM Monitoring > VM and Application Monitoring options are enabled.
At least one heartbeat datastore is configured for vSphere HA.
To configure application monitoring on a single-node cluster
- Use either one of the following ways to invoke the ConfigAppMonHB.pl utility (default location:
%vcs_home%\bin\AppMonHB\
):Navigate to the
AppMonHB
directory and run:C:\Program Files\Veritas\clusterserver\bin\AppMonHB>"C:\Program Files\Veritas\VRTSPerl\bin\perl.exe" ConfigAppMonHB.pl
Navigate to the
VRTSPerl
directory and run:C:\Program Files\Veritas\VRTSPerl\bin>perl.exe "C:\Program Files\Veritas\cluster server\bin\AppMonHB\ConfigAppMonHB.pl"
- When prompted, enter E as the option to enable application monitoring on the node.
To configure monitoring for all the service groups in the cluster
- When prompted, enter A to enable application monitoring for all the service groups configured on the node.
If any required groups or resources are not present in the local cluster, the utility prompts you for further action:
To append the missing entities to the existing service groups in the cluster, enter A.
To add the missing entities as per your preference and reset the cluster, enter R.
To configure monitoring only for specific service groups in the cluster
- When prompted, enter S to enable application monitoring for a selective set of service groups configured on the node.
Note:
You can also use this option to selectively discontinue monitoring the application service groups that you specify.
- When prompted, enter the names of only those service groups that you want to monitor, separated by spaces; for example, SG1 SG2 SG3.
The utility repeats the names of the service groups that you specified and then displays the names of the service groups that may have already been configured for monitoring.
- When prompted, specify your preference:
To append to the list of existing service groups being monitored, enter A.
To reset the configuration and monitor only those service groups that you specified in the previous step, enter R.
To specify the duration after which corrective action is taken
- When the utility prompts you to update the WaitBeforeCorrectiveAction duration:
To use the default value of 300 seconds, enter N.
To specify a custom value, enter Y.
When prompted, enter the value in seconds, for example 30.
Alternatively, you can change the duration by running the following sequence of commands on the node at any later time:
# haconf -makerw
# hares -modify VCSAppMonRes WaitBeforeCorrectiveAction <integer value in seconds>
# haconf -dump -makero