Free Webinar
November 15 | 11am PT / 2pm ET
VMware & StarWind: Guarantee data safety and constant applications availability
Speaker: Alexey Khorolets, Pre-Sales Engineer, StarWind

StarWind Virtual SAN® Compute and Storage Separated 2-Node Scenario with Windows Server 2016

Published: February 6, 2018

INTRODUCTION

StarWind Virtual SAN supports both architectures: hyper-converged and compute- and storage-separated. Running compute and storage layers separately make it possible to scale compute and storage resources independently.

This technical paper provides a detailed step-by-step guidance on configuring a 2-node Hyper-V Failover Сluster using StarWind Virtual SAN to turn storage resources of the separated servers into a fault-tolerant and fully redundant shared storage for Hyper-V environments.

The Failover Cluster configuration assumes that if one of the cluster nodes fails, the other nodes automatically take over resources, thus continuing serving the applications. Regarding this feature, the workflow remains uninterrupted and secured. Adding StarWind disks to CSVs provides efficient use of storage and simplifies its management, as well as enhances availability and increases resilience. Once it is done, you can start creating highly available virtual machines on them.

This guide is intended for experienced Windows system administrators and IT professionals who would like to configure the Hyper-V cluster using StarWind Virtual SAN to convert the clustered storage space into the fault-tolerant shared storage resource. It also highlights how to connect the StarWind HA devices to the Microsoft iSCSI initiator and configure the StarWind shared storage as the Cluster Shared Volumes.

A full set of up-to-date technical documentation can always be found here, or by pressing the Help button in the StarWind Management Console.

For any technical inquiries, please, visit our online community, Frequently Asked Questions page, or use the support form to contact our technical support department.

Pre-Configuring the Servers

The diagram below depicts the network architecture of the configuration described in this guide.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

NOTE: Additional network connections may be required depending on the cluster setup and applications that are running.

1. Make sure that cluster nodes are added to the domain.

2. Install Failover Clustering and Multipath I/O features, as well as the Hyper-V role on cluster nodes. This can be done through Server Manager (Add Roles and Features menu item).

3. Configure network interfaces on each node to make sure that Synchronization and iSCSI/StarWind heartbeat interfaces are in different subnets and connected as it is shown in the network diagram above.

In this document, 172.16.10.x and 172.16.20.x subnets are used for iSCSI/StarWind Heartbeat traffic while 172.16.30.x and 172.16.40.x subnets are used for the Synchronization traffic.

4. In order to allow iSCSI Initiator to discover all StarWind Virtual SAN interfaces, StarWind configuration file (StarWind.cfg) should be changed after stopping StarWind service.

Locate the StarWind Virtual SAN configuration file (the default path is: C:\Program Files\StarWind Software\StarWind\StarWind.cfg) and open it with Wordpad as Administrator.

Find the string < iScsiDiscoveryListInterfaces value=”0” />; and change the value from 0 to 1 (should look as follows: < iScsiDiscoveryListInterfaces value=”1” />;). Save the changes and exit Wordpad. Once StarWind.cfg has been changed and saved, StarWind service can be started.

Please note, this tip can be used only for Windows-based compute nodes.

Enabling Multipath Support

1. On the compute nodes, open the MPIO manager: Start->Administrative Tools>MPIO.

2. Go to the Discover Multi-Paths tab.

3. Tick the Add support for iSCSI devices checkbox and click Add.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

4. When it is prompted to restart the server, click Yes to proceed.

NOTE: Repeat the procedure on the second cluster node.

Downloading, Installing, and Registering the Software

5. Download the StarWind setup executable file from StarWind website by following the link below:

https://www.starwind.com/registration-starwind-virtual-san

NOTE: The setup file is the same for x86 and x64 systems, as well as for all Virtual SAN deployment scenarios.

6. Launch the downloaded setup file on the server where StarWind Virtual SAN or one of its components need to be installed. The setup wizard appears.

7. Read and accept the License Agreement.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next to continue.

8. Read the information about new features and improvements carefully.

Red text indicates warnings for users who are updating existing software installations.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next to continue.

9. Click Browse to modify the installation path if necessary.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next to continue.

10. Select the following components for the minimum setup:

  • StarWind Virtual SAN service. StarWind service is the “core” of the software. It can create iSCSI targets as well as share virtual and physical devices. The service can be managed from StarWind Management Console on any Windows computer or VSA connected to the network. Alternatively, the service can be managed from StarWind Web Console and deployed separately.
  • StarWind Management Console. The Management Console is the Graphic User Interface (GUI) part of the software that controls and monitors all storage-related operations (e.g., allows users to create targets and devices on StarWind Virtual SAN servers connected to the network).

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next to continue.

11. Specify the Start Menu folder.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next to continue.

12. Enable the checkbox to create a desktop icon.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next to continue.

13. There is an option to request a time-limited fully functional evaluation key, or a FREE version key, or a fully commercial license key sent to you with the purchase of StarWind Virtual SAN. Select the appropriate one.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next to continue.

