RHEV 2.2 to 3.0 Manager migrating
Red Hat provides a RHEV Upgrade Helper to help you upgrade your RHEV. All you need to provide is information about your upgrade path. We will not only present you the steps to upgrade RHEV, but we'll also give you some extra steps that will prevent known issues specific to your upgrade scenario.
For additional information and manual upgrade steps, please read the section below.
Important: For the procedure described in this guide, make sure you use version 3.0.0.20 or later of the rhevm-migration-tool RPM. This version is available through Red Hat Network, so you no longer need to contact Red Hat directly to get it.
If you are currently running Red Hat Enterprise Virtualization (RHEV) version 2.2, we strongly recommend that you migrate to version 3.0, as RHEV 2.2 is nearing end of life for support. If your goal is to upgrade to RHEV 3.1 and you are currently running RHEV 2.2, you must first upgrade to RHEV 3.0 (as described in this guide) before upgrading to RHEV 3.1.
Accordingly, this document describes how to migrate a Red Hat Enterprise Virtualization Manager (RHEV-M) version 2.2 (on a Microsoft Windows system) to version 3.0 (on a Red Hat Enterprise Linux 6.x system).
NOTES:
The latest RHEV 2.2.x is required prior to upgrading to RHEV 3.0. (At least RHEV 2.2.5 is needed to properly migrate your Windows virtual machines.)
This process does not upgrade the hypervisors, nor the storage domain metadata, to the latest version.
Upgrading only the RHEV-M to version 3.0 will mean the hypervisors (RHEL 5.x) and storage domains (V1) are running in Compatibility Mode.
Information added to the October 16, 2012 update of this guide describes issues related to migrating other components of your RHEV environment (hosts, storage, and Windows VMs).