Hi Handian Sudianto,
thx for asking here at Q&A portal. So based on your screenshot and description, you're working with an Azure Stack HCI (Hyper-Converged Infrastructure) 3-node cluster.
Storage Structure in Your Cluster
Folder Structure
- Infrastructure_1: Typically contains cluster system files and management data
- UserStorage_1, UserStorage_2, UserStorage_3: These appear to be storage pools for each node
Are these storages for each node?
- Yes, in a 3-node Azure Stack HCI cluster, each UserStorage_X typically corresponds to storage from each physical node
- The numbering usually (but not always) matches the node numbering
Data Replication and Consistency. Default Behavior
- Data is NOT automatically identical across all storage locations
- Each node maintains its own storage unless you've configured replication
Replication Options
- Mirrored volumes Data is duplicated across nodes (usually 2 or 3 copies)
- Parity volumes More space-efficient but with performance tradeoffs
- Non-replicated Data exists only on one node (vulnerable to node failure)
For check urs config
Get-VirtualDisk | Select FriendlyName, ResiliencySettingName, NumberOfDataCopies
Get-StoragePool | Select FriendlyName, HealthStatus, OperationalStatus
Ms best practices. For important data use 2-way or 3-way mirroring depending on your redundancy needs. For capacity optimization consider parity volumes for less critical data. And of coz monitoring set up alerts for storage health using
Get-StorageHealthReport -Name "StorageNode*"
Best regards,
Alex
P.S. If my answer help to you, please Accept my answer