Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. If the Answer is helpful, please click " Accept Answer" and upvote it. An accepted blog can be put on top of our forum, so that people who have a similar issue can get access to their solution more quickly. Thanks for your support! Besides, would you please help me Accept Answer. Microsoft does not guarantee the accuracy and effectiveness of information. Please note: Information posted in the given link is hosted by a third party. If you also use Hyper-V, you can take a look at this product:įinally, I found some articles comparing the pros and cons of Guest iSCSI mapping and Raw Device Mapping respectively: Secondly, for our Microsoft, we have SMB multichannel to support clients who use our product (like Hyper-V) while have the same demand as yours. But if you are in a VMware environment, I strongly suggest you to contact their engineers directly to gain more professional information on RDM. Using Raw Device Mapping (RDM), each LUN can represent an Operating System disk. And I see you prefer to have multipath and more capable read-write function, so I may suggest RDM. If an RDM through the ESXi host, you get the advantage of managing the LUNs, multipathing, and connectivity via the hosts and/or vCenter, easing many aspects of LUN management. If the latter, ESXi is only aware of your storage traffic as network traffic - it treats it and understands it as just another IP packet on the VM network setup. Firstly, I need to determine your production environment, VMware or Hyper-V (RDM seems to be a VMware product)? From my perspective, the choice then, is whether you wish control and management of iSCSI LUNs via the ESXi host or via the guest OS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |