vCenter HA (at least VCSA6.5 and above)

https://mp.weixin.qq.com/s/P2B6KwSyyVAnNYZ8U0FaMg

I believe no one would pay attention to the protection of vCenter, in particular, the use of these functions rely vCenter DRS, the distributed switch, etc. (Note vSphere HA does not depend vCenter), from vSphere 4.x, 5.x, 6.x, VMware vCenter are constantly protection against the introduction of solutions such as vCenter Server Heartbeat; myself in the implementation process, also used such as VM cloning, vCenter database backup, virtual machine backup vCenter, vCenter virtual machine replication and other methods , but now it seems, the best and easiest way is to use vCenterHA, I share vCenter HA deployment method for everyone below.

 

First introduced to the vCenter HA architecture

 

 Simply put, is already deployed to vCenter ServerAppliance (hereinafter referred to as VCSA) cloned two new virtual machine, as a passive node, another node as a witness; the owner of three nodes between the need to establish a private network, data copy and heart failure.

About (hereinafter referred to as PSC) in accordance with the manual mode, but also architecture and Platform Server Controller, the following two points:


 

Due to the use of external PSC deployment relatively rare, the following experiments will be embedded PSC way:

Requirements:

    You must use VCSA deploy vCenter, Windows does not have this version of vCenter welfare

    You must use at least version 6.5

    Need to open VCSA SSH before deployment

    To pre-planned vCenter HA network, add up the relevant Port Group on the host

 

In my experiment, I used the latest environmental vSphere 6.7:

VCenter IP address is: 192.168.240.7

vCenter HA network planning:

Active Node: 10.10.10.9/24
Passive Node:10.10.10.10/24
Witness:   10.10.10.11/24

在相关的主机上添加了一个名为”vCenter HA”的Port Group

还要检查下vCenter的SSH有没有打开,如果没有打开,可以访问https://your-vCenter-ip:5480,如下图:

    这些都准备就绪,就可以启用vCente HA配置,但很可惜,需要打开旧的flash界面,HTML5界面上,这个功能缺失了!

在上述页面上需要分别配置vcsa-9-peer,和vcsa-9-witness

这些设置做好后,按完成,开始部署;过一会,系统会克隆出被动节点,见证节点。

系统开始配置HA网络,注意这个时候,同vCenter的连接网络会中断,这个是正常现象,需要刷新下页面,重新进行登陆;登陆后,可以看到vCenter HA的状态。

可以尝试下故障切换

Vcenter的IP 地址会开始无法PING通

在我的这个环境中

需要大约5-6分钟的时间,可以重新登陆,会注意到之前的主动节点和被动节点发生了对调。

我理解这个过程是当前的主动节点上的服务被中断,被动节点上的服务需要启动,所以需要几分钟的时间,这期间,vCenter无法使用。

你也可以通过POWER OFF主动节点来模拟故障,看到的情形类似以上的描述。

你还可以对vCenter HA进行如下的操作:

总之,只需要大约十多分钟左右的时间,你就可以完成vCenter HA的部署,管理十分方便,vCenter在故障的时候,需要5分钟(依赖实际环境等因素)左右的时间切换,特别提醒一下,就是这个功能不需要额外的许可,并不需要购买两个vCenter的许可,只要满足必要的条件,大家就可以用这个方案去提高 vCenter的可用性。

发布了3 篇原创文章 · 获赞 20 · 访问量 4万+

Guess you like

Origin blog.csdn.net/z136370204/article/details/104050884