Storage Foundation and High Availability 8.0.1 Solutions Microsoft Clustering Solutions Guide for Microsoft SQL Server - Windows
- Introducing SFW solutions for a Microsoft cluster
- Planning for deploying SQL Server with SFW in a Microsoft cluster
- Workflows for deploying SQL Server with SFW in a Microsoft cluster
- Configuring SFW storage
- Tasks for configuring InfoScale Storage
- Planning for SFW cluster disk groups and volumes
- Considerations when creating disk groups and volumes for a campus cluster
- Considerations when creating volumes for a DR configuration using Volume Replicator replication
- Viewing the available disk storage
- Creating dynamic cluster disk groups
- Adding disks to campus cluster sites
- Creating dynamic volumes for high availability clusters
- Creating dynamic volumes for campus clusters
- Implementing a dynamic mirrored quorum resource
- Installing SQL Server and configuring resources
- Configuring disaster recovery
- Tasks for configuring the secondary site for disaster recovery for SQL Server
- Verifying the primary site configuration
- Creating a parallel environment for SQL Server on the secondary site
- Volume Replicator components overview
- Setting up security for Volume Replicator
- Creating resources for Volume Replicator
- Configuring Volume Replicator: Setting up an RDS
- Creating the RVG resource
- Setting the SQL server resource dependency on the RVG resource
- Normal Volume Replicator operations and recovery procedures
- Appendix A. Configure InfoScale Storage in an existing Microsoft Failover Cluster
Configuring the storage hardware and network
Use the following procedures to configure the hardware and verify DNS settings. Repeat this procedure for every node in the cluster.
To configure the hardware
- Install the required network adapters, and SCSI controllers or Fibre Channel HBA.
- Connect the network adapters on each system.
To prevent lost heartbeats on the private networks, and to prevent the Microsoft cluster from mistakenly declaring a system down, Veritas recommends disabling the Ethernet autonegotiation options on the private network adapters. Contact the NIC manufacturer for details on this process.
- Use independent hubs or switches for the private heartbeats. You can use cross-over Ethernet cables for two-node clusters.
- Verify that each system can access the storage devices. Verify that each system recognizes the attached shared disk and that the attached shared disks are visible.
To verify the DNS settings and binding order
- From the Control Panel, access the Network Connections window.
Ensure the public network adapter is the first bound adapter as follows:
From the Advanced menu, click Advanced Settings.
In the Adapters and Bindings tab, verify the public adapter is the first adapter in the Connections list. If necessary, use the arrow button to move the adapter to the top of the list.
- Ensure that DNS name resolution is enabled. Make sure that you use the public network adapter, and not those configured for the private network.
Do the following:
In the Network Connections window, double-click the adapter for the public network to access its properties. In the Public Status dialog box, on the General tab, click Properties.
In the Public Properties dialog box, on the General tab, select the Internet Protocol (TCP/IP) check box and click Properties.
Select the Use the following DNS server addresses option and verify the correct value for the IP address of the DNS server.
Click Advanced.
In the DNS tab, make sure the Register this connection's address in DNS check box is selected. Make sure the correct domain suffix is entered in the DNS suffix for this connection field.