11 best practices for upgrading to ESX 3.5 and VirtualCenter 2.5

Upgrading to ESX3.5 and VirtualCeter 2.5 Best Practices is a VMware KB article that lists best practice recommendations when performing the VI upgrade. As explained in the article:

This document provides additional steps which may be useful when upgrading to ESX 3.5 and VirtualCenter 2.5. It is assumed at this point that you have also read the Upgrade Guide.

Although the article contains 11 items in the list, in my opinion the last few are common steps (place the cd in the cd-rom drive of the host etc.) and not really best practices.
Regardless, review the following before performing the upgrade and follow these recommendations to minimize trouble.

  1. Backup your VirtualCenter database. VMware recommends detaching the database and copying it somewhere safe.
  2. Grant the System DSN user of the VirtualCenter Database db_owner privileges on the MSDB database as well as the VirtualCenter database. Ensure that your ODBC System DSN is using the proper driver. You must have a SQL Server driver if your database is SQL 2000, and SQL Native Client driver if using SQL 2005.
  3. If your ESX Server host is in a DRS or VMware High Availability (HA) Cluster remove it from the cluster so no virtual machines migrate to the ESX Server host.
  4. If possible VMotion all virtual machines off the host to be upgraded. If not, power them down gracefully and power off the ESX Server host.
  5. Log in to your VirtualCenter server with a local Administrator account to run the installation, do not use a domain administrator.
  6. Perform the upgrade to VirtualCenter to 2.5 and ensure all your data is visible in VirtualCenter 2.5 after the upgrade. Ensure no processes are running that conflict with the ports that VirtualCenter uses, such as IIS.
  7. If there is a SAN connected to your ESX Server host detach the SAN before continuing with the upgrade.
  8. Confirm that all the virtual machines are now migrated from the ESX Server host or powered down, and that ESX Server host is no longer part of an VMware HA or DRS cluster.
  9. Download the newest version of the ESX operating system ISO image and burn it to CD.
  10. Place the CD in the CD-ROM drive of the host and boot from the CD.
  11. Install ESX Server 3.5 with a fresh install or upgrade.

    Note: A fresh install wipes out all previous network configuration.

Related Posts

Tags: , , , , , , , , ,

Leave a Reply

*
To prove you're a person (not a spam script), type the security word shown in the picture. Click on the picture to hear an audio file of the word.
Click to hear an audio file of the anti-spam word

Subscribe



Add to Google Reader or Homepage
Subscribe in NewsGator Online
Add to netvibes
Add to Plusmo

Advertisements
INSANE

Support VM /ETC! Virtually Insane

Use the new INSANE page for general comments and questions.
UserOnline