14. Click Browse to locate the license file.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next to continue.

15. Review the licensing information.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next to apply the license key.

16. Verify the installation settings. Click Back to make any changes or Install to continue.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

17. Select the appropriate checkbox to launch the StarWind Management Console right after the setup wizard is closed.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Finish to close the wizard.

18. Repeat the installation steps on the partner node.

Configuring Shared Storage

19. Launch StarWind Management Console by double-clicking the StarWind tray icon.

NOTE: StarWind Management Console cannot be installed on a GUI-less OS. You can install the Console on any GUI-enabled Windows editions, including a desktop version of Windows.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

If StarWind Service and Management Console are installed on the same server, the Management Console automatically adds the local StarWind instance to the Console tree after the first launch. Then, the Management Console automatically connects to the

StarWind service using the default credentials. To add remote StarWind servers to the Console, use the Add Server button on the control panel.

20. StarWind Management Console will ask to specify a default storage pool on the server you connect to for the first time. Please, configure the storage pool to use one of the volumes you have prepared earlier. All the devices created through the Add Device wizard are stored in the configured storage pool. Should you decide to use an alternative storage path for your StarWind virtual disks, please use the Add Device (advanced) menu item.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Press the Yes button to configure the storage pool. Should you require to change the storage pool destination, press Choose path… and point to the necessary disk in the browser.

NOTE: Each array that will be used by StarWind Virtual SAN to store virtual disk images should meet the following requirements:

  • Initialized as GPT;
  • NTFS-formatted partition;
  • Assigned drive letter.

21. Select the StarWind server where the device intends to be created.

22. Press the Add Device (advanced) button on the toolbar.

23. Select Hard Disk Device in Add Device Wizard and click Next.

24. Select a Virtual disk and click Next.

25. Specify the virtual disk name, location, size and click Next.

Below, you can find how to prepare an HA device for a Witness drive. Devices for Cluster Shared Volumes (CSV) should be created the same way.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

26. Specify virtual disk options.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next.

27. Define the caching policy, specify the cache size, and click Next.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

NOTE: It is recommended to put 1 GB of L1 cache in the Write-Back mode per 1 TB storage capacity.

28. Define optional Flash Cache Parameters policy and size if necessary. Choose an SSD location in the wizard. Click Next to continue.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

NOTE: The recommended size of the L2 cache is 10% of the initial StarWind device size.

29. Specify target parameters.

Target Name is generated automatically based on the target alias. Additionally, custom name of the target can be assigned. Click Next to continue.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

30. Click Create to add a new device and attach it to the target. Then, click Close.

31. Right-click the servers field and select Add Server. Add a new StarWind server which will be used as the second HA node.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click OK and the Connect button to continue.

32. Right-click the recently created device and select Replication Manager.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Press the Add Replica button in the Replication Manager window.

33. Select Synchronous two-way replication and click Next to proceed.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

34. Specify the partner server IP address.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

The default StarWind management port is 3261. If you have configured a different port, please type it in the Port number field. Click Next.

35. Select Heartbeat as the Failover Strategy and click Next.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

36. Choose Create new Partner Device and click Next.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

37. Specify the partner device location if necessary. You can additionally modify the target name of the device.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next.

38. Specify the synchronization and heartbeat channels for the HA device on this screen. You can also modify the ALUA settings.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Change network settings.

39. Specify the interfaces for synchronization and Heartbeat.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click OK. Then click Next.

NOTE: It is recommended to configure the Heartbeat and iSCSI channels on the same interfaces to avoid the split-brain issue.

40. Select Synchronize from existing Device as a partner device initialization mode and click Next.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

41. Press the Create Replica button and click Close.

42. The added device will appear in StarWind Management Console.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Repeat the steps above for the remaining virtual disks used as Cluster Shared Volumes. Once all devices are created, the Management console should look as in the image below:

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Discovering Target Portals

This part describes how to discover Target Portals from each StarWind node on each Cluster node.

43. Launch Microsoft iSCSI Initiator on Cluster Node 1:

Start > Administrative Tools > iSCSI Initiator or iscsicpl from the command line interface. The iSCSI Initiator properties window appears.

44. Navigate to the Discovery tab. Click the Discover Portal button.

In Discover Target Portal dialog, enter iSCSI IP address of the first StarWind Node

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click the Advanced button.

45. Select Microsoft iSCSI Initiator as Local adapter and select Cluster Node 1 initiator IP address from the same subnet. Click OK twice to add the Portal.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

46. Click the Discover Portal button once again.

47. In Discover Target Portal dialog, enter the second iSCSI IP address of the first StarWind Node and click the Advanced button.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

48. Select Microsoft iSCSI Initiator as Local adapter and select Cluster Node 1 initiator IP address from the same subnet. Click OK twice to add the Portal.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

49. Target portals are added from the first StarWind Node.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

