Home > Storage > PowerStore > Virtualization and Cloud > Dell PowerStore: Microsoft Hyper-V Best Practices > Transport options
Deciding which transport to use is based on customer preference and factors such as the size of the environment, cost of the hardware, and the required support expertise.
iSCSI has grown in popularity for several reasons, such as improved performance with the higher bandwidth connectivity options now available. A converged Ethernet configuration also reduces complexity and cost. Small office, branch office, and edge use cases benefit when minimizing complexity and hardware footprints with converged networks.
Regardless of the transport, it is a best practice to ensure redundant paths to each host by configuring MPIO. For test or development environments that can accommodate down time without business impact, a less-costly, less-resilient design that uses single path might be acceptable.
In a Hyper-V environment on PowerStore, all hosts that are clustered should be configured to use a single common transport (FC or iSCSI).
There is limited Microsoft support for mixing transports on the same host. We do not recommend mixing transports as a best practice, but there are some uses cases for temporary use.
For example, when migrating from one transport type to another, both transports might be required to be available to a host during a transition period. If mixed transports must be used, use a single transport for each volume that is mapped to the host.
Consider the following example:
You would perform the following actions:
Note: Do not attempt to map a volume to a Windows host using more than one transport. Mixing transports for the same volume will result in unpredictable service-affecting I/O behavior in path failure scenarios. Each volume should be mapped using a unique transport.