问题

vSphere 7更新1和vSphere群集服务（VCLS）

  • 2021年2月2日
  • 2回复
  • 1109观点
戴维德
UserLevel 2.
徽章 +4

vCenter 7.0U1C和本地或共享存储上的vSphere群集服务VM。

在从6.5u3到7.0u1c（它工作的FINE WOURION SOURION）的6.5U3到7.0U1C升级后，启用了DRS和/或HA的每个VMware集群获取3个新VCLS（非常小的VMS W 2GB存储/ .13GB RAM）。

当NCC运行时，它注册3警告在SATADOM中运行VM。我会认为，甚至他们（今天）（今天）是什么（很少），这会磨损SATADOM或M.2吗？

这将是G4 / G5（W SALADOMS）的关注，而不是G6 / G7（M.2）？“

虽然VCLS可以移动到共享存储，但在NX集群停止期间，它们不会被移回本地存储？

（就像指出这是在实验室环境中完成的，不在生产中......在升级进度期间，没有比特和字节受到损害。）

vCenter 7.0U1c and vSphere Clustering Service VMs on local or shared storage.<\/p>

After test upgrading vCenter from 6.5U3 to 7.0U1c (which worked just fine w 0 issues), every vmware cluster with DRS and\/or HA enabled gets 3 new vCLS (very tiny VMs w 2GB storage\/.13GB RAM).<\/p>

When NCC is ran it registers 3 WARNs that there are VMs running on the SATADOM\u2019s.\u00a0I would assume that, even what (little) they do (today), would this wear out Satadom\u2019s or M.2\u2019s?<\/p>

Would this be a concern for G4\/G5\u2019s (w Satadoms) and not G6\/G7\u2019s (M.2\u2019s)?\u201d<\/p>

While vCLS can be moved to shared storage, wouldn\u2019t they be moved back to local storage during an NX cluster stop?<\/p>

(Like to point out this was done in a LAB environment, not in Production\u2026 no bits nor bytes were harmed during the upgrade progress.)<\/p>","quoteUsername":"DavidN","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

2回复

alona.
秩
UserLevel 6.
徽章 +5

嗨Davidn，

不要逃避你的余下问题（仍然检查），但要解决您所在的一些问题，似乎VCLS被放置在本地存储上作为最后的度假期权

VCLS VM的数据存储选择

基于对群集中的主机连接的所有数据存储来自动选择VCLS VMS的数据存储。如果群集中有包含连接到数据存储的免费保留DRS插槽，则更有可能选择数据存储区。如果可能在选择本地数据存储之前，该算法试图在共享数据存储中放置VCLS VM。优先一个具有更多可用空间的数据存储，并且算法尝试不会在同一数据存储上放置多个VCLS VM。您只能在部署和供电后更改VCLS VM的数据存储。

来源

还：

如果没有可用的共享存储，则代理VMS将放在本地存储上。如果在ESXi主机上配置了共享存储之前，请在使用VSAN时形成群集，强烈建议将VCLS代理VM移动到共享存储之后。

来源

在佩戴本地存储方面，我会将这个问题解决了VMware，因为它们更具配备以回答它。他们毕竟设计了它。

至于迁移vcls在群集停止期间回到本地存储，您将首先关闭它们，然后停止群集？

Hi DavidN,<\/p>

Not evading the rest of your questions (still checking) but to address some of what you are asking, it seems that vCLS is placed on the local storage as the last resort option<\/p>

Datastore selection for vCLS VMs<\/h2>

The datastore for vCLS VMs is automatically selected based on ranking all the datastores connected to the hosts inside the cluster. A datastore is more likely to be selected if there are hosts in the cluster with free reserved DRS slots connected to the datastore. The algorithm tries to place vCLS VMs in a shared datastore if possible before selecting a local datastore. A datastore with more free space is preferred and the algorithm tries not to place more than one vCLS VM on the same datastore. You can only change the datastore of vCLS VMs after they are deployed and powered on.<\/p><\/blockquote>

Source<\/a><\/p>

\u00a0<\/p>

Also:<\/p>

If no shared storage is available, the agent VMs are placed on local storage. If a cluster is formed before shared storage is configured on the ESXi hosts, as would be the case when using vSAN, it is strongly recommended to move the vCLS agent VMs to shared storage after.<\/p><\/blockquote>

Source<\/a><\/p>

In terms of wearing off local storage, I would address that question to VMware as they are more equipped to answer it. They designed it after all.<\/p>

As for the migration of the vCLS back to the local storage during the cluster stop, wouldn\u2019t you power them off first and then stop the cluster?<\/p>","quoteUsername":"Alona","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

戴维德
UserLevel 2.
徽章 +4

如果VCLS VM电源关闭，则立即启动它;如果一个人以某种方式删除，则会提出一个新的，以替换它（因此任何VMware主机集群中会有3个）。

因此，只有存储vMotion是一个选项 - 根据许可证类型，每个人都可能无法使用。

在任何情况下，我们都成功回到了上一个vCenter（遵循支持的过程，并回来了。）可能会等一下，直到其中一些问题得到解决。现在，我们要去了最新的6.7 ......之后可以在没有任何问题的情况下关闭/删除VCLS。

If a vCLS VM is powered off, it\u2019s powered back on immediately; if one is somehow deleted, a new one is brought up to replace it (so there would be 3 on any vmware Cluster of hosts).<\/p>

So, only storage vMotion is an option - which depending on license type may not be available to everyone.<\/p>

In any case, we successfully rolled back to the previous vCenter (followed supported process and all came back ok.) Probably going to wait a while until some of these questions are resolved. For now we\u2019re going w latest 6.7\u2026 vCLS can be powered off\/removed afterwards without any issues.<\/p>","quoteUsername":"DavidN","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

回复


Baidu