Notice: Trying to get property 'post_excerpt' of non-object in /home/n3svtp4r09fz/technet.vn/wp-content/themes/darknews/single.php on line 43
Setup Azure Stack HCI
-
Validating and create the cluster
Step | Detail |
1 | In this LAB, we will run the cluster validation and create the cluster. |
1.1 | In Server Manager à Dashboard à Tools à select Failover Cluster Manager |
1.2 | On Failover Cluster Manager console à click Validate Configuration |
1.3 | On Before You Begin à click Next |
1.4 | On Select Servers or a Cluster à click Browse Select the 2 nodes: MYIANLAB-01 and MYIANLAB-02 |
1.5 | On Testing Options à click Run all tests (recommended) |
1.6 | On Confirmation à click Next It will validate the cluster with 2 nodes.
Once done, click View Report |
1.9 | View the report
Click on each subject to view detail of the report. Once done, you can close the report and back to Summary console. |
1.10 | On Summary à select Create the cluster now using the validated nodes Then click Finish |
1.11 | On Before you begin, click Next Then enter the cluster info:
|
1.12 | Unselect the checkbox: Add all eligible storage to the cluster à Next |
1.13 | Once creation done, click Finish |
1.14 | The cluster will be like that
There is no Pool in the cluster
And we have 2 cluster network |
-
Enable Azure Stack HCI
Step | Detail |
1 | The below steps can be implemented on MYIANLAB-01 or MYIANLAB-02 |
1.1 | Check physical disks: We can check physical disks using Disk Management or by using Powershell: Get-PhysicalDisk
In the CanPool column, the disks are set to True which means we can group them to a pool |
1.2 | Enable Cluster Storage Space Direct using PowerShell: Enable-ClusterStorageSpacesDirect –Verbose And on Confirm |
1.43 | Once it completed, you can check the report in C:\Windows\Cluster\Reports
Some warnings in the report because we don’t have disks for cache
And now when we check all the disk again, it changes CanPool status from True to False
|
1.6 | A default Pool is created |
-
Configure File share witness on file share
Step | Detail |
1 | We will configure the file share witness with GUI |
1.1 | Create the folder named witness on server 10.0.010 and share it with read/write |
1.2 | On Failover Cluster Manager, right-click on s2dcluster à More Actions à Configure Cluster Quorum Settings |
1.3 | Click Next |
1.4 | Choose Select the quorum witness |
1.5 | Select Configure a file share witness |
1.6 | Click Browse > Browse
|
1.7 | Click Advanced |
1.8 | Click Find Now > Select MYIANLAB-DC (This is the server which we have share drive)
Click OK |
1.9 | Click Witness >> Click OK |
1.10 | View the File Share Path >> Click Next |
1.11 | Confirm the info then click Next |
1.12 | On Summary, click Finish |
1.13 | Back to Failover Cluster manager console to check the witness |
2 | (Optional) We can use Powershell to create the file share witness |
Using Powershell and run the command: Set-ClusterQuorum -FileShareWitness \\10.0.0.10\witness -Credential (Get-Credential) |
|
3 | Check the File Share Witness by access to \\10.0.0.10\Witness |
-
Check Cluster status
Step | Detail |
1 | Check Cluster Node status |
In Failover Cluster Manager à Nodes
Both Nodes are Up. |
|
2 | Check Disks status
There is a Cluster Virtual Disk (ClusterPerformanceHistory) => this one only listed when you enable Azure Stack HCI. |
2.1 |
-
Create a new Volume using Failover Cluster Manager
Step | Detail |
1.1 | In Failover Cluster Manager >> Storage >> Pools >> Click New Virtual Disk
|
1.2 | Select Storage Pool >> click OK |
1.3 | Create a virtual disk named VirtualDisk01
Enter 50 to create 50Gb disk |
1.4 | Confirm selections |
1.5 | View results >> Close
Note: remember to check the “Create a volume when this wizard closes” |
1.6 | Click Next >>
And Click Next >> Next |
1.7 | Select “Don’t assign to a driver letter or folder” |
1.8 | Name the volume: Volume01 >> click Next |
![]() |
|
1.9 | At Completion >> click Close |
1.10 | In Failover Cluster Manager >> Storage >> Pools >> check the new Cluster Virtual Disk
|
1.11 | Add this Cluster Virtual Disk to Cluster Shared Volumes
Now the Virtual Disk change from Available Storage to Cluster Shared Volume |
1.12 | Now we have created a new volume using VirtualDisk01 |