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
About installing SQL Server for a high availability (HA) configuration
Review the following considerations for installing SQL Server:
If you use shared NetApp storage, ensure that the following configurations are in place:
The Microsoft iSCSI Initiator is configured to establish a persistent connection between the NetApp filer and the systems on which you plan to install SQL Server.
The volumes are created on an external, basic disk, or LUNs (virtual disks) on a NetApp filer. These disks must be mounted on or connect to the first system on which you plan to install SQL Server.
If you use Windows LDM storage, ensure that the disks are accessible from all the systems on which you plan to install SQL Server .
Veritas recommends that you create volumes for the following:
SQL Server data
Registry replication
User defined database
User defined database logs
FILESTREAM enabled databse objects
When installing SQL Server on the first system in a physical environment, install the SQL Server instance on the local disk.
In case of shared storage, install the database files and the analysis service files on shared disks. These disks must be accessible from all the systems on which you plan to install SQL Server.
In case of non-shared storage, install the database files and analysis service files on the disks that reside on a datastore. This datastore must be accessible from all the systems on which you plan to install SQL Server. These disks are deported and imported during a failover.
When installing SQL Server on the first system in a VMware virtual environment, install the SQL Server instance at the default path. Ensure that you configure the data folders and log folders on a VMDK.
When installing SQL Server on additional systems in a physical environment, it does not matter whether the storage is shared or non-shared. Install the SQL Server instances, database files, and analysis service files on the local disk.
When installing SQL Server on additional systems in a VMware virtual environment, install the SQL Server instance at the default path. The data folders and log folders may be placed anywhere. However, ensure that you use the same instance name that you used when installing SQL Server on the first node.
If you are installing multiple instances of SQL Server on the same system, ensure the following:
Assign a unique name and a unique instance ID to each SQL Server instance. When installing SQL Server on additional systems for the same instance, ensure that you specify the same instance name and ID.
The order of the instance installation does not matter. You must ensure that the instances are installed with the same name and ID on all the systems.
Assign a unique port number for each instance.
Ensure that the [NT AUTHORITY\SYSTEM] account is granted the sysadmin server role (from SQL Management Studio Console).
The logged-on user must be a domain user with local Administrator privileges.
The logged-on user must be a member of the local Administrators group on all there systems where you plan to install SQL Server .