*** Disclaimer ***
s2d.dk is not responsible for any errors, or for the results obtained from the use of this information on s2d.dk. All information in this site is provided as "draft notes" and "as is", with no guarantee of completeness, accuracy, timeliness or of the results obtained from the use of this information. Always test in a lab setup, before use any of the information in production environment.
For any reference links to other websites we encourages you to read the privacy statements of the third-party websites.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
***
Draft work in progress
Storage Maintenance Mode impact when a Node reboot
What is the Impact or benefit to have Storage Maintenance Mode enabled when a Node reboot
Is there a benefit ? let's test...
Demo Setup with 6 Node S2D Cluster and 6 vDisk/CSVs.
18 x Guest VMs (Windows Server 2012R2, 2016 and 2019)
Part 1 - Preparation
Rebalacing after Node join back to the cluster and disable Storage Maintenance Mode
Video will come
Part 2
Video will come
# ************************************************************************************** #
PowerShell used in the Demo Videos
# ************************************************************************************** #
Get-VirtualDisk | sort FriendlyName
Get-StoragePool -FriendlyName "S2D on S2D10"
Optimize-StoragePool -FriendlyName "S2D on S2D10"
Get-StorageJob
# ************************************************************************************** #
# List the Operational Status of the Extens, for all vDisks
# ************************************************************************************** #
$vDisk=(Get-VirtualDisk).FriendlyName
# Operational Status for the Extens
foreach ($vDisknumber in $vDisk) {
$VirtualDisk1 = Get-VirtualDisk "$vDisknumber"
$Extents = Get-VirtualDisk "$vDisknumber" | Get-PhysicalExtent | Where VirtualDiskUniqueId -Eq $VirtualDisk1.UniqueId
$Extents | Group OperationalStatus -NoElement
$vDisknumber
}
# Copy Number
foreach ($vDisknumber in $vDisk) {
$VirtualDisk1 = Get-VirtualDisk "$vDisknumber"
$Extents = Get-VirtualDisk "$vDisknumber" | Get-PhysicalExtent | Where VirtualDiskUniqueId -Eq $VirtualDisk1.UniqueId
$Extents | Group CopyNumber -NoElement
$vDisknumber
}
# Size
foreach ($vDisknumber in $vDisk) {
$VirtualDisk1 = Get-VirtualDisk "$vDisknumber"
$Extents = Get-VirtualDisk "$vDisknumber" | Get-PhysicalExtent | Where VirtualDiskUniqueId -Eq $VirtualDisk1.UniqueId
$Extents | Group Size -NoElement
$vDisknumber
}
# ************************************************************************************** #
Get-VirtualDisk "vDisk1" | Get-PhysicalExtent
Get-VirtualDisk "vDisk1" | Get-PhysicalExtent | Select-Object -First 24
# ************************************************************************************** #
# MetaData
# ************************************************************************************** #
Get-StoragePool -FriendlyName s2d* | Get-PhysicalDisk -HasMetadata
Get-VirtualDisk -FriendlyName vDisk1 | Get-PhysicalDisk -HasMetadata
Get-VirtualDisk -FriendlyName vDisk2 | Get-PhysicalDisk -HasMetadata
Get-VirtualDisk -FriendlyName vDisk3 | Get-PhysicalDisk -HasMetadata
Get-VirtualDisk -FriendlyName vDisk4 | Get-PhysicalDisk -HasMetadata
Get-VirtualDisk -FriendlyName vDisk5 | Get-PhysicalDisk -HasMetadata
Get-VirtualDisk -FriendlyName vDisk6 | Get-PhysicalDisk -HasMetadata
