Free Webinar
October 3 | 11am PT / 2pm ET
Disaster Recovery 101
Hyper-V and vSphere
Speaker: Oleg Pankevych, Solutions Engineer, StarWind

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

Introduction to StarWind Virtual SAN for Hyper-V

StarWind Virtual SAN® is a native Windows hypervisor-centric hardware-less VM storage solution. It creates a fully fault-tolerant and high performing storage pool built for the virtualization workloads by mirroring the existing server’s storage and RAM between the participating storage cluster nodes. The mirrored storage resources are then connected to all cluster nodes and treated just as a local storage by all hypervisors and clustered applications. High Availability (HA) is achieved by providing multipath access to all storage nodes. StarWind Virtual SAN® delivers supreme performance compared to any dedicated SAN solution since it runs locally on the hypervisor and all I/O is processed by local RAM, SSD cache, and disks. This way it never gets bottlenecked by storage fabric.

StarWind VSAN for Hyper-V System Requirements

Prior to installing StarWind Virtual SAN for Hyper-V, please make sure that the system meets the requirements, which are available via the following link: https://www.starwindsoftware.com/system-requirements

Please read StarWind Virtual SAN Best Practices document for additional information: https://www.starwindsoftware.com/resource-library/starwind-virtual-san-best-practices

Pre-configuring the Windows Server 2016 Hosts

The network interconnection diagram is demonstrated below:

Interconnection diagram

1. Make sure that a domain controller is configured and the servers are added to the domain.
NOTE: Please follow the recommendation in KB article on how to place a DC in case of StarWind Virtual SAN usage.
2. Install Failover Clustering and Multipath I/O features, as well as the Hyper-V role on both cluster nodes. This can be done through the 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 according to the network diagram above. In this document, 172.16.10.x subnet is used for iSCSI/StarWind heartbeat traffic, while 172.16.20.x subnet is used for the Synchronization traffic.
4. In order to allow iSCSI Initiators to discover all StarWind Virtual SAN interfaces, the StarWind configuration file (StarWind.cfg) should be changed after stopping the StarWind service on the node where it will be edited. Locate the StarWind Virtual SAN configuration file (the default path is “C:\Program Files\StarWind Software\StarWind\StarWind.cfg”) and open it via WordPad as Administrator. Find the <iScsiDiscoveryListInterfaces value=”0”/> string and change the value from 0 to 1 (should look as follows: <iScsiDiscoveryListInterfaces value=”1”/>). Save the changes and exit Wordpad. Once StarWind.cfg is changed and saved, the StarWind service can be restarted.

Enabling Multipath Support
5. Open the MPIO Properties manager: Start -> Windows Administrative Tools -> MPIO. Alternatively, run the following PowerShell command:

6. In the Discover Multi-Paths tab, choose the Add support for iSCSI devices checkbox and click Add.

mpio properties

7. When prompted to restart the server, click Yes to proceed.
8. Repeat the same procedure on the other server.

Automated Storage Tiering Configuration

In case of using Automated Storage Tiering, the disks can be connected into OS directly in Pass-through mode or preconfigured into separate SSDs and HDDs RAID arrays, and then connected into OS.

NOTE: Simple Tier has no redundancy and in case of disk failure there is a risk of losing the data. It is recommended to configure resilient RAID arrays and use them as underlying storage for the Tier.

Automated Storage Tier creation

There are two ways to configure Automated Storage Tiering. It can be done via Server Manager and via the PowerShell console.

The first level of Storage Tier is Storage pools. At this level, separate physical disks are united into a single pool, providing the ability to flexibly expand the capacity and delegate administration.

The upper level is Storage Spaces. At this level, virtual disks are created using the available capacity of a storage pool. Storage Spaces feature the following characteristics: resiliency level, storage tiers, fixed provisioning, and precise administrative control.

1. Launch Server Manager->File and Storage Services->Volumes->Storage Pools. All disks available for Storage Pool are listed in Physical Disks. Click New Storage Pool.

Server Manager

NOTE:

is a PowerShell command that allows checking the disks available for Storage Pool.

is a PowerShell command that allows checking the parameters of physical disks.

2. Specify a Storage Pool name:

Storage Pool

3. Select the disks for Storage Pool and then press Next. In case of using Storage Tiers with both SSDs and HDDs, all these disks need to be added into the Storage Pool.

Phisical disk for the storage pool

