Home > Storage > PowerStore > Virtualization and Cloud > Dell PowerStore: Microsoft Hyper-V Best Practices > Transport options
PowerStore supports SCSI (iSCSI and Fibre Channel (FC)). PowerStore also supports NVMe/FC and NVMe/TCP. However, Microsoft does not support either NVMe transport option as of this writing.
For Microsoft environments, the choice of transport (iSCSI or FC) is based on factors such as customer preference, size of the environment, economics, and the required support expertise.
Fibre Channel: businesses that have standardized on FC benefit from a fast, stable, and reliable data transport that ensures resilience, performance, and data isolation.
iSCSI has grown in popularity.
Regardless of the transport, configure MPIO for redundant storage data paths to each host as a best practice.
A single path configuration is less complicated, easier to configure, and less expensive to implement. Use of a single data path is acceptable only when the workload is not critical. For example, nonproduction test or development environments that are not business critical might use lower tier hardware and a single path.
In a Hyper-V environment on PowerStore, configure all hosts or nodes to use a single common SCSI transport as a best practice. Use FC or iSCSI, but not both.
Windows Server hosts and clusters support the use of concurrent transports (FC and iSCSI). However, limit the use of multiple transports to specific or temporary use cases.
A data or workload migration is a valid use for multiple transports. Windows Server supports FC and iSCSI adapters installed in the same host.
Do not assign FC and iSCSI paths to the same volume or cluster volume. For example, configure volume 1 to use FC, and configure volume 2 to use iSCSI.
Caution: A volume with concurrent FC and iSCSI paths will experience unpredictable service-affecting I/O behavior given a path failure scenario.
Consider the following data migration example:
Perform the following steps: