How to configure S2D with AcloudA Extended Guide

Install Windows Server roles and features

Several Windows Server roles and features are used by this solution. It makes sense to install them all at the same time, then perform specific configuration tasks later. To make this installation quick and easy, use the following PowerShell script:

Note that it is a good idea to install the Hyper-V role on all nodes even if you plan to implement the disaggregated solution. Although you may not regularly use the storage cluster to host VMs, if the Hyper-V role is installed, you will have the option to deploy an occasional VM if the need arises. Once the roles and features have been installed and the nodes are back online, operating system configuration can begin.

Configure the operation system

Next, we configure the operating system, including Windows Update, AD Domain join, and internal drive verification.

Next, we configure the operating system, including Windows Update, AD Domain join, and internal drive verification. To ensure that the latest fixes and patches are applied to the operating system, perform updating of the Windows Server components via Windows Update. It is a good idea to reboot each node after the final update is applied to ensure that all updates have been fully installed, regardless what Windows Update indicates. Upon completing the Windows Update process, join each server node to the Windows Active Directory Domain. Use the following PowerShell command to accomplish this task.

PowerShell command to add system to an Active Directory Domain:

From this point onward, when working with cluster services be sure to log onto the systems with a Domain account and not the local Administrator account. Ensure that a Domain account is part of the local Administrators Security Group, as shown in Figure:

Administrators Properties

Verify that the internal drives are online, by going to Server Manager > Tools > Computer Management > Disk Management. If any are offline, select the drive, right-click it, and click Online. Alternatively, PowerShell can be used to bring all drives in each host online with a single command:

Since all systems have been joined to the domain, we can execute the PowerShell command remotely on the other hosts while logged in as a Domain Administrator. To do this, use the command shown in Example:

Create the Failover Cluster and Enable Storage Spaces Direct

Before creating the Failover Cluster we need to validate the components that are necessary to form the cluster. As an alternative to using the GUI, the following PowerShell commands can be used to test and create the Failover Cluster:

  1. We create the new cluster:

PowerShell window - Create the new cluster

If you have ‘failed’ starting test…:

  1. Enable Storage Spaces Direct with Cache Disabled and AutoConfig Off:

PowerShell window - Enable Storage Spaces Direct

  1. Create a new Storage Pool:

PowerShell window - Create a new Storage Pool


AcloudA device is always detected by the system like “Unspecified”, for continue installation, you have to manually change it’s type to HDD.


  1. Change the Media Types:

PowerShell window - Change the Media Types

PowerShell window - Change the Media Types - Check

5. Manually Turn back on Caching

PowerShell window - Turn back on Caching

This is it!

Create virtual disks

After the S2D cluster is created, create virtual disks or volumes based on your performance requirements. There are three common volume types for general deployments:

  • Mirror
  • Parity
  • Multi-Resilient

Table  shows the volume types supported by Storage Spaces Direct and several characteristics of each.

Table of summary characteristics assosiated with common storage volume types

Use the PowerShell commands in Example to create and configure the virtual disks. Choose any or all types of volumes shown, adjusting the volume names and sizes to suit your needs. However, the amount of pool space consumed by each volume will depend on which Storage Tier is used. For example, the commands below create three volumes that consume a total of 88TB from the pool.

Create a Parity Volume using the commands

Create a Multi-Resilient Volume using the commands

 Once S2D installation is complete and volumes have been created, the final step is to verify that there is fault tolerance in this storage environment. The PowerShell command to verify the fault tolerance of the S2D storage pool and shows the output of that command in our environment.

PowerShell command to determine S2D storage pool fault tolerance

To Query the virtual disk, use this command. The command verifies the fault tolerance of a virtual disk (volume) in S2D and Figure 24 shows the output of that command in our environment

PowerShell command to determine S2D virtual disk (volume) fault tolerance

Over time, the storage pool may get unbalanced because of adding or removing physical disks/storage nodes or data written or deleted to the storage pool. In this case, use the PowerShell command shown down to improve storage efficiency and performance.

PowerShell command to optimize the S2D storage pool

Fill the form below to get Extended version of this Guide

Please, fill all fields