12.4.1 vSphere Update Manager Configuration
To determine database patch repository sizing, use the
VMware vSphere Update Manager Sizing Estimator at
http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-update-manager-60-sizing-estimator.xls. For instance, you can base a vSphere Update Manager design on the following assumptions:
• No remediation of VMs
• Remediate ESXi 6.0+ hosts
• 1 concurrent ESXi host upgrade
• Patch scan frequency for hosts: 4 per month
• Upgrade scan frequency for hosts: 1 per month
The following table provides a sample design configuration for vSphere Update Manager. As with other platform design considerations, the goal for a service provider, who deploys multiple instances of vSphere Update Manager across multiple platforms, is to maintain consistency in order to simplify operational management of the environment.
Table 32. Sample vSphere Update Manager Configuration
Attribute | Specification |
Patch download sources | Select Download ESXi 6 patches De-select Download ESXi 3, 4 and 5 patches or as appropriate for the environment |
Shared repository | D:\vCenterUpdateManager\vSpherePatches |
Proxy settings | None |
Patch download schedule | Every Sunday at 12:00AM EST |
Email notification | TBD by Customer |
vSphere Update Manager baselines to leverage | Critical and non-critical ESXi host patches VMware Tools upgrade to match host |
Virtual machine settings | N/A |
ESXi host settings | Host maintenance mode failure: Retry Retry interval: 30 Minutes Number of retries: 3 |
vApp settings | N/A |
Note vSphere Update Manager does not address the issue of vCenter Server or Platform Services Controller component patching. Administrators are required to evaluate patches and updates to vCenter Server and the Platform Services Controller and apply those manually as required.