<div>
Plug the drives in. S2D cluster service will incorporate them into the pool. Only one storage pool is supported.<br />
<br />
Once complete, you can create your virtual disk using just those disks by setting your SSD tier to &quot;0&quot; in your PowerShell.
</div>


Plug the drives in. S2D cluster service will incorporate them into the pool. Only one storage pool is supported.

Once complete, you can create your virtual disk using just those disks by setting your SSD tier to "0" in your PowerShell.

<div>
There are other spare HDDs in the S2D servers though to cater for HDD failure. Would I be best to remove them disks while I create this new VD? As I don't want any data from this new Virtual Disk to be stored on them.
</div>


There are other spare HDDs in the S2D servers though to cater for HDD failure. Would I be best to remove them disks while I create this new VD? As I don't want any data from this new Virtual Disk to be stored on them.

CaptainGiblets

<div>
<div class="content wysiwyg-content">
Really I just want to check that what i am doing is a supported config.<br />
<br />
I have 3 servers i use for HCI using S2D 2019.<br />
<br />
I have 3 Virtual Disks all using 33% of the storage minus 1 spare HDD for failure(cache + ssd + hdd) seems to be working ok.<br />
<br />
I want to add 8 1TB drives into each of the servers to create a new virtual disk that only uses cache + hdd.<br />
<br />
The HDDs are a different model than the HDDs used in the other 3 virtual disks. I know that i should utilise only the one storage pool, but would i still be in a supported configuration, on top of that how would it know what disks to create the new virtual disk on? I dont want it to attempt to use the space capacity disks i currently have (they are 1.6tb disks) with the new ones i intend to use (1tb disks)<br />
<br />
Thanks in advance for any feedback!
</div>
</div>


Really I just want to check that what i am doing is a supported config.

I have 3 servers i use for HCI using S2D 2019.

I have 3 Virtual Disks all using 33% of the storage minus 1 spare HDD for failure(cache + ssd + hdd) seems to be working ok.

I want to add 8 1TB drives into each of the servers to create a new virtual disk that only uses cache + hdd.

The HDDs are a different model than the HDDs used in the other 3 virtual disks. I know that i should utilise only the one storage pool, but would i still be in a supported configuration, on top of that how would it know what disks to create the new virtual disk on? I dont want it to attempt to use the space capacity disks i currently have (they are 1.6tb disks) with the new ones i intend to use (1tb disks)

Thanks in advance for any feedback!

S2D multiple Virtual Disks with Different configs

Computer data storage, often called storage or memory, is a technology consisting of computer components and recording media used to retain digital data. In addition to local storage devices like CD and DVD readers, hard drives and flash drives, solid state drives can hold enormous amounts of data in a very small device. Cloud services and other new forms of remote storage also add to the capacity of devices and their ability to access more data without building additional data storage into a device.

Storage

The term "Backup" means the methods and processes involved to copy computer data (system data as well as application data) to media other than the ones where the data originally live (disk, tape, optical, cloud). "Restore" in turn means the methods and processes involved in data recovery, i. e., bringing back copied computer data to their original location. Backup/Restore primarily serves as a means of protection against data loss, be it due to disaster, corruption or sabotage. It can also be used for recovering data from an earlier point in time and even for cloning machines or applications. There is a wide variety of backup/restore software available, from expensive commercial products to free or open source tools.

Storage Software

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.