4. Confirm the correct settings and click Create to create Storage Pool.

NOTE: In case of creating Storage Pool from RAID arrays, the MediaType parameter should be assigned manually. It can be done with the following PowerShell commands:

Assign SSD MediaType for the disk with size less than [ ]GB:

Assign HDD MediaType for the disk with size more than [ ]GB:

Additionally, the following commands can be used:

or

5. The next step is to create a virtual disk on the storage pool. It is possible to create multiple virtual disks that exist in the storage pool and then create multiple volumes that exist in each virtual disk. Create new virtual disk by right-clicking on the storage pool and selecting New Virtual Disk.

Server manager

6. For Automated Storage Tiering, both HDD- and SSD-based disks or RAID arrays should be in the storage pool to make use of Storage Tiers. In case of using Storage Tiers, Storage Layout can be only Simple and Mirror. Specify Virtual Disk Name and select Create storage tiers on this virtual disk.

Virtual Disk Name

NOTE: Simple Tier has no redundancy and in case of disk failure there is a risk of losing the data. It is recommended to configure resilient RAID arrays from disks and use them as an underlying storage for the Tier.

7. Select the storage layout type. Under the Simple layout, the data is striped across physical disks. This would be equivalent to a RAID-0 configuration. In case of using at least two disks, the Mirror configuration can be configured. The Mirror is equivalent to RAID-1. Once done, click next.

Storage Layout

8. Specify the provisioning type.

Fixed. This provision type means that virtual disk cannot exceed the actual storage pool capacity.

Thin. This provision type means that there is a possibility to create a volume with a size exceeding the storage pool capacity and then add physical disks later.

Choose fixed disk provisioning since this type is required by Storage Tiers. Click Next.

9. Specify the size of the Virtual Disk.

Size of the virtual disk

NOTE: At least 8 GB of free space on each Tier should be provisioned to allow Automated Storage rebuilding in case of the disk loss.

10. Confirm the settings and click Create to create Virtual Disk.

NOTE: In case of using both SSD and HDD disks or RAID arrays, automated Storage Tier consists of the so-called “hot” and “cold” Tiers. Automated Storage Tier elaborates a data map taking into account how often the certain data is used, thus defining how hot separate data blocks are. During the process of optimization that is launched automatically every day, the hot data, i.e. data that is used on the most frequent basis, is transferred to the fast SSD tier, with the data used less frequently, the so called cold data, being transferred to the slower HDD tier.

As the SSD tier based data gets updated only once a day, it is possible to manually optimize it with the help of the following CMD one-liner:

This command should be run on all cluster nodes, as it optimizes only those virtual disks the owner node for which is the one where the command is running.

For certain files, it can be optimal to permanently stay on the SSD tier. An example is a VHDX file that is accessed frequently and requires minimum latency and high performance. Such result can be achieved by pinning the file to the SSD tier.

The following recommendations should be taken into account before running the command:

  • The command should be run from the node owning the storage (Cluster Shared Volume) with the file stored on it.
  • Local path to the storage (Cluster Shared Volume) on the node should be used.

After a file is pinned, it will stay in the tier until the next optimization process triggered either automatically or manually.

To pin files to the SSD tier, run the following PowerShell command:

To unpin files from the SSD tier, run the following PowerShell command:

The below PowerShell command lists all files that are currently pinned:

11. Create a New Volume using New Volume Wizard:

Server manager

12. Select the server and disk and click Next.

13. Select the file system settings and click Next to proceed.

System Setting

NOTE: The steps described above can be performed with help of PowerShell commands. Also, with help of PowerShell, additional parameters can be configured for better performance:

Set 64K size of interleave: Interleave 65536.

Set LogicalSectorSizeDefault 4096 instead of default 512.

The cache size can be changed with the help of –WriteCacheSize [ ]GB parameter. It is possible to set cache size only via PowerShell commands for creating Automated Storage Tier.

Set SSD tier in two-way mirror: ResiliencySettingName Mirror -NumberOfDataCopies 2

The number of threads can be set with -NumberOfColumns parameter. The recommended number is the number of SSDs divided by 2.

The example of the PowerShell commands for Storage Pool and Virtual Disk with Tiered Storage creation is provided below:

The operations specified in this section should be performed on each server.

Installing File Server Roles

Please follow the steps below if file shares configuration is required

Scale-Out File Server (SOFS) for application data

