- VMware vSphere Tanzu: Basic vs. Standard vs. Advanced edition - Fri, Sep 17 2021
- Containers and VMware vSphere - Fri, Sep 10 2021
- How to install ESXi 7.0 U2 directly from an HTTP server via a UEFI HTTP boot - Fri, Sep 3 2021
If you successfully pass the VCP7 exam, you automatically receive VCP-DCV 2020 certification without needing to pass the smaller "foundation" exam first (requirements for VCP6.7-DCV).
In fact, the official VMware name for the certification title is not VCP7-DCV, as one would expect, but VMware Certified Professional—Data Center Virtualization 2020 (VCP-DCV 2020). The number increments each year. This change has been here for the past year or two, but IT admins keep calling the exam VCP7-DCV.
To succeed on the exam, you should not rely only on this study guide. You should read the docs as well. We won't be able to cover everything. There is a full documentation set recommended for the exam. The VMware exam blueprint has 80 chapters (objectives). VCP-DCV 2020 certification is the latest certification based on vSphere 7.0.
vSphere high availability (HA) overview ^
VMware vSphere high availability (HA) is able to protect virtual machines (VMs) during hardware failures. If you have a VMware vSphere cluster configured and you activate HA, then if any of your hosts has a hardware problem, the VMs running on that host will be restarted automatically on the remaining hosts in the cluster.
vSphere HA can also protect against application failure by continuously monitoring a virtual machine and resetting it in the event a failure is detected.
If you have a datastore problem, vSphere HA protects against datastore accessibility failures by restarting affected virtual machines on other hosts that still have access to their datastores.
vSphere HA has another capability that can protect virtual machines against network isolation by restarting them if their host becomes isolated.
Activating vSphere high availability (HA) ^
You do not need to install special software in the application or virtual machine. All workloads are automatically protected by vSphere HA. After vSphere HA is configured, no actions are required to protect new VMs.
You can activate vSphere HA by selecting the cluster, and then selecting Configure > vSphere Availability > Edit.
When you activate vSphere HA, there are a couple of things going on in the background. The HA agent is installed on each host in the cluster. The agents can communicate with each other.
There is an election process where one host from the cluster will become a primary host. This depends on a couple of things, such as the total number of mounted datastores, etc. Once the primary host is elected, all the other hosts become "secondary hosts" that listen to the primary host. If the primary host has a problem and becomes unavailable, a new election takes place and a new primary host is elected.
The primary host receives information from vCenter Server on a regular basis. It pulls information which it then passes to the secondary hosts. If there is a host failure, the primary host uses network and datastore heartbeats to verify that a secondary host is offline.
It monitors both network and shared datastores, so it basically double-checks that there is some kind of problem with one of the secondary hosts. It then triggers an HA event, and VMs that were running on the failed secondary hosts are restarted on other hosts in the cluster.
vSphere high availability (HA) host failures ^
- Failure—The host stops functioning. This can be a power supply, motherboard or CPU problem, or the host has a purple screen of death (PSOD).
- Isolation—The host becomes isolated from the network. In this case, the host is running but cannot communicate with other hosts. vSphere HA has detected this because the datastore heartbeat is working.
- Partition—The host loses network connectivity with the primary host but is still connected to other secondary hosts.
When there is a failure, the HA must know what to do. We can configure different options in the case of host failure. Many failure conditions are supported, including host failure, host isolation, VM component protection (datastore with PDL and APD), VM, and application. The different configuration options and settings are available through the Failures and Responses tab via the drop-down lists. Then there are check boxes for each option. For the case of datastore Permanent Device Loss (PDL) or All Paths Down (APD), check with your hardware manufacturer to see whether those options are supported.
vSphere admission control ^
What is vSphere admission control? It is a configuration policy that enables ensuring that vSphere has enough failover capacity in the cluster. By default, a cluster can tolerate one host failure at a time. The maximum is one less the number of hosts in the cluster.
So, for example, you have a cluster with five hosts. You can set the maximum number of host failures to 4.
You can define the host failover capacity by:
Cluster resource percentage—This takes into account a specified percentage of aggregate CPU and memory resources that are reserved for failover.
Slot policy admission control—vSphere HA admission control makes sure that host(s) can fail and there are still sufficient resources in the cluster to failover all the VMs from those hosts.
Dedicated failover hosts—This policy is the least efficient. It reserves host(s) as "spare" host(s). No VMs can run on them because they are used only if an HA event is triggered.
vSphere HA works with other features, such as VMware vSAN or Distributed Resources Scheduler (DRS).
If you are using vSphere HA with vSAN, the pooled vSAN datastore and its separated network traffic are used to detect HA failure. There is only one small issue: you must disable HA to activate VMware vSAN. And vice versa: you can enable vSAN only if vSphere HA is disabled.
There are three policies to choose from in the heartbeat datastores. You can let vSphere automatically select the datastore that will be used for the datastore heartbeats (default), you can use a datastore from a specific list, or you can use datastores from the specified list and complement automatically if needed.
vSphere HA heartbeat datastores
In the last option, if one of the datastores becomes unavailable, vSphere HA will choose a different datastore. If there is no preferred datastore available, vSphere HA picks any available cluster datastore.
Subscribe to 4sysops newsletter!
Final words ^
Be sure to consult other documentation when studying for the exam. VMware vSphere is a large topic that is impossible to squeeze into a single blog post. Check the VCP-DCV 2020 Study Guide at the ESX Virtualization blog for other objectives.