I am creating a 2 node Hyper-V cluster with an SMB Witness using the CreateHASmbWitness.ps1 script. However it seems to have created both sides with the same target name/IQN. This seems to be causing problems with cross connecting iscsi between the two nodes. How do I change the iqn name? Do I edit ...

I have a 2-node Hyper-V vSAN (paid so I have the GUI). I am upgrading servers so I'm migrating one of the nodes to new hardware. One of the vSAN devices looks like it doesn't have the SMB witness configured (shutting down one node causes the vSAN storage to stop and go unsynchronized on both). Check...

To add a little more info (since I had to experiment for a while with this): -Stop the starwind service on the node you are taking out of Maintenance Mode BEFORE making any changes to the xxx_HA.swdsk file (apparently when the service stops, it refreshes the file with the running parameters and will...

I have a two node vSAN (commercial license) with two storage targets and when they re-sync, they go sequentially. From other forum threads, it seems they can be configured to sync simultaneously. Those threads talk about setting the parameter "syncSessionCount" to greater than 1 when creat...