1. Open Server Manager: Start -> Server Manager
2. Select: Manage -> Add Roles and Features
3. Follow the installation wizard steps to install the roles selected in the screenshot below:

StarWind - Select Server Role

4. Restart the server after installation is completed and perform steps above on the each server.

File Server for general use with SMB share

1. Open Server Manager: Start -> Server Manager
2. Select: Manage -> Add Roles and Features
3. Follow the installation wizard steps to install the roles selected in the screenshot below:

StarWind - Select Server Role

4. Restart the server after installation is completed and perform steps above on each server.

File Server for general use with NFS share

1. Open Server Manager: Start -> Server Manager
2. Select: Manage -> Add Roles and Features
3. Follow the installation wizard steps to install the roles selected in the screenshot below:

StarWind Select Role NFS

4. Restart the server after installation is completed and perform steps above on each server.

Installing StarWind VSAN for Hyper-V

1. Download the StarWind setup executable file from the StarWind website:
https://www.starwind.com/registration-starwind-virtual-san

2. Launch the downloaded setup file on the server to install StarWind Virtual SAN or one of its components. The Setup wizard will appear. Read and accept the License Agreement.
StarWind License agreement
3. Carefully read the information about the new features and improvements. Red text indicates warnings for users that are updating the existing software installations.
4. Select Browse to modify the installation path if necessary. Click on Next to continue.
select destination location
5. Select the following components for the minimum setup:

  • StarWind Virtual SAN Service. The StarWind Virtual SAN 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 that is on the same network. Alternatively, the service can be managed from StarWind Web Console deployed separately.
  • StarWind Management Console. 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).

NOTE: To manage StarWind Virtual SAN installed on a Windows Server Core edition with no GUI, StarWind Management Console should be installed on a different computer running the GUI-enabled Windows edition.

6. Specify Start Menu Folder.
Select start menu folder
7. Enable the checkbox if a desktop icon needs to be created. Click on Next to continue.
8. When the license key prompt appears, choose the appropriate option:

  • Request time-limited fully functional evaluation key.
  • Request FREE version key.
  • Select the previously purchased commercial license key.

9. Click on the Browse button to locate the license file.
10. Review the licensing information.
11. Verify the installation settings. Click on Back to make any changes or Install to proceed with installation.
12. Enable the appropriate checkbox to launch StarWind Management Console right after the setup wizard is closed and click on Finish.
13. Repeat the installation steps on the partner node.

Select the Required Replication Mode

The replication can be configured in one of two modes:

Synchronous “Two-Way” Replication
Synchronous or active-active replication ensures real-time synchronization and load balancing of data between two or three cluster nodes. Such a configuration tolerates the failure of two out of three storage nodes and enables the creation of an effective business continuity plan. With synchronous mirroring, each write operation requires control confirmation from both storage nodes. It guarantees the reliability of data transfers but is demanding in bandwidth since mirroring will not work on high-latency networks.

Asynchronous “One-Way” Replication
Asynchronous Replication is used to copy data over a WAN to a separate location from the main storage system. With asynchronous replication, confirmation from each storage node is not required during the data transfer. Asynchronous replication does not guarantee data integrity in case of storage or network failure; hence, some data loss may occur, which makes asynchronous replication a better fit for backup and disaster recovery purposes where some data loss is acceptable. The Replication process can be scheduled in order to prevent the main storage system and network channels overloads.
Please select the required option:

Synchronous “Two-Way” replication

1. Select Synchronous “Two-Way” replication as a replication mode.

2. Specify a partner Host name or IP address and Port Number.

Asynchronous "One-Way" Replication

NOTE: Asynchronous replication requires minimum 100 MbE network bandwidth or higher. The Asynchronous node uses the LSFS device by design. Please, make sure that the Asynchronous node meets the LSFS device requirements:
https://knowledgebase.starwindsoftware.com/explanation/lsfs-container-technical-description/
1. Select Asynchronous “One-Way” Replication.
wp-image-12410
2. Enter Host name or IP address of the Asynchronous node.
3. Choose the Create New Partner Device option.
4. Specify the partner device Location . Optionally, modify the target name by clicking the appropriate button.
5. Click Change Network Settings.
6. Specify the network for asynchronous replication between the nodes. Click OK and then click Next.
7. In Select Partner Device Initialization Mode, select Synchronize from existing Device and click Next.
8. Specify Scheduler Settings and click Next.
NOTE: The size of journal files and number of snapshots depends on the settings specified in this step.
9. Specify the path for journal files and click Next.
NOTE: By default, the journal files will be located on the node with the original device. However, it is highly recommended not to store journal files on the same drive where the original device is located. Additionally, the C:\ drive should not be used as the path for journal files to avoid any issues with Windows OS.
If the same drive where the StarWind device is located is selected, the warning message about possible performance issues will pop up. If there is no additional volume available for storing the journals, click I understand the potential problem. Use the selected path.
wp-image-12419
10. Press the Create Replica button.
11. Wait until StarWind service creates a device and click Close to complete the device creation.

