Nutanix和NOS 4.1.5上的SQL簇

  • 2015年9月20日
  • 11个答复
  • 1672年的观点
VCDXNZ001
秩
UserLevel 3
徽章 +19
大家好，

只是想让您知道，使用传统的SQL故障转移群集和SQL FCI，或者从第4.1.5号nos Preview中使用任何MSCS / MICCOST / MICROSOFT故障转移群集。这是因为我们已经在ISCSI堆栈中引入了SCSI 3持续保留。要实现一个群集，您需要使用MS ISCSI启动器和Nutanix卷组合同和ISCSI目标，以实现guest INCSI访问。这将成为即将发布的NOS版本的完整功能。请尝试一下，让我们知道您的想法。
\n
\nJust wanted to let you know that using traditional SQL failover clusters and SQL FCI, or any MSCS \/ Microsoft failover cluster is available in tech preview as of NOS 4.1.5. This is because we have introduced SCSI 3 Persistent Reservations to the iSCSI stack. To implement a cluster you need to use the MS iSCSI Initator and the Nutanix Volume Groups contract and iSCSI target for in-Guest iSCSI access. This will become a full GA feature in an upcoming release of NOS. Please experiment with it and let us know your thoughts.","quoteUsername":"vcdxnz001","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

11个答复

VCDXNZ001
秩
UserLevel 3
徽章 +19
使用4.5，故障转移聚类功能现在为GA。如果您希望配置生产SQL簇或其他类型的Windows故障转移簇，请升级到4.5。
Willfulmer
Userlevel 1
徽章 +10
是有1：1的lun关系的最佳做法：卷组还是建议/支持多：1

tempdblun：sqlvg
sysdblun：sqlvg
UserDblun：SQLVG

或者
tempdblun：tempdbvg
sysdblun：sysdbvg
USERDBLUN：USERDBVG

目前是否有一个用VG生长LUN的过程？
（and）我应该认为这不是一个稀薄的供应驱动器，因此使生长更重要。

目前在4.5.0.2上，看不到任何有关调整大小的信息。

将要
会富勒
\n
\nTempDBLUN : SQLVG
\nSysDBLUN : SQLVG
\nUserDBLUN : SQLVG
\n
\nor
\nTempDBLUN : TempDBVG
\nSysDBLUN : SysDBVG
\nUserDBLUN : UserDBVG
\n
\nIs there currently a process to grow a LUN with a VG?
\n(and) should I assume this is not a thin provisioned drive, therefore making growing the LUN even more important.
\n
\nCurrently on 4.5.0.2 and not seeing any information on resizing.
\n
\nWill","quoteUsername":"WillFulmer","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
VCDXNZ001
秩
UserLevel 3
徽章 +19
嗨，威尔

使用4.5.0.2，最佳点是每个VG/目标的4个LUN/VDISK。这是一个表演的甜蜜点，而不是限制。您可以配置更多的东西，但是Lun的CPU与随机IO绑定在CVM中，这将影响性能。可以从单个LUN/目标中获得20K IOP（8KB单个IO模式）或更大的方法，可以通过多个LUN/目标实现更高的目标。当然，取决于平台。

对于4.5.0.2中的SQL DB，如果您只需要4个驱动器，则应该可以使用单个目标/VG。那将是最简单的配置。每个LUN/VDISK都是薄的。在应用程序写入数据之前，我们不会消耗存储资源。

在此阶段，我认为我们没有办法扩展与目标连接的现有VDISK/LUN。因此，扩展大小的过程将是向目标添加另一个VDISK，然后使用宾客工具扩展卷。我将进一步检查并回复此线程。
\n
\nWith 4.5.0.2 the sweet spot is 4 LUNs\/vDisks per VG\/Target. This is a performance sweet spot and not a limitation. You can configure more than that, but LUN's become CPU bound in the CVM with random IO and that will impact performance. 20K IOPS (8KB single IO pattern) or more is acheivable from a single LUN\/Target, higher can be achieved with multiple LUN's\/Target. Depending on the platform being used of course.
\n
\nFor a SQL DB in 4.5.0.2 you should be able to use a single Target\/VG if you just need 4 drives. That would be the easiest configuration. Every LUN\/vDisk is thin provisioned. We don't consume storage resources until the point that the application goes to write data.
\n
\nAt this stage I don't think we have a way to extend an existing vDisk\/LUN connected to a target. So the process to expand the size would be to add another vDisk to the target and then use in guest tools to extend the volume. I'll check into this more and reply to this thread.","quoteUsername":"vcdxnz001","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
VCDXNZ001
秩
UserLevel 3
徽章 +19
嗨

