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 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
- 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. Configuring SQL Server in a VMware environment
- Configuring application monitoring using the Veritas High Availability solution
- Administering application monitoring
- About the various interfaces available for performing application monitoring tasks
- Administering application monitoring using the Veritas High Availability tab
- Understanding the Veritas High Availability tab work area
- To view the status of configured applications
- To configure or unconfigure application monitoring
- To start or stop applications
- To suspend or resume application monitoring
- To switch an application to another system
- To add or remove a failover system
- To clear Fault state
- To resolve a held-up operation
- To determine application state
- To remove all monitoring configurations
- To remove VCS cluster configurations
- Administering application monitoring settings
- Administering application availability using Veritas High Availability dashboard
- Understanding the dashboard work area
- Monitoring applications across a data center
- Monitoring applications across an ESX cluster
- Searching for application instances by using filters
- Selecting multiple applications for batch operations
- Starting an application using the dashboard
- Stopping an application by using the dashboard
- Entering an application into maintenance mode
- Bringing an application out of maintenance mode
- Switching an application
- Section IV. 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
- Troubleshooting application monitoring configuration issues
- Troubleshooting Veritas High Availability view issues
- Veritas High Availability tab not visible from a cluster node
- Veritas High Availability tab does not display the application monitoring status
- Veritas High Availabilitytab may freeze due to special characters in application display name
- Veritas High Availability view may fail to load or refresh
- Operating system commands to unmount resource may fail
- Appendix B. Using the virtual MMC viewer
- Appendix A. Troubleshooting
To add or remove a failover system
Each row in the application table displays the status of an application on the systems that are part of a VCS cluster in a VMware environment. The displayed system/s either form a single-system Cluster Server (VCS) cluster with application restart configured as a high-availability measure, or a multi-system VCS cluster with application failover configured. In the displayed cluster, you can add a new system as a failover system for the configured application.
The system must fulfill the following conditions:
Cluster Server (InfoScale Availability)8.0 is installed on the system.
The system is not part of any other VCS cluster.
The system has at least two network adapters.
The required ports are not blocked by a firewall.
The application is installed identically on all the systems, including the proposed new system.
To add a failover system, perform the following steps:
Note:
The following procedure describes generic steps to add a failover system. The wizard automatically populates values for initially configured systems in some fields. These values are not editable.
To add a failover system
- In the appropriate row of the application table, click More > Add Failover System.
- Review the instructions on the welcome page of the Veritas High Availability Configuration Wizard, and click Next.
- If you want to add a system from the Cluster systems list to the Application failover targets list, on the Configuration Inputs panel, select the system in the Cluster systems list. Use the Edit icon to specify an administrative user account on the virtual machine. You can then move the required system from the Cluster system list to the Application failover targets list. Use the up and down arrow keys to set the order of systems in which VCS agent must failover applications.
If you want to specify a failover system that is not an existing cluster node, on the Configuration Inputs panel, click Add System, and in the Add System dialog box, specify the following details:
System Name or IP address
Specify the name or IP address of the system that you want to add to the VCS cluster.
Domain/Username
Specify the user name with administrative privileges on the system.
Specify the user name must be in the domain.com\username format.
If you want to specify the same user account on all systems that you want to add, check the Use the specified user account on all systems box.
Password
Specify the password for the account you specified.
Use the specified user account on all systems
This option is checked by default. You cannot modify this setting.
The wizard validates the details, and the system then appears in the Application failover target list.
- Specify the user name and that VCS agents must use to perform domain operations such as Active Directory updates.
- If you are adding a failover system from the existing VCS cluster, the Network Details panel does not appear.
If you are adding a new failover system to the existing cluster, on the Network Details panel, review the networking parameters used by existing failover systems. Appropriately modify the following parameters for the new failover system.
Note:
The wizard automatically populates the networking protocol (UDP or Ethernet) used by the existing failover systems for Low Latency Transport communication. You cannot modify these settings.
To configure links over ethernet, select the adapter for each network communication link. You must select a different network adapter for each communication link.
To configure links over UDP, specify the required details for each communication link.
Network Adapter
Select a network adapter for the communication links.
You must select a different network adapter for each communication link.
Veritas recommends that one of the network adapters must be a public adapter and the VCS cluster communication link using this adapter is assigned a low priority.
Note:
Do not select the teamed network adapter or the independently listed adapters that are a part of teamed NIC.
IP Address
Select the IP address to be used for cluster communication over the specified UDP port.
Port
Specify a unique port number for each link. You can use ports in the range 49152 to 65535.
The specified port for a link is used for all the cluster systems on that link.
Subnet mask
Displays the subnet mask to which the specified IP belongs.
- If a virtual IP is not configured as part of your application monitoring configuration, the Virtual Network Details page is not displayed. Else, on the Virtual Network Details panel, review the following networking parameters that the failover system must use, and specify the NIC:
Virtual IP address
Specifies a unique virtual IP address.
Subnet mask
Specifies the subnet mask to which the IP address belongs.
Virtual name
Specifies a virtual name.
NIC
For each newly added system, specify the network adaptor that must host the specified virtual IP.
- If the newly added failover system is associated with a different ESX host as compared to other systems, then on Target ESX Details page, specify the ESX host of the newly added failover system. Also specify the administrative user account details associated with the ESX host.
Note:
If the application for which you are adding a failover system does not use storage attached directly to the ESX host, the wizard does not display this page.
If the new failover system runs on a different ESX host, or is configured to failover to another ESX host, specify that ESX host. To specify the ESX host, click Add ESX Host and on the Add ESX Host dialog box, specify the following details, and then click Next:
ESX host name or IP address
Specify the target ESX host name or IP address. The virtual machines can failover to this ESX host during vMotion.
Specify an ESX host that has the same mount points as those currently used by the application.
User name
Specify a user account for the ESX host. The user account must have administrator privileges on the specified ESX host.
Password
Specify the password that is associated with the user name you specified.
The wizard validates the user account and the storage details on the specified ESX host, and uses this account to move data disks during vMotion.
- On the Configuration Summary panel, review the VCS cluster configuration summary, and then click Next to proceed with the configuration.
- On the Implementation panel, the wizard adds the specified system to the VCS cluster, if it is not already a part. It then adds the system to the list of failover targets. The wizard displays a progress report of each task.
If the wizard displays an error, click View Logs to review the error description, troubleshoot the error, and re-run the wizard from the Veritas High Availability tab.
Click Next.
- On the Finish panel, click Finish. This completes the procedure for adding a failover system. You can view the system in the appropriate row of the application table.
Similarly you can also remove a system from the list of application failover targets.
Note:
You cannot remove a failover system if an application is online or partially online on the system.
To remove a failover system
- In the appropriate row of the application table, click More > Remove Failover System.
- On the Remove Failover System panel, click the system that you want to remove from the monitoring configuration, and then click OK.
Note:
This procedure only removes the system from the list of failover target systems, not from the VCS cluster. To remove a system from the cluster, use VCS commands. For details, see the Cluster Server Administrator's Guide.