Section 1 – Plan, Install and Upgrade VMware ESX/ESXi
- Objective 1.2 – Upgrade VMware ESX/ESXi
The vSphere 4 Host Update Utility provides a graphical user interface for (Choose Two):
A.upgrading ESX hosts in DRS/HA clusters
B.upgrading standalone ESX/ESXi hosts
C.performing a host compatibility check
D.keeping guest operating systems patched
vSphere Host Update Utility
This tool is for upgrading ESX 3.x/ESXi 3.5 standalone hosts to ESX 4.0/ESXi 4.0 and for patching ESXi 4.0 standalone hosts. A standalone host is an ESX/ESXi host that is not managed in vCenter Server.
When you select a host to be upgraded, the tool performs an automated host compatibility check as a preupgrade step.
Before you upgrade an ESXi host:
A.Save the ESXi configuration using vicfg-cfgbackup s from the vCLI
B.Update the ESXi restore CD with the current ESXi image
C.Save the current ESXi image to another ESXi server
D.Copy the embedded ESXi image to a USB flash drive
vSphere Upgrade Guide ESX 4.0 ESXi 4.0 vCenter Server 4.0 vSphere Client 4.0 , page 71.
Back up the host configuration before you begin a host upgrade.
For more information about the VMware vSphere Command-Line Interface and the vicfg-cfgbackup command, see the vSphere Command-Line Interface Installation and Reference Guide.
vCenter Update Manager is capable of upgrading which of the following (Choose Three):
D.Virtual Machine Hardware
vSphere Update Manager upgrades multiple VMware vSphere components Table . Upgraded Components
Component Upgraded by Update Manager
Virtual machine kernel (vmkernel) Yes
Service console, where present Yes
Virtual machine hardware Yes
Virtual Machine Tools Yes
Guest operating systems Yes, for SP and patch releases.
Additional licensing is required once the number of cores per CPU reaches which of the following?
A.8 or more cores
B.12 or more cores
C.6 or more cores
D.16 or more cores
Essentials for Retail, Essentials Plus for Retail, Standard and Enterprise support 6 cores per CPU. Advanced and Enterprise Plus support 12 cores per CPU.
After upgrading an ESX host to vSphere 4, which of the following three actions should be taken (Choose Three)
A.restore files to the service console
B.connect the host to vCenter if managed
C.boot into Troubleshooting Mode for proper operation
E.verify virtual machine operation
vSphere Upgrade Guide ESX 4.0 ESXi 4.0 vCenter Server 4.0 vSphere Client 4.0, page 79.
After you upgrade an ESX/ESXi host, consider the following:
right-clicking the host in the vCenter Server inventory and selecting Connect. for 60 days. You must assign an upgraded license to your product within 60 days after the upgrade. Use the License Portal and the vSphere Client to configure licensing.
There is no requirement to restore files to the service console after an upgrade
Troubleshooting mode is not a valid mode for a vSphere host
It makes sense to verify virtual machine operation after an upgrade has taken pace.
Before you upgrade an ESX host:
A.back up /var/logs, /usr, /bin and the dmesg output
B.back up /proc, /mnt, /tmp, custom scripts and all VMFS datastores
C.back up /home, /etc/init.d and /boot
D.back up /etc/passwd, /etc/groups, /etc/shadow, /etc/gshadow, custom scripts and local VMFS
vSphere Upgrade Guide ESX 4.0, ESXi 4.0, vCenter Server 4.0, vSphere Client 4.0, page 71
‘Before you upgrade an ESX host, back up the local VMFS file system. This ensures that you will not lose data during the upgrade.
* Back up the files in the /etc/passwd, /etc/groups, /etc/shadow, and /etc/gshadow directories. The /etc/shadow and /etc/gshadow files might not be present on all installations.
* Back up any custom scripts.
* Back up your .vmx files.
* Back up local images, such as templates, exported virtual machines, and .iso files.’
In order to upgrade to vSphere 4,an ESX host must have a /boot partition of at least:
vSphere Upgrade Guide ESX 4.0 ESXi 4.0 vCenter Server 4.0 vSphere Client 4.0 Page 73
Direct, in-place upgrade from ESX 2.5.5 to ESX 4.0 is not supported, even if you upgrade to ESX 3.x as an intermediary step. The default ESX 2.5.5 installation creates a /boot partition that is too small to enable upgrades to ESX 4.0. As an exception, if you have a non-default ESX 2.5.5 installation on which at least 100MB of space is available on the /boot partition, you can upgrade ESX 2.5.5 to ESX 3.x and then to ESX 4.0.
The vSphere 4 Host Update Utility upgrades the (Choose Two):
A.service console if present
B.Virtual machine hardware
vSphere Upgrade Guide, ESX 4.0, ESXi 4.0, vCenter Server 4.0, vSphere Client 4.0, page 67
‘vSphere Host Update Utility Graphical utility for standalone hosts. Allows you to perform remote upgrades of ESX 3.x/ESXi 3.5 hosts to ESX 4.0/ESXi 4.0. vSphere Host Update Utility upgrades the virtual machine kernel (vmkernel) and the service console, where present. vSphere Host Update Utility does not upgrade VMFS datastores or virtual machine guest operating systems.’
An ESX Administrator plans to install additional supported components on the ESX Server that would increase the memory requirements for the Service Console. Which ESX Server partition would also need to be increased during installation as a result?
Mastering VMware vSphere 4 Page 25.
‘As a general rule, swap files are created with a size equal to at least two times the memory allocated to the operating system. The installation process allocates a default amount of 300MB of memory for the Service Console; therefore, the default swap partition size would be 600MB. ‘
‘It might be necessary to increase the amount of memory granted to the Service Console.
…If additional third party applications are needed to run in the Service Console…then more memory may be needed…’
An administrator is in the process of upgrading ESX 3.5 Hosts to vSphere. vCenter Data Recovery has been installed and configured to back up the virtual machines in the datacenter. However, after a scheduled backup it appears that not all of the virtual machines selected were successfully backed up. What is most likely the cause for this issue?
A.The virtual machines which were not backed up are running unsupported Operating Systems.
B.The affected virtual machines did not have the VDR agent installed
C.Some of the virtual machines are on the ESX 3.5 hosts.
D.Some of the virtual machines were running during the backup window.
VMware Data Recovery Frequently Asked Questions (FAQ), April 2009.
VMware Data Recovery is not backward compatible to ESX 3.5 or earlier hosts.
|One Time Purchase||✔||✖||✖||✖||✖|
|100% Pass Guarantee||✔||✖||✖||✖||✖|
|100% Money Back||✔||✖||✖||✖||✖|