压缩，DEDUPE和EC-X都得到了支持。就ADFS/NDFS而言，LUN就像其他VMDK一样。
\n
\nCompression, Dedupe, and EC-X are all supported. As far as ADFS\/NDFS is concerned the LUN is just a vDisk on our system just like any other VMDK would be.","quoteUsername":"vcdxnz001","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
t
徽章 +3
你们是否曾经发现VG扩展功能是可能的还是在路线图上？
mmcghee
秩
UserLevel 3
徽章 +17
从4.6开始使用ACLI（VG.Disk_update）扩展VG磁盘，但不能使用磁盘，这意味着必须将VG分离。热扩展是已知的要求，但今天不存在。
C
徽章 +5
作为现有客户，缺乏在线扩展数量组磁盘是阻止我们一起杀死SAN（Windows故障转移群集）。

我们希望此功能在下一个或接近未来的版本中出现吗？专门针对Hyper-V客户。

-e
\n
\nDo we expect this feature to come in the next or a near-future release? Specifically for Hyper-V customers.
\n
\n-E","quoteUsername":"Coleman","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
VCDXNZ001
秩
UserLevel 3
徽章 +19
嗨，科尔曼，

这已经可以在支持门户和Nutanix圣经上可用。自AOS 4.1.5和4.5以来，我们支持Windows故障转移群集。还有一个最佳实践指南，可在我们的网站上使用块服务。因此，可能是时候重新评估它了。

//www.jhbzcj.com/products/features/acropolis-block-services/

https://next.nutanix.com/t5/nutanix-connect-blog/putting-acropolis-blocpis-services-services-abs-through-its-paces/ba-paces/ba-paces/ba-pacle/11433

https://portal.nutanix.com/#/page/docs/details?targetId=web_console_guide-prism_v4_7:wc_block_services_requirements_r.html

https://portal.nutanix.com/#/page/docs/details?targetId=command_ref-acr_v4_6:man_ncli_volumegroume-group_auto_r.html

https://portal.nutanix.com/#/page/docs/details?targetId = advanced_admin-aos_v4_7:vm__failover_cluster_cluster_create_t.html

https://vimeo.com/182407000

http://nutanixbible.com/#anchor-block-services-76

http://itbloodpressure.com/2015/10/09/nutanix-only-hci-with-with-with-windows-failover-clustering/

http://www.mcghem.com/2015/09/18/microsoft-sql-server-server-high-availability-options-options-on-nutanix/
\n
\nThis is already available and on the support portal and on the Nutanix bible. We have supported Windows Failover Clusters since AOS 4.1.5 and 4.5. There is also a best practice guide for Block Services availble on our web site. So it could be time to re-evaluate it.
\n
\n\/\/www.jhbzcj.com\/products\/features\/acropolis-block-services\/<\/a>
\n
\nhttps:\/\/next.nutanix.com\/t5\/Nutanix-Connect-Blog\/Putting-Acropolis-Block-Services-ABS-through-its-Paces\/ba-p\/11433<\/a>
\n
\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Web_Console_Guide-Prism_v4_7:wc_block_services_requirements_r.html<\/a>
\n
\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Command_Ref-Acr_v4_6:man_ncli_volume-group_auto_r.html<\/a>
\n
\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Advanced_Admin-AOS_v4_7:vm__failover_cluster_create_t.html<\/a>
\n
\nhttps:\/\/vimeo.com\/182407000<\/a>
\n
\nhttp:\/\/nutanixbible.com\/#anchor-block-services-76<\/a>
\n
\nhttp:\/\/itbloodpressure.com\/2015\/10\/09\/nutanix-only-hci-vendor-with-windows-failover-clustering\/<\/a>
\n
\nhttp:\/\/www.mcghem.com\/2015\/09\/18\/microsoft-sql-server-high-availability-options-on-nutanix\/<\/a>","quoteUsername":"vcdxnz001","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
VCDXNZ001
秩
UserLevel 3
徽章 +19
抱歉，只需阅读这是Lun's的在线扩展即可。那是两个阶段问题。除非您使用Veritas，否则一个Windows簇不支持在线扩展Lun。其次，我们将在下一个软件版本中支持在线扩展。扩展到那时的方法是添加一个额外的磁盘，可以在线完成。
C
徽章 +5
感谢您的答复，但我认为您可能会错过我的关注。

除非我误会了，否则我们将无法在不脱机故障转移群集的情况下调整属于卷组的磁盘 - 这就是阻止我们在fialover群集中使用NTX块服务的原因。

我是否误会了，我们可以在使用这些磁盘时调整大小？

**编辑**
刚看到您的第二个答复。谢谢。我们非常期待这一热点，因为目前我们能够使用属于NetApp和equilogic Sans的LUN来做到这一点。
\n
\nUnless I'm mistaken, we are not able to resize disks that belong to a Volume Group without taking the Failover Cluster offline - that's what is preventing us from using NTX Block Services in our fialover clusters.
\n
\nAm I mistaken and we can resize these disks while they're being used?
\n
\n**Edit**
\nJust saw your second reply. Thank you. We are very much looking forward to that hot-expand as we're currently able to do this with our Luns that reside on our NetApp and Equilogic SANs.","quoteUsername":"Coleman","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

回复


条款和条件
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