17. Windows Server 2022: Configuring NFS Storage | Types of Storage Comparison | Step-by-Step Guide!

[@gnancloudgarage]

17. vSphere 7.x_vSphere Storage - How to Configure NFS Datastore or NAS datastore on Windows Server 2022 & Home Lab NFS Datastore Configuration & Management - Home lab How to Configure NFS Datastore or NAS datastore on Windows Server 2022 & Home Lab Kerberos authentication Add NFS Server role on Windows Server 2022

[@arifsohelshaik5979]

Very informative session, crystal clear explanation about NFS DS.. Much appreciated.

[@gnancloudgarage]

Glad it was helpful!

[@basireddysivaranjan8570]

Very help full and simple worthy for watch

[@gnancloudgarage]

Thank you so much Siva 🙂

[@harisingh1983]

superb !!

[@gnancloudgarage]

Thanks a lot!!

[@gotetisais]

Good explanation

[@gnancloudgarage]

Thanks for liking Sai Ji :-)

[@Toward-eternity76]

I have seen some of blog posts where they have not selected Available services as management, while creating NFS VMkernal port group...! is it right ?

[@gnancloudgarage]

Thank you for your question! When creating a VMkernel port group for NFS storage in VMware, selecting "Available Services" as "Management" is generally not required unless the VMkernel port is also intended for management traffic. For NFS traffic, you only need to ensure the "NFS" service is enabled. Here's a clarification: If the port group is dedicated solely to NFS traffic, you should select "NFS" as the available service when configuring the VMkernel port. Selecting "Management" would typically be done for a port group intended to handle management tasks like vSphere client connections or vCenter server communication. Selecting unnecessary services can cause unwanted traffic and potential security concerns, so it's good to keep services specific to their intended purpose.

[@Toward-eternity76]

@gnancloudgarage thank you for info Another thing I came across that in real time enviornment their is no need to setup port group binding for iscsi storage

[@gnancloudgarage]

@@Toward-eternity76 Thank you for your question! In a real-time production environment, port group binding for iSCSI storage is generally not required if you are using VMware ESXi, as it automatically handles network failover for iSCSI traffic at the VMkernel layer. This is because VMware’s iSCSI multipathing is designed to work with VMkernel adapters (one-to-one mapping) rather than relying on port group policies. However, port binding might still be relevant in specific scenarios where strict control is needed, such as in certain legacy setups or configurations with specific storage requirements. The key consideration is to follow VMware’s best practices for your specific storage vendor and ensure multipathing is correctly configured for redundancy and performance.