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
Adding storage agent resources to the SQL service group
After creating the database, run the SQL Server Configuration Wizard and modify the SQL Server service group. This allows the wizard to add the NetAppFiler and NetAppSnapDrive (Mount and DiskRes in case of Windows LDM) storage resources for the user databases, to the SQL Server service group.
You must run the SQL Server Configuration Wizard in the modify mode only if you create user-defined databases after creating the SQL Server service group.
For a shared storage configuration, use the service group configuration wizard to modify the service group. For a non-shared storage configuration, use the Cluster Manager (Java Console) to add the required storage resources to the service group manually.
Note:
You must run the wizard in the modify mode even if you have added or changed volumes in your existing configuration.
Before running the configuration wizard to add the storage agent resources, do the following:
Make sure the SQL service group is online.
Make sure the volumes for the user database, transaction logs, and FILESTREAM are mounted on the node.
Note:
Mount or NetAppSnapDrive resources are required only if the database is created on a new volume.
To add storage agent resources to the SQL service group
- Click Start > All Programs > Veritas > Veritas Cluster Server > Configuration Tools > SQL Server Configuration Wizard to start the configuration wizard.
- Review the Prerequisites page and click Next.
- On the Wizard Options panel, click Edit service group, select the service group and then click Next.
- Click Yes on the VCS Notice informing you that the service is not completely offline. No adverse consequences are implied.
- In the Service Group Configuration page, click Next.
- In the SQL Server Instance Selection page, make sure the correct instance of SQL Server is selected and click Next.
- In the User Databases List page, make sure the databases are shown with correct paths and click Next.
- If a database is not configured correctly, a VCS warning appears indicating potential problems. Click OK to continue.
- In the Detail Monitoring and succeeding pages, review the information and click Next to continue.
- Click Yes to continue when a VCS Notice indicates the configuration will be modified.
- Click Finish to exit the wizard.
The wizard marks all the resources in the service group as CRITICAL. If desired, use Cluster Manager (Java Console) or the command line to change the state.