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 the VCS agent for SQL Server FILESTREAM
The VCS agent for SQL Server FILESTREAM enables FILESTREAM storage for the specified SQL Server instance, monitors its status, and disables it. The agent makes FILESTREAM highly available in a clustered environment.
FILESTREAM enables SQL Server-based applications to store unstructured data, such as documents and images, on the file system.FILESTREAM integrates the SQL Server Database Engine with an NTFS file system by storing varbinary(max) binary large object (BLOB) data as files on the file system. Transact-SQL statements can insert, update, query, search, and back up FILESTREAM data. Win32 file system interfaces provide streaming access to the data.
Online | Enables FILESTREAM on the system. |
Offline | Disables FILESTREAM on the system. |
Monitor | Monitors FILESTREAM status on the system. If the agent is unable to query the status of FILESTREAM or if FILESTREAM is disabled on the system, the FILESTREAM resource in the application monitoring configuration faults. |
Clean | Cleans up the resource state after the resource fails to come online, fails to go offline, or fails to be detected as online even though it is in the ONLINE state. |
The agent for SQL Server FILESTREAM is configured as a resource of the SQLFilestream type.
type SQLFilestream (
static i18nstr ArgList[] = { InstanceName }
i18nstr InstanceName
)Table: VCS agent for SQL Server FILESTREAM - required attribute
Required attribute | Description |
|---|---|
Name: InstanceName Type: String Dimension: Scalar | Name of the SQL Server instance for which FILESTREAM is configured. If the value of this attribute is empty, the agent monitors the default SQL Server instance (MSSQLSERVER). Note: This attribute can take localized values. |