问题

ESXi修补和文件

  • 2020年4月27日
  • 2回复
  • 1795年观点
D.

3节点群集运行vCenter / ESXi6.7

还运行文件。

如果要修补的特定主机上的文件VM是否会关闭或移动？

我知道控制器VM应该只是关闭。

此外，我想我已经看过我可以在某处/以某种方式将ESXi补丁装入棱镜（元素，起动器，5.10.9）和棱镜将管理动作和关机？

谢谢

3 node cluster running vCenter \/ ESXi6.7<\/p>

Also running Files.<\/p>

Should the Files VM on the\u00a0particular host\u00a0to be patched be shut down or moved?<\/p>

I know the Controller VM should just be shut down.<\/p>

Also, I think I\u2019ve seen mention that I could load the ESXi patches somewhere\/somehow into Prism(Element, Starter, 5.10.9) and Prism would manage the moves and shutdown?<\/p>

Thanks<\/p>

\u00a0<\/p>","quoteUsername":"DarrylO","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

2回复

V.
徽章 +1

嘿达里洛，

从我所知道的，FSVM-S可以在群集中自由vMotion-ed（这是Drs无论如何可以在群集上做什么），并且它们可以在这种意义上被视为UVM。很高兴被专家纠正（如本周晚些时候开始修补）。

随着修补，已经在愿望清单上。事实是，虽然您确实可以通过一键更新上传二进制攻击并推送，但您无法立即上传多个文件。一次只有一个。因此，如果您在主机上部署ESXi更新（累积）或升级ESXi时，可能会有所帮助。但是通过正常修补，您可以在其中有多个文件，一键无用。我的意思是，嗯，你可以逐个推动补丁，等待在每个补丁后等待滚动的重启。但从经验中，它更快（并且让我们是诚实的，更方便的）使用VUM和Patch主机，但处理CVM关机并手动启动，并等待在每次重新启动后返回棱镜的数据恢复。仍然非常痛苦。(A side note, with recent experience of 6.0->6.7 upgrade, I’d certainly refrain from rolled ESXi version push as well - too many cases when the host is up, but before moving on to the next one, you have to attend a number of things first.) In summary, One-Click for hypervisor obviously works fine for AHV, but ESXi still needs to maintained in its own way with the overhead of handling CVMs and going one-by-one.

希望这可以帮助。

Hey DarrylO,<\/p>

\u00a0<\/p>

From what I know, the FSVM-s\u00a0can be freely vMotion-ed across the cluster (this is what DRS can be doing on your cluster anyway), and they can be treated as UVMs in that sense. Happy to be corrected by experts (as going to start patching later this week).<\/p>

\u00a0<\/p>

With patching, that has been in a wish-list for years. The thing is, although you indeed can upload a binary in to PRISM and push via One-Click Update, you cannot upload multiple files at once. Only one at a time. So it may help in case when you deploy an ESXi Update (cumulative), or upgrade ESXi across the hosts. But with normal patching, where you can have multiple files, One-Click is of no use. I mean, well, you can push the patches one by one, waiting for rolled reboots after each patch. But from the experience, it\u2019s quicker (and let\u2019s be honest, more convenient) to use VUM and patch hosts one by one, but handle CVM shutdowns and starts manually, and wait for Data Resilience to return to OK in PRISM after each reboot. Still very painful. (A side note,\u00a0with recent experience of 6.0->6.7 upgrade, I\u2019d certainly refrain from rolled ESXi version push as well - too many cases when the host is up, but before moving on to the next one, you have to attend a number of things first.) In summary, One-Click for hypervisor obviously works fine for AHV, but ESXi still needs to maintained in its own way with the overhead of handling CVMs and going one-by-one.<\/p>

Hope this helps.<\/p>","quoteUsername":"VictorKiwi","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

D.

感谢您对ESX的“一份文件”的澄清。

Thanks for the clarification on the \u201cone file at a time\u201d info for esx.<\/p>","quoteUsername":"DarrylO","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

回复


Baidu