Specifications

c Enter a name and optionally a description for the snapshot.
d (Optional) Select the Take a snapshot of the memory for the virtual machine check box.
9 Click Next.
10 Review the Ready to Complete page, and click Finish.
Planning Downtime for Virtual Machines
Plan downtime for each virtual machine during the upgrade process. Typically, this downtime occurs
during the virtual machine upgrade and the VMware Tools upgrade. Depending on your upgrade plan,
some virtual machine downtime might be required during the ESX upgrade.
If an ESX/ESXi host is not managed by vCenter Server, you cannot use vMotion to move virtual machines.
The virtual machines must have some downtime when the ESX/ESXi host reboots after upgrade.
You might not have to shut down more than a single virtual machine at any given time. You can stagger
virtual machine downtimes to accommodate a schedule convenient to you and your customers.
For example:
n
If your virtual machine users are located in diverse time zones, you can prepare by migrating virtual
machines to specific hosts to serve a given time zone. This way you can arrange host upgrades so that
virtual machine downtime occurs transparently outside business hours for that time zone.
n
If your virtual machine users operate around the clock, you can delay downtime for their virtual
machines to normally scheduled maintenance periods. You do not need to upgrade any stage within a
certain time period. You can take as long as needed at any stage.
Downtime for Upgrading Virtual Machines
When you upgrade virtual machines, the required downtime depends on the guest operating system.
When you upgrade VMware Tools, expect the following downtime:
n
No downtime is required for vCenter Server.
n
No downtime is required for ESXi hosts.
n
You must reboot Microsoft Windows virtual machines at the end of the upgrade procedure, or later, for
the upgrade take effect.
n
On Windows guest operating systems, you must reboot the virtual machine three times when you
upgrade VMware Tools and the virtual hardware.
n
For Linux, NetWare, and Solaris guest operating systems, no reboot is required at the end of the
procedure.
During the virtual hardware upgrade, you must shut down the virtual machine for all guest operating
systems.
Table 7-2 summarizes the downtime required by guest operating system and by upgrade operation.
Table 7‑2. Virtual Machine Downtime by Guest Operating System
Guest Operating System Upgrade VMware Tools Upgrade Virtual Hardware
Linux No downtime. Downtime for shut down and power on of
virtual machine.
NetWare
Solaris
Microsoft Windows Downtime for reboot of guest
operating system.
vSphere Upgrade
156 VMware, Inc.