Patching a Production Stretched Cluster with VMware Update Manager

Patching a Production Stretched Cluster

Question

An administrator is patching a production Stretched Cluster using VMware Update Manager.

Which statement is accurate?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

A.

In a stretched cluster, two or more clusters are stretched across geographical locations to provide high availability and disaster recovery capabilities. One of the key components in a stretched cluster is the witness host, which is used to provide tie-breaking and quorum functionality in the event of a split-brain scenario.

When patching a stretched cluster using VMware Update Manager, it is important to consider the impact on the witness host. The correct answer to the question depends on the version of VMware vSphere and the specific requirements of the stretched cluster environment.

If the stretched cluster is running on vSphere 6.7 or later and is configured with a vSAN witness host, then option A is correct. The witness hosts can be patched using normal patch processes with VMware Update Manager. It is recommended to patch the witness hosts first before patching the other hosts in the stretched cluster.

If the stretched cluster is running on vSphere 6.5 or earlier or is not configured with a vSAN witness host, then option B is correct. Witness hosts cannot be patched or upgraded using VMware Update Manager. In this case, the witness host must be patched manually by following the vendor's instructions.

Option C is incorrect. Even though the witness host does not store data, it is an important component in the stretched cluster environment and must be patched or upgraded as required.

Option D is also incorrect. There is no need to delete and redeploy the witness host. If a new witness host is required, it can be added to the stretched cluster as a new host, and the existing witness host can be removed from the cluster.