In this episode, Sean Donahue is joined by Al Solorzano of E360 to discuss the worst disasters they've recovered from. Surprise twist, not all clouds are cumulonimbus and not all disasters are natural.<\/p><\/oembed>

Resources<\/p>

解决了

MS SQL簇 - 多个SCSI控制器

一种
徽章 +4
嗨，我是我在Server 2012R2上创建一些MSCS SQL群集的过程。在适用的文档中，与Nutanix一起使用基于ISCSI的VG。另请阅读Mike Websters在即将发布的软件版本中与这些VG相关的HOT扩展与这些VG相关的磁盘的信息，真的很好！我的问题是关于我如何在当前多个VMware P/V SCSI控制器上破坏I/O。如果我遵循说明



https://portal.nutanix.com/#/page/solutions/details?targetID=BP-2049_ACROPOLIS_BLOCK_SEVICES:BP-2049_ACRAPOLIS_BLOCK_SERVICES



该VM的所有I/O都不会浏览默认值和SCSI控制器吗？我正在尝试通过多个SCSI控制器分发I/O用于日志，tempdb等。它在我们利用RDM的环境中运行良好，并想尝试在Nutanix方面重复此操作。您能告诉我这是否是可行的，也是实现它的最佳方法。
图标

最好的答案mmcghee2016年10月12日，21：32

