This post was edited/updated on April 5, 2015.
In Part I of this series we covered the deployment of HP StoreVirtual VSA and the Centralized Management Console (CMC) on Hyper-V, Part II This post is dedicated to the configuration of the StoreVirtual VSA Cluster and Failover Manager, in Part III we will create our Hyper-V Cluster using Virtual Machine Manager, I know it’s a long series blog posts, but I want to make sure that we cover all the aspects of the Hyper-V Software-Defined Storage deployment.
So without further ado, we are in Step 3 in our deployment plan:
Let’s start the Centralized Management Console (CMC). If you did not see any system under “Available Systems”, click “Find” on the menu and then choose “Find Systems…”. A dialog box will appear. Click “Add…” and enter the IP address of one of the earlier deployed VSA nodes (HP-VSA01). Repeat this until all deployed VSA nodes are added. Then click “Close”. Now you should have all available VSA nodes listed under “Available Systems”.
A management group is a collection of one or more storage VSA systems. It is the container within which your cluster storage systems and create volumes for storage. Creating a management group is the first step in creating HP StoreVirtual VSA Storage. Right click on any node and choose “Add to New Management Group…” from the context menu. We will add two nodes (HP-VSA01 and HP-VSA02) into this new management group.
As you can see warning message! To ensure that we have the highest level of availability we need to install HP StoreVirtual Failover Manager (FOM).
HP StoreVirtual FOM is a specialized version of the LeftHand OS designed to run as a virtual appliance in a virtual environment. The HP StoreVirtual FOM participates in the management group as a manager in the system performing quorum operations only, not data movement operations. It is recommended for 2-node or Multi-Site configurations to maintain quorum without requiring any additional physical hardware.
IMPORTANT: You must Install the Failover Manager on network hardware other than the storage systems in the SAN to ensure that it is available for failover and quorum operations if a storage system in the SAN becomes unavailable.
Now If you don’t use Failover Manager, and you select “I understand that not using FOM…” a Virtual Manager is added to the management group by default, but is not started on a storage system until a failure in the system causes a loss of quorum. Unlike the Failover Manager, which is always running, the virtual manager must be started manually on a storage system after quorum is lost. It is designed to be used in two-systems or two-site system configurations which are at risk for a loss of quorum.
Note: A virtual manager requires manual intervention to recover quorum and can have undesirable effects when left running after quorum is recovered. Therefore, it’s highly recommended that you use the Failover Manager rather than the Virtual Manager.
OK, so having this explained and because I have only two VSA storage nodes, I will install HP StoreVirtual FOM on a third Hyper-V host and then repeat the cluster group wizard.
The installation of the Failover Manager for Hyper-V Server is straightforward:
Note: Before you start the installation, please make sure .NET Framework 3.5 (includes .NET 2.0 and 3.0) is installed on the Hyper-V host.
1. Insert the .iso image for HP StoreVirtual VSA and Failover Manager DVD.
2. Locate the applicable executable and double-click it to begin.
3. Click Agree to accept the terms of the License Agreement.
4. Choose a location for the Failover Manager virtual machine and a location for the virtual hard
disks, and click Next.
5. Enter the network information, including the host name and network addressing information, and click Next.
6. Enter a name for the Failover Manager, select whether you want it powered on after it is installed, and click Next.
- Finish the installation, reviewing the configuration summary, and click Next. When the installer is finished, the Failover Manager is ready to be used in the HP StoreVirtual Storage.
After the installation, click Find→Find Systems in the CMC and enter the Failover Manager IP address to discover the Failover Manager, and then add it to the management group, but before doing that let’s open Hyper-V Manager and check the settings of the StoreVirtual Failover Manager VM.
Now let’s create the Cluster Management Group again using the Centralized Management Console:
Click “Next”. On the next page of the wizard we have to enter a username and password for the administrator user, that will be added to all VSA nodes.
On the next page we need to provide NTP server. we can set the time manually, but a preferred NTP server is one that is more reliable, such as a server that is on a local network. An NTP server on a local network would have a reliable and fast connection to the storage system. They have to be reachable by the VSA nodes!
On the next page of the wizard, you have to provide information about the DNS Server: DNS domain name, additional DNS suffixes and one or more DNS servers. For the DNS servers the same applies as for the NTP server. They have to be reachable by the VSA nodes!
You can set up email notification for events for each management group. You must set up the email server to send events. You need the email (SMTP) server IP or host name, server port, and a valid email address to use as the sender address.
Now very important question: Standard or Multi-Site Cluster? A Multi-Site cluster incorporates different features to ensure site fault tolerance. You must have the same number of VSA storage systems in each of the data sites spanned by your Multi-Site cluster. I chose to create a standard cluster since we don’t have Multi-Site deployment
After choosing the cluster type, we have to provide a cluster name and the number of nodes, that should be member of this new cluster.
The next step is to configure the cluster Virtual IP address (Cluster VIP). This IP address has to be in the same subnet (VLAN) as the VSA nodes. This IP address is used to access the cluster. After the initial connection to the cluster VIP, the initiator will contact a VSA node for the data transfer.
A VIP is required for a fault-tolerant iSCSI cluster configuration, using VIP load balancing or the HP StoreVirtual DSM for Microsoft MPIO. When using a VIP, one storage system in the cluster hosts the VIP. All I/O goes through the VIP host. You can determine which storage system hosts the VIP by selecting the cluster, then clicking the iSCSI tab when the cluster is created.
Note: All iSCSI initiators (Hyper-V Hosts) must be configured to connect to the VIP address for the iSCSI failover to work properly.
The wizard allows us to create a volume. This step can be skipped and create the volume later, however I created two full provisioned volumes, one volume 5GB for Windows Failover Cluster Quorum and another one 195GB for Cluster Shared Volume.
After clicking “Finish” the management group and the cluster will be created. This steps could take some time.
At the end you will get a summary screen. You can create further volumes or you can repeat the whole wizard to create additional management groups or cluster.
Congratulations! You have now a fully functional HP StoreVirtual VSA cluster .
But wait we didn’t finish yet… we need to add the Hyper-V Hosts.
To present the volumes to the hosts, you have to add hosts. A host consist of a name, an IP address, and an iSCSI IQN and, if needed, CHAP credentials. Multiple hosts can be grouped to server clusters. You need at least two hosts to build a server cluster. But first of all, we will add the two Hyper-V hosts:
What is the Controlling Server IP Address to use?
When working with Hyper-V, it’s the Physical IP address required for each server hosting a VSS Provider in the Windows Failover Cluster. Since there is likely more than one LeftHand OS server in a Windows Failover Cluster, enter one physical IP address in each of the related LeftHand OS server dialogs.
With at least two hosts, you can create a server group. A server group simplifies the volume management, because you can assign and unassign volumes to a group of Hyper-V hosts with a single click. This ensures the consistency of volume presentations for a group of hosts.
Last but not least, we need to present the volumes, during the initial Cluster Management Group configuration we created two volumes 5GB and 195GB full-provisioned Network-RAID 10 volume. To assign the volumes to a server group, right-click the new server group in the CMC and click “Assign and Unassign Volumes…”. A window will popup and you can check or uncheck the volume and set the permission as Read-Only or Read-Write.
And here we go, we are nearly at the end. We only have to add the Cluster VIP to the iSCSI initiator on each Hyper-V host, initialize the disks and then create two volumes out of the presented volumes.
Part 3 will cover the configuration of the Hyper-V Cluster in VMM. If you have any question or feedback, please feel free to leave a comment below.
Thanks for reading.
Stay tuned… Until then, enjoy your day!