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
Managing storage using NetApp filer
NetApp manages data by creating volumes on physical disks. These volumes can further be divided into LUNs (Logical Unit Numbers). The LUNs are accessible from the cluster nodes, provided the nodes have Microsoft iSCSI Initiator and NetApp SnapDrive installed. However, if you plan to use Fibre Channel (FC) for connecting the LUNs, ensure that filer is connected to the nodes and the LUNs are shared between all the cluster nodes.
Refer to the NetApp documentation for more information.
The following figure illustrates a typical VCS cluster in a NetApp storage environment.
The VCS agent for SQL Server requires two LUNs to be created on the NetApp filer, one for the SQL Server data and the other for the registry replication information.
If you are using SQL Server FILESTREAM, create additional LUNs for FILESTREAM-enabled database objects.
If you plan to configure an MSDTC service group, create additional volumes for MSDTC log and MSDTC registry replication. These LUNs must be accessible from all cluster nodes.
Veritas recommends that you create separate LUNs (virtual disks) for the following:
INST1_DATA_FILES
Contains the SQL Server system data files (including the master, model, msdb, and tempdb databases).
INST1_REGREP_VOL
Contains the list of registry keys that must be replicated among cluster systems for the SQL Service. Create a 100 MB (minimum recommended size) volume for this purpose.
INST1_FS_VOL
Contains FILESTREAM enabled database objects for the SQL database.
INST1_DB1_VOL
Contains the user database files.
INST1_DB1_LOG
Contains the user database log files.
INST1_DB1_FS_VOL
Contains FILESTREAM enabled database objects for the user database
These LUNs must be accessible from all cluster nodes.
Perform the following tasks to create LUNs on the NetApp filer and to make them accessible from cluster nodes:
Add the filer storage system to the SnapDrive Storage System Management snap-in on the cluster nodes.
Create volumes on the NetApp filer.
Share the volumes.
Create LUNs or virtual disks on the shared volumes.
Refer to NetApp documentation for instructions on performing these tasks.