\n
\nWhen using iSCSI, storage traffic will go through the vNICs you have configured for the VM. From a performance perspective there are some cases where having muliple vNICs can help, like when CPU utilization is high due to a lot of IOPs. Multiple vNICs can help to balance the network operations across multiple cores. Enabling RSS helps with this but multiple vNICs can also have a benefit. If you have concerns you could add another vNIC and then balance the iSCSI sessions across the two.
\n
\nHTH,
\nMike","className":"post__content__best_answer"}">
查看原件
    该主题已关闭以供评论

    7个答复

    mmcghee
    秩
    UserLevel 3
    徽章 +17
    嗨，亚当，



    使用ISCSI时，存储流量将通过您为VM配置的VNIC进行。从性能的角度来看，在某些情况下，拥有Muliple VNIC可以提供帮助，例如由于很多IOPS，CPU利用率高。多个VNIC可以帮助平衡跨多个内核的网络操作。启用RSS可以帮助您，但是多个VNIC也可以带来好处。如果您有疑问，则可以添加另一个VNIC，然后在两者中平衡ISCSI会议。



    hth，

    麦克风

    \n

    \nWhen using iSCSI, storage traffic will go through the vNICs you have configured for the VM. From a performance perspective there are some cases where having muliple vNICs can help, like when CPU utilization is high due to a lot of IOPs. Multiple vNICs can help to balance the network operations across multiple cores. Enabling RSS helps with this but multiple vNICs can also have a benefit. If you have concerns you could add another vNIC and then balance the iSCSI sessions across the two.

    \n

    \nHTH,

    \nMike","quoteUsername":"mmcghee","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Mikegelhar
    Userlevel 1
    徽章 +9
    您是将卷组呈现给整个VMware群集，然后从中创建数据存储，还是直接将ABS卷组呈现给虚拟SQL节点？要复制与RDMS一起使用的IO分离，您需要使用该选项，以在VMware群集上创建数据存储。这将使您可以分配多个PVSCSI控制器，并将虚拟磁盘分配给VM，就像您习惯用于DBS，LOGS，TEMPDB等一样。请务必检查VMware KB2038869查看您的网络配置是否需要ISCSI端口绑定。如果您有针对ISCSI流量与其他网络的单独的VLAN，则需要端口绑定。对于主机级别的冗余，您需要在每个主机中添加两个VMKernel端口，然后将每个端口中的每个端口绑定到物理NIC。VMware KB2045040解释过程。



    如果您直接从VMS绘制ISCSI，则所有ISCSI配置都在访客中。就像说的那样，所有IO都将通过NIC界面。根据您的IP/VLAN设置，您可能会使用NIC团队或MPIO。请参阅此Microsoft博客以获取更多信息这里。您很可能会使用MPIO。



    无论哪种情况，Nutanix都使用AOS 4.7和使用“外部数据服务IP地址”使多路径变得非常容易。现在，您只需使用一个目标IP即可使用，Nutanix使用外部数据服务IP地址作为虚拟IP来自动管理ISCSI连接并在所有CVM上进行后端MPIO。



    希望我离您的问题不太遥远，此信息可以帮助您更接近您想要的内容。
    2038869 <\/a>to see if your network configuration requires iSCSI port binding. If you have separate VLANs for iSCSI traffic from other networks you'll need port binding. For redundancy at the host level, you'll want two vmkernel ports added to each host for iSCSI and then bind those each of those ports to a physical NIC. VMware KB 2045040<\/a> explains the process.

    \n

    \nIf you're mapping iSCSI directly from the VMs all the iSCSI configuration is all in the guest. Like \ufeff says, all the IO will be going through the NIC interface. Depending on your IP\/VLAN setup you might use NIC teaming or MPIO. See this Microsoft blog for more info     here<\/a>. Most likely you'll be using MPIO.

    \n

    \nIn either case, Nutanix has made multipathing incredibly easy with AOS 4.7 and the use of the \"external data services IP address\". Now you just have one target IP to use and Nutanix uses the external data services IP address as a virtual IP to automagically manage the iSCSI connections and backend MPIO across all CVMs.

    \n

    \nHopefully I wasn't too far off topic from your question and this info helps get you closer to what you're looking for.","quoteUsername":"mikegelhar","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    一种
    徽章 +4
    迈克（S） -

    非常感谢您的回复，基本上，在我们的POC群集上，我正在调整两种配置，以查看我可以从可管理性的角度获得最佳性能以及最简单的内容。如果测试进展顺利（我预计会这样，请将SQL工作负载移至一些新节点）。你们俩都可以评论Nutanix发现的最佳位置，ISCSI映射到VMS，或者呈现卷组并创建数据存储。我看到两者的优点/缺点，好奇是否有人可以对两种方法的好/糟糕/丑陋发出声音。

    \nThanks so much for your responses, basically at this point on our POC cluster I am turning up both configurations to see what I can get the best performance out of and what is easiest from a managability perspective. If testing goes well (which I anticipate it will, move SQL workload over to some new nodes). Can either of you comment on what Nutanix finds as the sweet spot, the iSCSi mapping to the VMs, or presenting the volume groups and creating a datastore. I see pros\/cons with both, curious if anyone could chime in on good\/bad\/ugly of both approaches.","quoteUsername":"adamlw","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Mikegelhar
    Userlevel 1
    徽章 +9
    我的个人偏爱是使用数据存储在虚拟化层处保持存储分配的可见性，以监视工具，基于图像的备份和复制。

    今年早些时候，我在访客（单个VNIC）和基于数据存储的配置中进行了一些比较，发现数据存储配置总是更快。我的测试不是非常科学的，但这是一致的。

    \nEarlier this year I did some comparisons between in guest (single vNIC) and datastore based configurations and found the datastore config was always faster. My testing wasn't extremely scientific, but it was consistent.","quoteUsername":"mikegelhar","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    mmcghee
    秩
    UserLevel 3
    徽章 +17
    我可能会误解，但我认为目标是为在VM中运行的共享磁盘SQL/WSFC提供存储。我们支持的方法是将ISCSI直接用于带有ESXI的VM。您将无法使用数据存储器创建共享磁盘群集（在其中最好使用我们的标准NFS方法），并且我们今天不支持RDMS。
    Mikegelhar
    Userlevel 1
    徽章 +9
    感谢您将我们重新回到...工作的配置也是一个关键考虑因素
    一种
    徽章 +4
    是的，你是对的迈克，对不起，那里有一点漂移。实际上，我们同时进行WSFC和AGS，因此我将在适用的情况下探索这两个选项。感谢您的意见 - 非常感谢。
    条款和条件
    Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
    Functional","cookiepolicy.modal.level2":"Normal
    Functional + analytics","cookiepolicy.modal.level3":"Complete
    Functional + analytics + social media + embedded videos"}}}">
    Baidu