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
Configuring a standalone SQL Server for high availablility
Perform the following tasks to configure the standalone SQL Server for high availability, in an active-passive configuration with one to one failover capabilities:
Note:
In addition to the tasks mentioned below, the procedures described in Microsoft Knowledge Base Article - 224071: INF: Moving SQL Server databases to a New Location with Detach/Attach are required.
Refer to: http://support.microsoft.com/default.aspx?scid=kb;en-us;224071.
The following table lists the tasks to configure the standalone SQL Server for high availability.
Table: Tasks to configure the standalone SQL Server for high availability
Task | Description |
|---|---|
Prepare the standalone SQL Server | Complete the following tasks before you begin the InfoScale installation and configuring a VCS cluster:
|
Install the InfoScale product and configure VCS cluster on the standalone SQL server | Install Arctera InfoScale Availability on all the systems where you want to configure the application. During installation, the product installer installs the VCS agents required for making the applications highly available. For details refer to theArctera InfoScale™ Installation and Upgrade Guide. For details on configuring the VCS cluster, refer to, See Configuring the cluster using the Cluster Configuration Wizard. |
Create volumes or LUNs (virtual disks) necessary to manage the SQL Server storage. | |
Install and configure SQL Server on additional nodes, if required | Perform the following tasks to install Microsoft SQL Server on additional nodes.
|
Verify that the existing SQL Server databases and logs are moved to shared storage | Verify the location of all SQL Server databases and logs for the existing standalone server. If they are located on local storage, move them from the local drive to the appropriate volumes or LUNs on shared storage to ensure proper failover operations in the cluster. |
Configure the SQL Server service group | |
Create and manage SQL Server user-defined database | See Making SQL Server user-defined databases highly available. |