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
About installing SQL Server on additional systems
Note:
This topic is not applicable in case of non-shared storage configurations. Instead, follow the prerequisites and procedure for installing SQL Server on the first system.
Review the following considerations for installing SQL Server on the additional systems:
Install SQL Server in the standalone installation mode in a non-clustered environment.
Ensure that all the SQL Server services other than the SQL Server Browser service are stopped on the first system where this instance is installed.
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.
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, select the same features that you selected during the installation on the first system.
On the Instance Configuration panel, make the following selections:
Specify the same instance name and instance ID that you used while installing this instance on the first system.
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 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 VCS agent's SQLClusterAccount attribute while configuring the SQL Server service group later.
On the Data Directories tabs of the Database Engine Configuration panel and the Analysis Services Configuration panel, do the following:
Set the locations of database files and the analysis service files to the local disk.
You do not need to install these files to the shared storage that cluster disk group manages. The SQL Server Agent Configuration Wizard configures the SQL Server instance to use the files from the shared storage.
If you choose a shared storage location, ensure that you do not overwrite the data directories that were created when installing SQL Server on the first system.
Refer to the Microsoft documentation for application-specific instructions.