Step 2: Set Up Shared Storage for Servers for the Head Node
Applies To: Microsoft HPC Pack 2012, Microsoft HPC Pack 2012 R2
Use the following instructions to connect the networks and storage for the servers that will be placed in a failover cluster that supports head node services. Also use the instructions if you are installing a SQL Server failover cluster (rather than a standalone SQL Server).
For a failover cluster network, avoid having single points of failure. To accomplish this with HPC Pack, use one of the network topologies that is not public-only, that is, choose from Topology 1 through 4 (not Topology 5). These topologies connect your head node by multiple, distinct networks. If you use a network for iSCSI, create this network in addition to the other networks. For more information, see Requirements for HPC Pack in Failover Clusters.
For each failover cluster, when you connect the servers for the head node to the failover cluster storage, expose at least two volumes (LUNs). You can expose additional volumes as needed to test your configuration.
Important
Expose each volume (LUN) only to a set of servers that will be in a single failover cluster.
To connect servers to networks and storage
Review the details about networks in the Hardware requirements section in Requirements for HPC Pack in Failover Clusters.
Connect and configure the networks that connect the servers that will run head node services.
Follow the manufacturer's instructions for physically connecting the servers to the storage.
Ensure that the disks (LUNs) that you want to use in this failover cluster are exposed to the servers that will be in this failover cluster (and only those servers). You can use an interface such as the following to expose disks or LUNs:
The interface that is provided by the manufacturer of the storage
If you are using iSCSI, an appropriate iSCSI interface
Microsoft Storage Manager for SANs (part of the operating system in Windows Server 2008 R2). To use this interface, you need to contact the manufacturer of your storage for a Virtual Disk Service (VDS) provider package that is designed for your storage.
If you have purchased software that controls the format or function of the disk, follow instructions from the vendor about how to use that software with Windows Server. Host bus adapters and multipath I/O software can be version sensitive. If you are implementing a multipath solution for your cluster, work closely with your hardware vendor to choose the correct adapters, firmware, and software for Windows Server.
On a server that you want to include in this failover cluster, in Disk Management, confirm that the cluster disks are visible.
Format the volumes that the failover cluster will use, using a file system supported by failover clusters in your version of Windows Server.
If you will be installing a SQL Server failover cluster (rather than a standalone SQL Server), repeat this procedure for the servers in the SQL Server cluster.
Additional references
Step 3: Set Up Failover Clustering and File Services for Servers that Will Run the Head Node