Interviews

What’s new with your favorite virtualization companies and executives.

Events

Check out what’s happening in your area, from webinars to lunch and learns.

Blogs

Get the scoop on the latest technology news from industry experts.

How To’s

Step by step instructions on a variety of need to know virtualization topics.

News

Take a look at the industries most recent company and product annoucements.


Home » How To's

How to roll back or downgrade VMware 4.x to 3.x

Submitted by on May 17, 2010 – 11:16 amNo Comment

VMware Infrastructure 3By Brian Suhr

The chance that you might have to do this in the future are pretty small. I can’t think of too many reasons that you might need to rollback your upgraded host. But in case you do I have put together a few steps to show you the way. Make sure to read the risks and understand what you might be in for.

Risks and Considerations

The following risks and considerations must be taken into account before proceeding with a rollback:
  • Any changes made to the ESX 4.x service console are lost after the rollback.
  • Changes made to virtual machines (such as an installation of VMware Tools) persist after the rollback.
  • If you upgraded the virtual machine hardware, the virtual machines will not work after you perform the ESX rollback. To avoid this situation, take a snapshot of the virtual machines before you upgrade the virtual machine hardware. After you run the ESX rollback script, boot into ESX 3.x and revert to the snapshot.
  • Only perform the rollback if you are very familiar with the ESX environment and are comfortable running commands from the service console.

Follow these steps to roll back your installation from 4.x to 3.x

Do not perform this process until you have read and understand the Risks. This cannot be reversed.

1. Log onto the service console as Root

2. Run this command: rollback-to-esx3

Note: This command reconfigures the bootloader to boot into ESX 3.x and removes the ability to boot into ESX 4.0. You can include the optional -f (force) flag. If you omit the -f flag, you are prompted to confirm that you want to roll back to ESX 3.x.

3. Next issue the reboot command or a “shutdown -r now” will also work.

Note: When the host is powering on, you can see that the boot menu has reads ESX 3.x.

4.  After the host boots into ESX 3.x, you can safely delete the ESX 4.0 service console VMDK folder from the VMFS datastore. The service console VMDK folder name has the format esxconsole-<UUID>.

Take a look at the full VMware roll-back Document


Orginally contributed from VirtualizeTips. Read more guides and how to’s on VirtualizeTips.com.

Brian Suhr is a Senior Virtualization Engineer and Architect working for HP Enterprise Services. He’s worked in the IT Industry since 1991, and worked for several companies. He runs the blog virtualizetips to document tips and problems encountered during his projects and reads. A VMware Certified Professional (VCP VI3.5) MCSE on Windows NT – 2000, Cisco CCNA/CCDA. Brian is currently working on upgrading my VCP to vSphere and will be pursuing VMware Certified Design Expert (VCDX) next.

Leave a comment!

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.