Username or Email Address
Storage Spaces Direct allows you to create a highly available, highly scalable program-defined storage on the basis of standard servers with local drives, at a lower cost than using traditional SAN or NAS arrays
Now this is a very rapidly developing direction in the IT industry and a lot of clients around the world are looking towards such solutions because of their relative cheapness, practicality and ease of scaling.
However, in such solutions only SSD (for system and quick availability data) and HDD (for large amount of data storage) are used and there is no possibility to use cloud data storage (for example AWS, Azure, GCP, etc.) for the “limitless” volume of stored data.
We offer you a solution capable of combining the convenience and speed of vSAN with the reliability and availability of Cloud data storage.
Using our AcloudA device, you can connect a cloud data storage (for example AWS, Azure, GCP, etc.) instead of one or more, for fault tolerance, hard drives.
You will be able to transfer your CapEx to OpEx, since you will not have to buy new servers to store an increasing amount of data, and you will be able to pay only for the storage you use.
You can easily and quickly increase the space for storing your data in one click as needed.
In addition, data storage in cloud storage is more reliable than conventional storage methods and is consistent with data storage rule 3-2-1.
Storage Spaces Direct allows you to create a highly available, highly scalable program-defined storage on the basis of standard servers with local drives, at a lower cost than using traditional SAN or NAS arrays.
The convergent or hyperconvergent architecture of this solution simplifies procurement and deployment, and features such as caching, tiered storage with the RDMA network and NVMe drives provide unprecedented efficiency and performance.
Before we begin the deployment of Storage Spaces Direct, we need to prepare an action field.
To deploy Storage Spaces Direct, we need a cluster based on Windows Server 2016 datacenter. Additionally, to configure the cluster, we need a domain controller. Setting up the controller is a separate topic, not relevant to this article, it is assumed that you have it. I also recommend that you read the original Microsoft documentation.
This instruction created to understand the process of connecting Aclouda, and not a detailed guide to configuring the cluster and my goal does not require cluster stability, and show how to configure S2D + Aclouda – I will not configure the witness for the cluster and duplicate the network interfaces, due to than we need only 2PC based on Intel core i5 or similar.
In each PC we install 1 Aclouda expansion board and 2 SSD drives, one of which is system, and the second one will be used for the cache (you can use HDD, but then you need to change the type of drive, I said at the end of the “Storage” Spaces Tier”).
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.
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:
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:
First of all you have to Configuring Aclouda on created Targets according to the instruction «Quick Start Guide» on Download page of AcloudA site.
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:
If you have ‘failed’ starting test…:
AcloudA device is always detected by the system like “Unspecified”, for continue installation, you have to manually change it’s type to HDD.
5. Manually Turn back on Caching
This is it!
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:
Table shows the volume types supported by Storage Spaces Direct and several characteristics of each.
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
We build highly available storage system (using Windows Server 2016 Storage Spaces Direct) with AcloudA device without local storage – only Cloud storage.
This eliminates the need for a shared SAS fabric and its complexities, but also enables using devices such as SATA SSDs, which can help further reduce cost or NVMe SSDs to improve performance.