This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 33%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDS%3C/text%3E%3C/svg%3E)
As a part of my Az-801 self studying following the course
i I think I’m understanding Failover clustering however I’m seeing there is an option for Pools in the mmc.
am I correct in assuming that section of the failover clustering is exclusively for storage spaces direct (s2d)
also I’m trying to follow a set of labs
im trying to understand the below in the context of do I need to attach a blank vhdx dynamically expanding 10GB vhdx file as a new scsi controller? Or can the equivalent be done with guest Os level vhd or must be done at host level I’ve noticed if I run the test cluster command from powershell or the mmc and check the output the guest level OS doesn’t have a compatible Bus for s2d and also the partition isn’t right but if I attach a blank disk without even brining it online initialising in raw it can work for s2d.
can you advise a lab and help me understand this please
so if at the end of it I do
the enable cluster command which I understand from the material
Chris Gill
Configuring Windows Server Hybrid Advanced Services Exam Ref AZ-801: Configure advanced Windows Server services for on-premises, hybrid, and cloud environments
Enable-ClusterS2D -cachestate disabled
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 86%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi Dalbir Singh,
Thank you for reaching out to us on the Microsoft Q&A forum.
Failover Clustering and Storage Pools
Failover Clustering: This is a feature of Windows Server that enables you to create a group of independent servers that work together to increase the availability of applications and services. The clustered servers (called nodes) are connected by physical cables and by software. If one of the nodes fails, another node can take over its workload without downtime, a process known as failover.
Storage Pools in Failover Clustering: The section in the MMC (Microsoft Management Console) you're referring to is indeed related to storage. In a failover cluster, this typically involves managing the storage that the cluster nodes use.
Storage Spaces Direct (S2D)
Storage Spaces Direct (S2D): This feature allows you to create highly available and scalable storage by using local storage on cluster nodes. S2D aggregates the internal disks of each cluster node to create a distributed storage pool.
Pools in MMC: When you see an option for "Pools" in the Failover Cluster Manager MMC, it is primarily for managing Storage Spaces Direct (S2D). S2D consolidates local disks from all cluster nodes into a single storage pool, which is then used to create virtual disks that are highly available and resilient.
So, you are correct in assuming that the "Pools" section within the Failover Clustering MMC is specifically designed for managing Storage Spaces Direct (S2D). This setup allows you to handle storage more efficiently within a failover cluster, providing benefits such as high availability, scalability, and performance improvements.
Failover Clustering: Understand how to set up and manage failover clusters, including:
Storage Spaces Direct (S2D): Learn how to configure and manage S2D, including:
Backup and Recovery: Configure Windows Server Backup, Azure Backup, and other backup solutions. Understand how to perform restore operations and implement disaster recovery plans.
Software Defined Networking (SDN): Understand the components and configuration of SDN, including:
Advanced Network Services: Configure and manage advanced network services, such as:
Active Directory Domain Services (AD DS): Configure and manage advanced AD DS features, including:
Active Directory Certificate Services (AD CS): Implement and manage AD CS, including:
Active Directory Federation Services (AD FS): Configure and manage AD FS for single sign-on (SSO) and federated identities.
Azure Active Directory (Azure AD): Integrate on-premises AD DS with Azure AD, configure Azure AD Connect, and implement hybrid identity.
Azure Integration: Understand how to integrate Windows Server environments with Azure services, including:
Azure Arc: Manage on-premises and multi-cloud resources using Azure Arc.
Windows Admin Center: Configure and use Windows Admin Center for managing hybrid environments.
Performance Monitoring: Use Performance Monitor, Resource Monitor, and other tools to monitor Windows Server performance.
Event Logs and Diagnostics: Analyze event logs and implement diagnostic logging and tracing.
Troubleshooting Tools: Use various troubleshooting tools and techniques to resolve complex issues in Windows Server environments.
Please don't hesitate to reach out to us if you have any other queries.
If you found the information helpful, we would greatly appreciate it if you could acknowledge it by selecting the Accept Answer & Upvote options.
So how would I lab this on hyper v for s2d should can I attach it in the VM the disk or must it be done only at hyper v level
Hi Dalbir Singh,
To set up Storage Spaces Direct (S2D) in a lab environment using Hyper-V, you'll need to ensure that the disks are correctly configured. Here’s a step-by-step guide to achieve this:
Prerequisites
Steps to Configure S2D on Hyper-V
Add Data Disks: You need to add additional virtual hard disks (VHDX) to each VM. These will be used by S2D.
Create an Internal/External Virtual Switch:
- Assign each VM a network adapter connected to this virtual switch.
Log in to each VM and open PowerShell.
Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools
1. **Validate the Cluster Configuration**
```powershell
Test-Cluster -Node VM1, VM2, VM3, VM4
New-Cluster -Name S2DCluster -Node VM1, VM2, VM3, VM4 -StaticAddress <Cluster_IP_Address>
Enable-ClusterS2D
New-Volume -StoragePoolFriendlyName S2D* -FriendlyName Volume1 -FileSystem CSVFS_ReFS -Size 10TB
Considerations
By following these steps, you should be able to set up and lab Storage Spaces Direct (S2D) on Hyper-V effectively.
Please don't hesitate to reach out to us if you have any other queries.
If you found the information helpful, we would greatly appreciate it if you could acknowledge it by selecting the Accept Answer & Upvote options.
So to confirm s2d can not be labbed with disks added within the VM (new-vhd, attach-vhd) itself due to the bus compatibility required for s2d? My assumption is the answer is no. No s2d can’t use disks within the VM, they must be added outside via the guest?
no?
Hi Dalbir Singh,
Your assumption is correct. In the context of Storage Spaces Direct (S2D), you cannot use disks that are added within the VM (using commands like New-VHD and Attach-VHD) for S2D storage directly.
Storage Spaces Direct requires direct access to physical disks or to virtual disks that are connected to the VM through virtual SCSI controllers that support persistent reservations. This means the disks must be presented to the VM from the hypervisor with the appropriate virtual SCSI controller that supports S2D requirements.
To use S2D within a VM, you typically configure it by adding virtual disks that are presented to the VM by the hypervisor. These virtual disks are usually created and attached to the VM through the hypervisor management tools (such as Hyper-V Manager or PowerShell commands related to the hypervisor).
In summary, disks used for S2D storage need to be managed at the hypervisor level and presented to the VM correctly with the required bus compatibility (virtual SCSI controllers supporting persistent reservations), rather than being added within the VM itself using New-VHD and Attach-VHD commands.
Please don't hesitate to reach out to us if you have any other queries.
If you found the information helpful, we would greatly appreciate it if you could acknowledge it by selecting the Accept Answer & Upvote options.
Hi Dalbir Singh,
Just checking in to see if you had got a chance to see the previous response. To benefit the community, find the right answers, please do mark the post which was helpful by clicking on Accept Answer. Has your issue been resolved? If you are still experiencing the problem, please inform us. We are happy to help you.