Selecting the Failover Strategy

StarWind provides 2 options for configuring a failover strategy:

Heartbeat
The Heartbeat failover strategy allows avoiding the “split-brain” scenario when the HA cluster nodes are unable to synchronize but continue to accept write commands from the initiators independently. It can occur when all synchronization and heartbeat channels disconnect simultaneously, and the partner nodes do not respond to the node’s requests. As a result, StarWind service assumes the partner nodes to be offline and continues operations on a single-node mode using data written to it.
If at least one heartbeat link is online, StarWind services can communicate with each other via this link. The device with the lowest priority will be marked as not synchronized and get subsequently blocked for the further read and write operations until the synchronization channel resumption. At the same time, the partner device on the synchronized node flushes data from the cache to the disk to preserve data integrity in case the node goes down unexpectedly. It is recommended to assign more independent heartbeat channels during the replica creation to improve system stability and avoid the “split-brain” issue.
With the heartbeat failover strategy, the storage cluster will continue working with only one StarWind node available.

Node Majority
The Node Majority failover strategy ensures the synchronization connection without any additional heartbeat links. The failure-handling process occurs when the node has detected the absence of the connection with the partner.
The main requirement for keeping the node operational is an active connection with more than half of the HA device’s nodes. Calculation of the available partners is based on their “votes”.
In case of a two-node HA storage, all nodes will be disconnected if there is a problem on the node itself, or in communication between them. Therefore, the Node Majority failover strategy requires the addition of the third Witness node which participates in the nodes count for the majority, but neither contains data on it nor is involved in processing clients’ requests. In case an HA device is replicated between 3 nodes, no Witness node is required.
With Node Majority failover strategy, failure of only one node can be tolerated. If two nodes fail, the third node will also become unavailable to clients’ requests.
Please select the required option:

Heartbeat

1. Select Failover Strategy.

2. Select Create new Partner Device and click Next.
3. Select a partner device Location.
4. Click Change Network Settings.

5. Specify the interfaces for Synchronization and Heartbeat Channels. Click OK and then click Next.
sync channels6. In Select Partner Device Initialization Mode, select Synchronize from existing Device and click Next.
7. Click Create Replica. Click Finish to close the wizard.
The successfully added device appears in StarWind Management Console.
8. Follow the similar procedure for the creation of other virtual disks that will be used as storage repositories.

Node Majority

1. Select the Node Majority failover strategy and click Next.
Node Majority2. Choose Create new Partner Device and click Next.
3. Specify the partner device Location and modify the target name if necessary. Click Next.
4. In Network Options for Replication, press the Change network settings button and select the synchronization channel for the HA device.
5. In Specify Interfaces for Synchronization Channels, select the checkboxes with the appropriate networks and click OK. Then click Next.
6. Select Synchronize from existing Device as the partner device initialization mode.
7. Press the Create Replica button and close the wizard.
8. The added devices will appear in StarWind Management Console.
Repeat the steps above to create other virtual disks if necessary.

Adding Witness Node
Witness node can be configured on a separate host or as a virtual machine in a cloud. It requires StarWind Virtual SAN service installed on it.
NOTE: Since the device created in this guide is replicated between 2 active nodes with the Node Majority failover strategy, a Witness node must be added to it.
1. Open StarWind Management Console, right-click on the Servers field and press the Add Server button. Add a new StarWind Server which will be used as the Witness node and click OK.
witness node2. Right-click on the HA device with the configured Node Majority failover policy and select Replication Manager and press the Add Replica button.
3. Select Witness Node.
witness node
4. Specify the Witness node Host Name or IP address. The default Port Number is 3261.
Ad partner node
5. In Partner Device Setup, specify the Witness device Location. Optionally, modify the target name by clicking the appropriate button.
6. In Network Options for Replication, select the synchronization channel with the Witness node by clicking the Change Network Settings button.
7. Specify the interface for Synchronization and Heartbeat and click OK.
8. Click Create Replica and then close the wizard.
9. Repeat the steps above to create other virtual disks if necessary.

