View source for Updating vCenter 6.5 with DC-DR replication enabled and vCenter HA enabled to 6.7U2

[[Main_Page|Home]] > [[VMWare platform]] > [[VMWare vCenter]] > [[Updating vCenter 6.5 with DC-DR replication enabled and vCenter HA enabled to 6.7U2]]

It is possible to upgrade vCenter 6.5 with DC-DR replication configured with SRM and vSphere replication 8.x without replications getting affected (Stopped / Disabled).   For this we mount vCenter 6.7.0U2 ISO file and run the GUI installer and go through the ugprade process.   First update DR PSC and vCenter (Assuming cold DR).  Then after 24 hours of observation update DC PSC and vCenter.   Check the compatibility of new vCenter version in VMWare interoperability matrix - https://interopmatrix.vmware.com/#/Interoperability while planning the upgrade.


Note that from 6.7.0 onwards it is recommended to have embedded PSC.  For that first upgrade PSC and vCenter from 6.5 to 6.7.  Then go via converge process to convert from external PSC to embedded PSC.
Refer: 
* https://kb.vmware.com/s/article/60229
* https://virtualblog.nl/2019/08/23/vcenter-server-converge-psc-from-external-to-embedded/


However, if there is vCenter HA enabled on existing vCenter 6.5 then there is a problem.  We cannot disable HA with HTML 5 UI and vCenter upgrade requires HA to be disabled before we can upgrade from 6.5 to 6.7.  For this use following steps to disable HA:
# In work nodes note the following for all three (Active / Passive / Witness):
#: ESXi host
#: IP addresses and VLANs
#: Datastores
# Then login into each vCenter appliance (ACtive / PAssive and Witness) via ESXi console  ('''Note use of ESXi console instead of vCenter console, as during next steps vCenter console would stop working''')
# Login into each vCenter appliance using ESXi console as root and open shell
# In each appliance type:
#:<pre>
#:: ip addr show
#:</pre>
#: and find which appliance is active (Has vCenter IP address mapped to vCenter FQDN) and which other is passive.  
# Note that there are '<tt>vcha</tt>' and '<tt>vcha-reset-primary</tt>' commands to change which node is active / which is passive.  We did not need to try that as in our case desired node was already active.  
# Poweroff the passive and witness appliance using:
#:<pre>
#:: poweroff
#:</pre>
# Now the vCenter UI would stop working and its IP will also not ping.  At this poing remove vCenter HA configuration from active node using:
#:<pre>
#:: destroy-vcha -f
#:</pre>
# After this reboot the vCenter node so that it becomes standalone.
#:<pre>
#:: reboot
#:</pre>
# Ideally after 24 hours of observation Delete the older witness and PSC appliances.

Refer:
* https://communities.vmware.com/t5/VMware-vCenter-Discussions/Remove-vCenter-HA-6-5-when-flash-is-gone/td-p/2822634
* https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.avail.doc/GUID-BB70E40A-B429-46E3-BD12-D493D4D9FDD4.html
* https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-FE5106A8-5FE7-4C38-91AA-D7140944002D.html
* https://nolabnoparty.com/en/recover-failed-vcenter-ha/




[[Main_Page|Home]] > [[VMWare platform]] > [[VMWare vCenter]] > [[Updating vCenter 6.5 with DC-DR replication enabled and vCenter HA enabled to 6.7U2]]