How are RHEV upgrades/migrations performed and supported?

Updated -

ISSUE

  • Are Microsoft Windows Server 2003 to 2008 migrations supported, while staying on RHEV 2.2?
  • Are RHEV 2.1 to RHEV 2.2 upgrades supported?
  • Are RHEV 3.0 Beta to RHEV 3.0 GA upgrades supported?
  • Are RHEV 2.2 to RHEV 3.0 upgrades supported?
    • How do I upgrade RHEV-M only?
    • How do I upgrade the hypervisors?
    • How do I upgrade the storage data center metadata from Version 1 to Version 2?

ENVIRONMENT

  • Red Hat Enterprise Virtualization 2.1, 2.2, 3.0

RESOLUTION

  • Microsoft Windows Server 2003 to Microsoft Windows Server 2008 Migration (Staying on RHEV 2.2)

Migration of the Windows server on RHEV-M requires a community-supported upstream tool called rhevUP. The tool can be found at the following upstream project space: https://github.com/dougsland/rhevUP/wiki This action is unsupported by Red Hat.

UPGRADING TO:
2.1 2.2
 3.0
 3.1
2.1 YES NO NO
2.2 YES NO
3.0 YES
  • RHEV 2.1 to RHEV 2.2 Upgrades

An upgrade from RHEV 2.1 to RHEV 2.2 is trivial, assuming the RHEV-M server continues to use Microsoft Windows Server 2003. This action is supported by Red Hat while RHEV 2.2 is not at end-of-life. Please refer to the RHEV life cycle page for more information.

  • RHEV 2.2 to RHEV 2.2.x Upgrades
    Please refer to the following article: https://access.redhat.com/kb/docs/DOC-57194

  • RHEV 2.2 to RHEV 3.0 Upgrades

    • Upgrading RHEV Manager (RHEV-M) only

      • The following upgrade is supported by Red Hat, and the tool used is named Migration Tool. Supported use case for Migration Tool is that the customer is running either Windows Server 2003 or Windows Server 2008 R2.
        NOTE: The latest RHEV 2.2.x is required prior to upgrading to RHEV 3.0.
        NOTE: This process does not upgrade the hypervisors, nor the storage domain metadata to the latest version.
        NOTE: Upgrading only the RHEV Manager to version 3.0 will mean the hypervisors and storage domains are running in "compatibility mode."

      • Location of Final Tech Brief:  https://access.redhat.com/knowledge/techbriefs/migrating-red-hat-enterprise-virtualization-manager-version-22-30The Migration Tool contains two components: The first contains content for use on the existing RHEV 2.2 installation in Windows, and the second contains content for use on the new RHEV 3.0 installation on RHEL 6. Both components are contained in the rhevm-migration-tool package.

Once that package is installed the content is available in the following directory:

    /usr/share/rhevm-migration-tool

The Windows components are delivered inside the rhevm-migration-tool.zip file inside that directory.

/usr/share/rhevm-migration-tool/rhevm-migration-windows.zip

The main Red Hat Enterprise Linux component is the rhevm-migration.py script. It is also located in the /usr/share/rhevm-migration-tool directory and a symbolic link is provided in the /usr/bin directory to simplify usage:

/usr/bin/rhevm-migration

  • Log files of migration:

    /var/log/rhevm/migration-etl.log
/var/log/rhevm/rhevm-migration-<date>.log
/usr/share/rhevm/dbscripts/upgrade.sh.log

  • Package:

    rhevm-migration-tool

  • Upgrading the hypervisors from RHEL 5.x to RHEL 6.2 or later

  • Upgrading the storage data center metadata from Version 1 to Version 2

    • Please refer to the following Knowledgebase Article:
      https://access.redhat.com/kb/docs/DOC-69911

  • RHEV 3.0 Beta to RHEV 3.0 GA Upgrades
    This is unsupported and untested by Red Hat. A clean install should be performed.

  • RHEV 2.2 to RHEV 3.1 (future) Upgrades
    The following is supported by first upgrading RHEV 2.2 to 3.0 before 3.1.

Comments