NOTE: To extend an Image File or a StarWind HA device to the required size, please check the article below:

How to extend Image File or High Availability device

Provisioning StarWind HA Storage to Windows Server Hosts

1. Launch Microsoft iSCSI InitiatorStart -> Windows Administrative Tools -> iSCSI Initiator. Alternatively, launch it using the command below in the command line interface:

2. Navigate to the Discovery tab.
3. Click the Discover Portal button. The Discover Target Portal dialog appears. Type 172.16.30.10discover target portal node1Click the Advanced button.
4. 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.csv target5. Click the Discover Portal button once again.
6. In Discover Target Portal dialog, type in the iSCSI interface IP address of the partner node that will be used to connect the StarWind provisioned targets. Click Advanceddicover second target portal node17. Select Microsoft iSCSI Initiator as the Local adapter, select the Initiator IP in the same subnet as the IP address of the partner server from the previous step. Confirm the actions to complete the Target Portal discovery.connect csv1 node1 second target8. Now, all the target portals are added on the first node.
9. To Discover Targets Portals from the second StarWind node, click the Discover Portal button once again, enter iSCSI IP address for the second StarWind Node (172.16.30.20). Click the Advanced button.discover target portal node210. 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.connect csv1 node 2 connection111. Click the Discover Portal button once again. In Discover Target Portal dialog, enter another iSCSI IP address of the second StarWind Node (172.16.40.20). Click the Advanced button.discover second target portal node212. Select Microsoft iSCSI Initiator as Local adapter and select the Cluster Node 1 initiator IP address from the same subnet. Click OK twice to add the Portal.connect csvtarget node1 connection113. All target portals are successfully added to the Cluster Node 1.discover portals14. Repeat the steps 1-13 on the partner node.

Connecting Targets

1. 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).
2. Select a target discovered from the first StarWind Node and click Connect.iniator properties3. Enable checkboxes as shown in the image below. Click Advanced.connect csv1node14. Select Microsoft iSCSI Initiator in the Local adapter dropdown menu. 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.connect csv target node1 connection15. To connect the same target via another subnet, select it once again and click Connect.
6. Enable checkboxes like in the image below and click Advanced.connect csv1node17. Select Microsoft iSCSI Initiator in the Local adapter text field.
8. In the Target portal IP select another IP address of the first StarWind Node and Initiator IP address from the same subnet. Click OK twice to connect the target.connect csv1 node1 second target9. Select the partner target discovered from the second StarWind node and click Connect.first target connected10. Enable checkboxes like in the image below and click Advanced.connect csv1 node 211. Select Microsoft iSCSI Initiator in the Local adapter text field.
12. 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.connect csv1 node 2 connection 113. To connect the same target via another subnet, select it once again and click Connect.
14. Enable checkboxes like in the screenshot below and click Advanced.connect csv1 node 215. In the Target portal IP select another IP address of the second StarWind Node and Initiator IP address from the same subnet. Click OK twice to connect the target.connect csv1 node2 connection 216. Repeat steps 1-15 for all HA device targets.
After that, repeat the steps 1-17 on the Cluster node 2, specifying corresponding IP addresses. The result should look like in the picture below.

targets connceted17. Initialize the disks and create partitions on them 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 disks as GPT.

Creating a Failover Cluster in Windows Server 2016

NOTE: To avoid issues during the cluster validation configuration, it is recommended to install the latest Microsoft updates on each node.
1. Open Server Manager. Select the Failover Cluster Manager item from the Tools menu.failover manager2. Click the Create Cluster link in the Actions section of Failover Cluster Manager.failover cluster3. Specify the servers to be added to the cluster. Click Next to continue.add nodes to cluster4. Validate the configuration by running the cluster validation tests: select Yes… and click Next to continue.validation warning5. Specify 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, set the cluster IP address manually.cluster ip6. In Confirmation, make sure that all settings are correct. Click Previous to make any changes or Next to proceed.
NOTE: If checkbox Add all eligible storage to the cluster is selected, the wizard will add all disks to the cluster automatically. The device with the smallest storage volume will be assigned as a Witness. It is recommended to uncheck this option before clicking Next and add cluster disks and the Witness drive manually.
7. The process of the cluster creation starts. Upon the completion, the system displays the summary with the detailed information. Click Finish to close the wizard.confirmation

