Cluster Server 8.0 Implementation Guide for Microsoft SQL Server - Windows
- Section I. Introducing Veritas InfoScale solutions for application high availability
- Understanding the InfoScale solutions for application high availability
- About the VCS agents for SQL Server
- How VCS monitors storage components
- How application availability is achieved in a physical environment
- How is application availability achieved in a VMware virtual environment
- Managing storage and installing the VCS agents
- Installing SQL Server
- Understanding the InfoScale solutions for application high availability
- Section II. Configuring SQL Server in a physical environment
- Overview
- Configuring the VCS cluster
- Configuring the SQL Server service group
- Configuring a SQL Server service group using the wizard
- Making SQL Server user-defined databases highly available
- Verifying the service group configuration
- Administering a SQL Server service group
- Configuring an MSDTC service group
- Configuring the standalone SQL Server
- Configuring an Active/Active cluster
- Configuring a disaster recovery setup
- Section III. Configuring SQL Server in a VMware environment
- Configuring application monitoring using the Veritas High Availability solution
- Administering application monitoring
- Administering application monitoring using the Veritas High Availability tab
- Administering application availability using Veritas High Availability dashboard
- Understanding the dashboard work area
- Section IV. Appendixes
- Appendix A. Troubleshooting
- Error and warning messages from VCS agent for SQL Server
- Troubleshooting application monitoring configuration issues
- Troubleshooting Veritas High Availability view issues
- Appendix B. Using the virtual MMC viewer
- Appendix A. Troubleshooting
Understanding the Veritas High Availability tab work area
The Veritas High Availability tab displays the consolidated health information for applications running in a Cluster Server (VCS) cluster. The cluster may include one or more systems.
When you click a system in the inventory view of the VMware vSphere Client, the Veritas High Availability tab displays application information for the entire VCS cluster, not just the selected system.
Note:
If you do not configure any application for monitoring in the VCS cluster, then the Veritas High Availability tab displays only the following link: .
The Veritas High Availability tab uses icons, color coding, dependency graphs, and tool tips to report the detailed status of an application.
TheVeritas High Availability tab displays complex applications, like SAP Netweaver, in terms of multiple interdependent instances of that application. These interdependent instances represent component groups of the application. The component groups are also known as "service groups" in VCS terminology.
Each service group in turn includes several critical components of the application. The components are known as "resources" in VCS terminology.
The following figure displays two instances of SAP running in the Veritas High Availability tab:
Title bar | Actions menu |
Aggregate status bar | Application dependency graph |
Application table | Application-specific task menu |
Component dependency graph |
The Veritas High Availability tab graphic user interface (GUI) includes the following components:
Title bar: Displays the name of the VCS cluster, the Actions menu, the Refresh icon, the Alert icon. Note that the Alert icon appears only if the Veritas High Availability view fails to display a virtual machine, or displays stale data
Actions menu: Includes a drop-down list of operations that you can perform with effect across the cluster. These include: Configuring an application for high availability; Unconfigure all applications; and Unconfigure VCS cluster.
Aggregate status bar: Displays a summary of applications running in the cluster. This summary includes the total number of applications, and the state-wise breakdown of the applications in terms of the Online, Offline, Partial, and Faulted states.
Application dependency graph: Illustrates the order in which the applications or application instances, must start or stop.
If an application must start first for another application to successfully start, the former application appears at a lower level. A line connects the two applications to indicate the dependency. If no such dependency exists, all applications appear in a single horizontal line.
Application table: Displays a list of all applications that are configured in the VCS cluster that is associated with the system you selected in the inventory view.
Each application is listed in a separate row. Each row displays the systems where the application is configured for monitoring.
The title bar of each row displays the following entities to identify the application or the application instance (service group):
Display name of the application (for example, Payroll application)
Type of application (for example, Custom)
Service group name
Application-specific task menu: Appears in each application-specific row of the application table. The menu includes application-specific tasks such as Start, Stop, Switch, and a drop-down list of more tasks. The More drop-down list includes tasks such as Add a failover system, and Remove a failover system.
Component dependency graph: Illustrates the order in which application components (resources) must start or stop for the related application or application instance to respectively start or stop. The component dependency graph by default does not appear in the application table. To view the component dependency graph for an application, you must click a system on which the application is running.
The track pad, at the right-bottom corner helps you navigate through complex component dependency graphs.
If you do not want to view the component dependency graph, in the top left corner of the application row, click
.