Red Hat Training

A Red Hat training course is available for Red Hat Virtualization

5.2. Upgrading the Manager from 3.6 to 4.0

In Red Hat Enterprise Virtualization 3.6, the Manager runs on Red Hat Enterprise Linux 6. An in-place upgrade of the Manager machine to Red Hat Enterprise Linux 7 is not supported. To upgrade from 3.6 to 4.0, you must install a new 4.0 Manager on Red Hat Enterprise Linux 7, and restore a backup of the 3.6 Manager database on the new Manager.

If any optional extension packages, such as ovirt-engine-extension-aaa-ldap, ovirt-engine-extension-aaa-misc, or ovirt-engine-extension-logger-log4j are installed on Red Hat Enterprise Virtualization Manager 3.6, they must be installed on the upgraded Manager before running engine-setup. The settings for these package extensions are not migrated as part of the upgrade. You can copy the configuration files to the same device or machine as the 3.6 Manager backup file.


Connected hosts and virtual machines can continue to work while the Manager is being upgraded.


  • All data centers and clusters in the environment must have the cluster compatibility level set to version 3.6 before attempting the procedure.
  • Directory servers configured using the domain management tool are not supported after Red Hat Enterprise Virtualization 3.6. If your directory servers are configured using the domain management tool, migrate to the new extension-based provider before backing up the environment. See Migrating from the Legacy Provider to the New Extension-Based Provider in the Red Hat Enterprise Virtualization 3.6 Administration Guide for more information.


  1. On the 3.6 Manager, back up the environment:

    # engine-backup --scope=all --mode=backup --file=backup.bck --log=backuplog.log
  2. Copy the backup file to a suitable device or machine.
  3. If the ISO storage domain is hosted on the Manager machine, back up the contents of /var/lib/exports/iso:

    # cd /var/lib/exports/iso
    # tar zcf iso_domain.tar.gz UUID

    You will restore the ISO storage backup file after the upgrade.

  4. Install Red Hat Enterprise Linux 7. See the Red Hat Enterprise Linux Installation Guide.

    If you are installing RHEL 7 on a new machine, you must configure it to have the same fully qualified domain name as the 3.6 Manager machine, and update your DNS so that the FQDN correlates to the IP address of the new machine.

  5. Install the Red Hat Virtualization 4.0 packages:

    1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

      # subscription-manager register
    2. Find the Red Hat Enterprise Linux Server and Red Hat Virtualization subscription pools and record the pool IDs:

      # subscription-manager list --available
    3. Use the pool IDs to attach the entitlements to the system:

      # subscription-manager attach --pool=pool_id
    4. Configure the repositories:

      # subscription-manager repos \
          --enable=rhel-7-server-rpms \
          --enable=rhel-7-server-supplementary-rpms \
          --enable=rhel-7-server-rhv-4.0-rpms \
    5. Ensure all packages are up to date:

      # yum update
    6. Install the rhevm package and dependencies:

      # yum install rhevm
  6. Copy the backup file to the 4.0 Manager machine and restore the backup:

    # engine-backup --mode=restore --file=backup.bck --log=restore.log \
        --provision-db --provision-dwh-db --restore-permissions

    If the backup contained grants for extra database users, this command will create the extra users with random passwords. You must change these passwords manually if the extra users require access to the restored system. See


    Use the --provision-dwh-db option if the backup contains Data Warehouse data.

    Red Hat Enterprise Virtualization Reports has been deprecated in Red Hat Virtualization 4.0 and will not be restored. See BZ#1340810 for more information.

  7. Install optional extension packages if they were installed on the 3.6 Manager machine:

    # yum install ovirt-engine-extension-aaa-ldap ovirt-engine-extension-aaa-misc ovirt-engine-extension-logger-log4j

    The configuration for these package extensions must be manually reapplied because they are not migrated as part of the backup and restore process.

  8. Decommission the 3.6 Manager machine if you are using a different machine for the 4.0 Manager.
  9. Run engine-setup to configure the Manager:

    # engine-setup

If you use external CA to sign HTTPS certificates, follow the steps in Replacing the Red Hat Virtualization Manager SSL Certificate in the Administration Guide to log in to the Administration Portal after the upgrade. Ensure the CA certificate is added to system-wide trust stores of all clients to ensure the foreign menu of virt-viewer works.