Adding Storage to the Cluster
1. In Failover Cluster Manager, navigate to Cluster -> Storage -> Disks. Click Add Disk in the Actions panel, choose StarWind disks from the list and confirm the selection.add disks to cluster2. To configure the cluster witness disk, right-click on Cluster and proceed to More Actions -> Configure Cluster Quorum Settings.configure cluster quorum3. Follow the wizard and choose the Select the quorum witness option. Click Next.select quorum4. Select Configure a disk witness. Click Next.select disk witness5. Select the Witness disk to be assigned as the cluster witness disk. Click Next and press Finish to complete the operation.configure storage witness6. In Failover Cluster Manager, right-click the disk and select Add to Cluster Shared Volumes.
add to CSV7. If renaming of the cluster shared volume is required, right-click on the disk and select Properties. Type the new name for the disk and click Apply followed by OK.CSV properties8. Perform the steps 6-7 for any other disk in Failover Cluster Manager. The resulting list of disks will look similar to the screenshot below.
CSV created
Configuring Cluster Network Preferences
1. In the Networks section of the Failover Cluster Manager, right-click on the network from the list.  If required, set its new name to identify the network by its subnet. Apply the change and press OK.

NOTE: Do not allow cluster network communication on either iSCSI or synchronization network.
rename iscsi2. Rename other networks as described above, if required.networks renamed3. In the Actions tab, click Live Migration Settings. Uncheck the synchronization network only if the iSCSI network is 10+ Gbps. Apply the changes and click OK.
live migration

The cluster configuration is completed and it is ready for virtual machines deployment. Select Roles and in the Action tab, click Virtual Machines -> New Virtual Machine. Complete the wizard.

Configuring File Shares

Please follow the steps below if file shares should be configured on cluster nodes.

Configuring the Scale-Out File Server Role

1. To configure the Scale-Out File Server Role, open Failover Cluster Manager
2. Right-click the cluster name, then click Configure Role and click Next to continue

StarWind Configuring Server Roles

3. Select the File Server item from the list in High Availability Wizard and click Next to continue

StarWind Select Role

4. Select Scale-Out File Server for application data and click Next

Select Server Type

5. On the Client Access Point page, in the Name text field, type the NetBIOS name that will be used to access a Scale-Out File Server

StarWind File Server Name

Click Next to continue.

6. Check whether the specified information is correct. Click Next to continue or Previous to change the settings

File Server Confirmation

7. Once the installation is finished successfully, the Wizard should now look like the screenshot below.

Click Finish to close the Wizard.

File Server Summary

8. The newly created role should now look like the screenshot below.

File Server Confirmation

NOTE: If the role status is Failed and it is unable to Start, please, follow the next steps:

FIle Server Error

  • Open Active Directory Users and Computers;
  • Enable the Advanced view if it is not enabled;
  • Edit the properties of the OU containing the cluster computer object (in this case – Production);
  • Open the Security tab and click Advanced;
  • In the appeared window, press Add (the Permission Entry dialog box opens), click Select a principal;
  • In the appeared window, click Object Types, select Computers, and click OK;
  • Enter the name of the cluster computer object (in this case – Production);

Select User. Computer

  • Go back to Permission Entry dialog, scroll down, and select Create Computer Objects

Permission Entry for Computers

  • Click OK on all opened windows to confirm the changes.
  • Open Failover Cluster Manager, right-click SOFS role and click Start Role

Configuring File Share

To Add File Share:

1. Open Failover Cluster Manager.
2. Expand the cluster and then click Roles.
3. Right-click the file server role and then press Add File Share.
4. On the Select the profile for this share page, click SMB ShareApplications and then click Next.

SMB Share

5. Select a CSV to host the share. Click Next to proceed

Selecting server for share

6. Type in the file share name and click Next

Spacify Share name

7. Make sure that the Enable Continuous Availability box is checked. Click Next to proceed

Configuring share settings

8. Specify the access permissions for the file share.

Permissions to Control Access

