Quantcast
Channel: VMware Communities: Message List - vSphere Upgrade & Install
Viewing all articles
Browse latest Browse all 11859

Re: Adding more ESX hosts and upgrading at the same time. What's the preferred order of operations here?

$
0
0

The Steps that you must follow

 

- Upgrade vCenter Server

- Upgrade ESX hosts (because we are doing a hardware refresh we are just going to install 5.5 on our new hosts and add them to the cluster and then decommission our existing)

- Upgrade VMWare Tools

- Upgrade Datastores



ESXi 5.5 has these storage requirements:

  • Installing ESXi 5.5 requires a boot device that is minimum 1GB in size. When booting from a local disk or SAN/iSCSI LUN, a 5.2GB disk is required to allow the creation of the VMFS volume and a 4GB scratch partition on the boot device. If a smaller disk or LUN is used, the installer attempts to allocate a scratch region on a separate local disk. If a local disk cannot be found, the scratch partition (/scratch) is located on the ESXi host ramdisk, linked to /tmp/scratch. You can reconfigure /scratch to use a separate disk or LUN. For best performance and memory optimization, VMware recommends that you do not leave /scratch on the ESXi host ramdisk.

  • To reconfigure /scratch, see Set the Scratch Partition from the vSphere Client in the vSphere Installation and Setup Guide.

  • Due to the I/O sensitivity of USB and SD devices, the installer does not create a scratch partition on these devices. As such, there is no tangible benefit to using large USB/SD devices as ESXi uses only the first 1GB. When installing on USB or SD devices, the installer attempts to allocate a scratch region on an available local disk or datastore. If no local disk or datastore is found, /scratch is placed on the ramdisk. You should reconfigure /scratch to use a persistent datastore following the installation.

  • In Auto Deploy installations, the installer attempts to allocate a scratch region on an available local disk or datastore. If no local disk or datastore is found /scratch is placed on ramdisk. You should reconfigure /scratch to use a persistent datastore following the installation.

  • For environments that boot from a SAN or use Auto Deploy, it is not necessary to allocate a separate LUN for each ESXi host. You can co-locate the scratch regions for many ESXi hosts onto a single LUN. The number of hosts assigned to any single LUN should be weighed against the LUN size and the I/O behavior of the virtual machines.

Viewing all articles
Browse latest Browse all 11859

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>