50. To Discover Target Portals from the second StarWind Node, click the Discover Portal button once more, enter iSCSI IP address for the second StarWind Node, and Click the Advanced button.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

51. Select Microsoft iSCSI Initiator as Local adapter and select Cluster Node 1 initiator IP address from the same subnet. Click OK twice to add the Portal.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

52. Choose the Discover Portal button once again. In Discover Target Portal dialog, enter the second iSCSI IP address of the second StarWind Node. Click the Advanced button.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

53. Select Microsoft iSCSI Initiator as Local adapter and select Cluster Node 1 initiator IP address from the same subnet. Click OK twice to add the Portal.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

54. All target portals are successfully added to the Cluster Node 1.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

55. Perform the steps of this part on the Cluster Node 2. All target portals added to the Cluster Node 2 should look like in the picture below.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Connecting Targets

56. Launch Microsoft iSCSI Initiator on Cluster Node 1 and click on the Targets tab. The previously created targets should be listed in the Discovered Targets section.

NOTE: If the created targets are not listed, check the firewall settings of the StarWind Server as well as the list of networks served by the StarWind Server (go to StarWind Management Console -> Configuration -> Network).

57. Select a target discovered from the first StarWind Node and click Connect.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

58. Enable checkboxes like in the image below and click Advanced.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

59. Select Microsoft iSCSI Initiator in the Local adapter text field.

60. In the Target portal IP, select the IP address of the first StarWind Node and Initiator IP address from the same subnet. Click OK twice to connect the target.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

61. To connect the same target via another subnet, select it one more time and click Connect.

62. Enable checkboxes like in the image below and click Advanced.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

63. Select Microsoft iSCSI Initiator in the Local adapter text field.

64. In the Target portal IP, select another IP address of the first StarWind Node and Initiator IP address from the same subnet. Click OK to connect the target.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

65. Select the partner target discovered from the second StarWind node and click Connect.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

66. Enable checkboxes like it is shown in the image below and click Advanced.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

67. Select Microsoft iSCSI Initiator in the Local adapter text field.

68. In Target portal IP, select the IP address of the second StarWind Node and Initiator IP address from the same subnet. Click OK twice to connect the target.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

69. To connect the same target via another subnet, select it one more time and click Connect.

70. Enable checkboxes like in the image below and click Advanced.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

71. In the Target portal IP, select another IP address of the second StarWind Node and Initiator IP address from the same subnet. Click OK to connect the target.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

72. Repeat the above actions for all HA device targets.

After that, repeat the steps described in this section on the Cluster node 2, specifying corresponding IP addresses. The result should look like in the picture below.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

73. Initialize the disks and create partitions using the Disk Management snap-in. To create the cluster, the disk devices must be initialized and formatted on both nodes.

NOTE: it is recommended to initialize the drives as GPT.

Creating a Cluster

NOTE: To avoid issues during cluster configuration validation, it is recommended to install the latest Microsoft updates on each node.

74. Open Server Manager. Select the Failover Cluster Manager item from the Tools menu.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

75. Click the Create Cluster item in the Actions section of the Failover Cluster Manager.

Specify the servers that need to be added to the cluster. Click Next to continue.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

76. Verify that your servers are suitable for building a cluster. Select “Yes…” and click Next.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

77. Specify the cluster name.

NOTE: If the cluster servers get IP addresses over DHCP, the cluster also gets its IP address over DHCP. If the IP addresses are set statically, you need to set the cluster IP address manually.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Next to continue.

78. Make sure that all of the settings are correct. Click Previous to make any changes. Click Next to continue.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

79. The cluster creation process starts. Upon completion, the system displays the report with detailed information.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Click Finish to close the wizard.

Adding Cluster Shared Volumes

Follow these steps to add Cluster Shared Volumes (CSV) that is necessary for working with Hyper-V virtual machines:

80. Open Failover Cluster Manager.

81. Go to Cluster->Storage -> Disks.

82. Click Add Disk in the Actions panel, choose the disks from the list and click OK.

83. To configure a Witness drive, right-click the Cluster->More Actions->Configure Cluster Quorum Settings, follow the wizard, and use the default quorum configuration.

84. Right-click the required disk and select Add to Cluster Shared Volumes.

StarWind Virtual SAN<sup>®</sup> Compute and Storage Separated 2 Node Scenario with Windows Server 2016

Once the disks are added to the Cluster Shared Volumes list, you can start creating the highly available virtual machines on them.

NOTE: To avoid the unnecessary CSV overhead, configure each CSV to be owned by one Cluster node. This node should also be the preferred owner of the VMs it runs.

CONCLUSION

The cluster increases availability of the services or applications on it. CSV feature simplifies the storage management by allowing multiple VMs to be accessed from a common shared disk. Resilience is provided by creating multiple connections between StarWind nodes and the shared disk. Thus, if one of the nodes goes down, another one will take over the production operations.