InfoScale™ 9.0 Cluster Server 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 Veritas InfoScale solutions for monitoring SQL Server
- About the VCS agents for SQL Server
- How VCS monitors storage components
- Shared storage - if you use NetApp filers
- Shared storage - if you use SFW to manage cluster dynamic disk groups
- Shared storage - if you use Windows LDM to manage shared disks
- Non-shared storage - if you use SFW to manage dynamic disk groups
- Non-shared storage - if you use Windows LDM to manage local disks
- Non-shared storage - if you use VMware storage
- How application availability is achieved in a physical environment
- How is application availability achieved in a VMware virtual environment
- Modifying the ESXDetails attribute
- Managing storage and installing the VCS agents
- Installing SQL Server
- About installing SQL Server for a high availability (HA) configuration
- Configuring Microsoft iSCSI initiator
- About installing SQL Server on the first system
- About installing SQL Server on additional systems
- Assigning ports for multiple SQL Server instances
- Enabling IPv6 support for the SQL Server Analysis Service
- 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
- About configuring the SQL Server service group
- Before configuring the SQL Server service group
- Configuring a SQL Server service group using the wizard
- Configuring the service group in a non-shared storage environment
- Running SnapManager for SQL Server
- About the modifications required for tagged VLAN or teamed network
- 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. Appendixes
- Appendix A. Troubleshooting
- VCS logging
- VCS Cluster Configuration Wizard (VCW) logs
- VCWsilent logs
- NetApp agents error messages
- Error and warning messages from VCS agent for SQL Server
- Messages from the VCS agent for SQL Server Database Engine
- Messages from the VCS agent for SQL Server FILESTREAM
- Messages from the VCS agent for SQL Server Agent service and Analysis service
- SQL Server Analysis service (MSOLAP) service fails to come online with "invalid context of address" error
- Messages from the VCS agent for MSDTC
- Appendix B. Using the virtual MMC viewer
- Appendix A. Troubleshooting
SQL Server sample dependency graph
The following figure is a sample dependency graph, which depicts the resources and their dependencies a typical SQL Server service group in a NetApp environment.
A SQL Server service group is configured to make a SQL Server application highly available in a VCS cluster. The SQL Server Analysis service (MSOLAP) and the SQL Server Agent service (SQLServerAgent) are configured as GenericService resources.
As the dependency graph depicts:
The virtual name for the SQL Server is configured using the Lanman resource, and the service group IP address is configured using the IP and NIC resources.
The FileStream resource monitors the Windows FILESTREAM configuration settings for the SQL Server instance.
This graphic depicts shared storage that is configured in a NetApp environment.
If the shared storage is managed using Windows LDM, the VCS Mount and DiskRes resources replace the NetAppSnapDrive, NetAppSnapMirror, and NetAppFiler resources.
In case of non-shared storage managed using Windows LDM, the VCS Mount and NativeDisks resources should be configured instead.
In case the storage belongs to a VMware virtual environment, the VCS Mount, NativeDisks, and VMwareDisks resources are configured instead of the NetApp resources.
The SQL Server registry is replicated using the RegRep and RegRepNetAppSnapDrive resources.
The SQLServer resource comes online after each of these resources are brought online.