question

lra-4650 avatar image
0 Votes"
lra-4650 asked AlexBykovskyi answered

HYPER-V Clustering - Storage and Network Configuration

Hello,

I would like to clarify some doubts regarding the creation of a cluster in hyper-v:

1- Can I have two clusters that have the same name? Of course in this case each cluster has its respective IP address.

2- THE storage network, will it always be mandatory? Is it recommended to do a nic teamig for this network?

3- Or what are the number of networks that I should take into account when configuring a hyper-v cluster?

With the networks management, live migration, storage and herbeat (Clustering) is it enough?

4- Regarding shared storage, should it always be done with iSCSI virtual disks, or is there a different way to configure shared storage?

5- Can storage spaces be used?

5- In case you have an HP 3PAR and present the LUN to the hyper-v hosts, would you use iSCSI initiators so that the hyper-v host can see the LUN assigned to it from the HP 3PAR ?. Or should it be done in another way?

6- If the storage is by fiber, what should I take into account for shared storage?

7- What size quorum disk would it be? Can it be 1GB regardless of the number of physical hosts?

windows-server
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

AlexBykovskyi avatar image
0 Votes"
AlexBykovskyi answered

Hey,

1- You can't have two clusters with the same name. Cluster requires cluster name object in AD and DNS entry. You can't have 2 of the same name.
https://docs.microsoft.com/en-us/windows-server/failover-clustering/configure-ad-accounts
2- Storage network is required to connect to your storage array or to deploy Software-Defined Storage. As for teaming it depends on the configuration. With iSCSI storage it is recommended to use MPIO.
3- It is recommended to have separated networks for storage and network communications. Management, live migration, storage and heartbeat (Clustering) should be enough.
4- iSCSI is not the only option. SMB 3.0 file shares as shared storage can be used to create Failover Cluster.
5- Storage Spaces Direct can be used to create Failover Cluster.
https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-hardware-requirements
6- With iSCSI storage, you will need to connect it via iSCSI initiator and bring LUNs as CSVs to the cluster.
https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-hyperconverged-scenario-with-windows-server-2016/
7-

If you are using Serial Attached SCSI or Fibre Channel, in all clustered servers, all elements of the storage stack should be identical. It's required that the multipath I/O (MPIO) software be identical and that the Device Specific Module (DSM) software be identical. It's recommended that the mass-storage device controllers— the host bus adapter (HBA), HBA drivers, and HBA firmware—that are attached to cluster storage be identical. If you use dissimilar HBAs, you should verify with the storage vendor that you are following their supported or recommended configurations.

https://docs.microsoft.com/en-us/windows-server/failover-clustering/clustering-requirements
8- Size of LUN must be at least 512 MB. 1GB is usually enough.

Cheers,

Alex Bykovskyi

StarWind Software

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.