NOTE:

  • For the Scale-Out File Server for Hyper-V, all Hyper-V computer accounts, the SYSTEM account, and all Hyper-V administrators must be provided with the full control on the share and file system;
  • For the Scale-Out File Server on Microsoft SQL Server, the SQL Server service account must be granted full control on the share and the file system.

9. Check whether specified settings are correct. Click Previous to make any changes or click Create to proceed.

Confirm Selections SOFS

10. Check the summary and click Close to close the Wizard.

SOFS results

To Manage Created File Shares:

1. Open Failover Cluster Manager.
2. Expand the cluster and click Roles.
3. Choose the file share role, select the Shares tab, right-click the created file share, and select Properties:

Failover Cluster manager Shares

Configuring the File Server for General Use Role

NOTE: To configure File Server for General Use, the cluster should have available storage

1. To configure the Scale-Out File Server role, open Failover Cluster Manager
2. Right-click on the cluster name, then click Configure Role and click Next to continue

StarWind Configuring Server Roles

3. Select the File Server item from the list in High Availability Wizard and click Next to continue

StarWind Select Role

4. Select File Server for general use and click Next

File Server Type

 

5. On the Client Access Point page, in the Name text field, type the NETBIOS name that will be used to access the File Server and IP for it

File Server Client Access Point

Click Next to continue

6. Select the Cluster disk and click Next

Select Storage

7. Check whether the specified information is correct. Click Next to proceed or Previous to change the settings

File Server General Use Confirmation

8. Once the installation has been finished successfully, the Wizard should now look like the screenshot below

Click Finish to close the Wizard.

File Server Summary

9. The newly created role should now look like the screenshot below

File Server

NOTE: If the role status is Failed and it is unable to Start, please, follow the next steps:

  • Open Active Directory Users and Computers;
  • Enable the Advanced view if it is not enabled;
  • Edit the properties of the OU containing the cluster computer object (in this case – Production);
  • Open the Security tab and click Advanced;
  • In the appeared window, press Add (the Permission Entry dialog box opens), click Select a principal;
  • In the appeared window, click Object Types, select Computers, and click OK;
  • Enter the name of the cluster computer object (in this case – Production);

Select User. Computer

  • Go back to Permission Entry dialog, scroll down, and select Create Computer Objects

Permission Entry for Computers

  • Click OK on all opened windows to confirm the changes.
  • Open Failover Cluster Manager, right-click File Share role and click Start Role

Configuring SMB File Share

To Add SMB File Share:

1. Open Failover Cluster Manager
2. Expand the cluster and then click Roles
3. Right-click the File Server role and then press Add File Share
4. On the Select the profile for this share page, click SMB ShareQuick and then click Next

Profile for SMB Share

5. Select available storage to host the share. Click Next to continue

Server and path for share

6. Type in the file share name and click Next

Share Name

7. Make sure that the Enable Continuous Availability box is checked. Click Next to continue

Configure share settings

8.Specify the access permissions for the file share

Permissions

9. Check whether specified settings are correct. Click Previous to make any changes or Next/Create to continue

Confirmation

10. Check the summary and click Close

View results

To manage created SMB File Shares:

11. Open Failover Cluster Manager
12. Expand the cluster and click Roles
13. Choose the File Share role, select the Shares tab, right-click the created file share, and select Properties

Failover cluster settings

 

Configuring NFS file share

To Add NFS File Share:

1. Open Failover Cluster Manager.
2. Expand the cluster and then click Roles.
3. Right-click the File Server role and then press Add File Share.
4. On the Select the profile for this share page, click NFS Share – Quick and then click Next

Profile for this share

5. Select available storage to host the share. Click Next to continue

Server and path for share

6. Type in the file share name and click Next

Share Name

7. Specify the Authentication. Click Next and confirm the message in pop-up window to continue

Autentication method

8. Click Add and specify Share Permissions

Share Permissions

Add Permission

9. Specify the access permissions for the file share

Permissions

 

10. Check whether specified settings are correct. Click Previous to make any changes or click Create to continue

Confirm Selections

11. Check a summary and click Close to close the Wizard

NFS Share results

To manage created NFS File Shares:

1. Open Failover Cluster Manager.
2. Expand the cluster and click Roles.
3. Choose the File Share role, select the Shares tab, right-click the created file share, and select Properties.

Failover cluster settings

Save your time finding all the answers to your questions in one place!
Have a question? Doubt something? Or just want to know an independent opinion?
StarWind Forum exists for you to “trust and verify” any issue already discussed and solved