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 on the first system
Review the following considerations for installing SQL Server on the first system:
Install SQL Server in the standalone installation mode in a non-clustered environment.
Make sure that the volumes or LUNs (virtual disks) required for SQL Server are mounted or connected to the system.
When installing SQL Server on the first system in a VMware virtual environment, install the SQL Server instance at the default path. Place the data folders and log folders on a VMDK. The VMware disk agent detaches and attaches the disk between nodes during a failover.
Open the SQL Server Installation Center using the appropriate Microsoft SQL Server installer.
To launch the SQL Server Setup wizard, click
on the Installation panel.On the SQL Server Setup wizard, provide the following information:
On the Feature Selection panel, ensure that you select all the features (for example, Full-Text Search, Analysis Services) that you plan to configure for high availability.
On the Instance Configuration panel, make the following selections:
Specify the instance name and instance ID, and make a note of these values.
You must use the same name and ID when you install the SQL Server instance on additional systems.
If you plan to install multiple instances of SQL Server in a cluster, each instance must have a unique instance name and instance ID. Later, use these same values when installing the instance on the corresponding additional systems.
Ensure that the Instance root directory resides on the local system disk.
Doing so installs the SQL Server instance on the local disk. The location of data directories is to be specified later on a different panel of the installation wizard.
On the Service Accounts tab of the Server Configuration panel, specify the following values:
Specify a domain user name for the SQL Server services account.
Note:
This user may not be a part of the local Administrators group on all the systems. In this case, you must configure the SQLClusterAccount attribute of the VCS agent while configuring the SQL Server service group later.
Set the Startup Type of the SQL Server Browser service to Automatic.
Set the Startup Type of all the other services to Manual.
Alternatively, use the SQL Server Configuration Manager to change the Startup Type of each service it after the installation is complete.
On the Data Directories tab of the Database Engine Configuration panel, verify the following:
In case of shared storage, all the directories must be located on the shared disks.
In case of non-shared storage, all the directories must be located on the disks that reside on a shared datastore. These include Data root, User database, User database log, Temp DB, Temp DB log, and Backup.
On the Data Directories tab of the Analysis Services Configuration panel, verify the following:
In case of shared storage, all the directories must be located on the shared disks.
In case of non-shared storage, all the directories must be located on the disks that reside on a shared datastore. These directories include Data, Log file, Temp, and Backup.
Refer to the Microsoft documentation for the application-specific instructions.