Saturday, 03 April 2021 15:56

HANA on VMware – Maintenance

Written by Jens Gleichmann
Rate this item
(0 votes)
Source https://blogs.sap.com/2021/04/04/hana-on-vmware-maintenance/
“© 2020. SAP SE or an SAP affiliate company. All rights reserved.” “Used with permission of SAP SE”

A lot of customers are using VMware as Hypervisor to run the HANA workload. Since the initial certification of this platform there are some limitations regarding features and sizing. Some of this limitations depending on the vSphere version. With every maintenance you have to take attention to compatibility and parametrization. The most VMware administrators don’t know any of the SAP HANA dependencies. May be this blog is the chance to bring them and your landscape up-to-date before you get support issues.

So, we have two possibilities as maintenance scenarios: the update of the vSphere version and a hardware change (security is another topics which I don’t want to discuss in the HANA context of VMware, because there is no SAP dependency). Both can take place due to support, limitation or feature dependencies.

  1. vSphere version
  2. Hardware change
  3. Miscellaneous


1. vSphere version

At first check if your vSphere version is supported with your current hardware. I heard from some customers that the matrix on the wiki page is pretty hard to interpret because it is too big and not handsome.

Long story short: Haswell and Broadwell are currently not supported for vSphere 7.0+. As you can see it is planned for Broadwell. I will update the blog if anything changes.

This means with these old processors (Haswell and Broadwell) you can max. go for vSphere 6.7 U3.

Source: ©2021 VMware, Inc

If you want to go for vSphere 7.0 you have to buy new hardware. If you have such new processor architecture and want to migrate your VMs via vMotion you have to check the EVC compatibility (see below).

Attention:

vCLS: Starting with vSphere 7.0 the VMware Clustering Services vCLS needed to be considered for the sizing. For details check Erik’s blog.
vMotion: VM moves over CPU families limits (e.g. Broadwell => Cascade Lake) should be handled carefully due to some limits and performance brakes. Check the EVC modes and compatibilities, but I recommend a general VM restart if you migrate VMs between CPU families although the EVC compatibility is guaranteed.
EVC: EVC is short for Enhanced vMotion Compatibility. EVC allows you to migrate virtual machines between different generations of CPUs.

Source: ©2021 VMware, Inc

Why you should go for vSphere 7.0? Normally the virtual performance overhead is about 10-15%. This is the factor the sizings are calculated in the past.

Continue reading here
Read 48 times

Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.