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 Windows Logical Disk Manager
If your configuration uses shared disks and volumes that are managed using Windows Logical Disk Manager (LDM), use the VCS Mount and DiskReservation (DiskRes) agents. If you use LDM to manage non-shared local storage, use the VCS Mount and NativeDisks agents.
Before configuring the storage, review the resource types and attribute definitions of these VCS storage agents (Mount, DiskRes, NativeDisks) described in the Cluster Server Bundled Agents Reference Guide.
The following restrictions apply for storage managed using LDM:
Mount, DiskRes, and NativeDisks agents are supported on VCS for Windows only. These agents are not supported if the storage is managed using Storage Foundation (SFW).
If you are using shared storage, your storage devices must be configured to use SCSI-2 disk reservations. SCSI-3 is not supported.
SCSI support is not required if you are using non-shared storage.
LDM support is not applicable for Disaster Recovery configurations. Currently only HA configurations are supported.
The VCS agent for SQL Server requires that you create two volumes, one for SQL Server data and the other for the registry replication information.
If you are using SQL Server FILESTREAM, create additional volumes for FILESTREAM enabled database objects.
If you will plan to configure an MSDTC service group, create additional volumes for MSDTC log and MSDTC registry replication.
Veritas recommends that you create separate volumes 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.
If you are using a shared storage configuration, ensure that these volumes are created on shared storage and are accessible from all cluster nodes.
If you are using a non-shared storage configuration, create these volumes separately on the local storage attached to each cluster node.
Perform the following tasks to configure your storage:
Reserve disks
Create volumes
Mount volumes
Unassign the drive letter
Release the disks