Chapter 5. Upgrading a Remote Database Environment from 3.6 to Red Hat Virtualization 4.2

You cannot upgrade the Manager directly from 3.6 to 4.2. You must upgrade your environment in the following sequence:

5.1. Updating the Red Hat Virtualization Manager

Updates to the Red Hat Virtualization Manager are released through the Content Delivery Network.

Procedure

On the Red Hat Virtualization Manager machine, check if updated packages are available:
```
# engine-upgrade-check
```
Update the setup packages:
```
# yum update rhevm-setup
```
Update the Red Hat Virtualization Manager. The engine-setup script prompts you with some configuration questions, then stops the ovirt-engine service, downloads and installs the updated packages, backs up and updates the database, performs post-installation configuration, and starts the ovirt-engine service.
```
# engine-setup
```
Note
The engine-setup script is also used during the Red Hat Virtualization Manager installation process, and it stores the configuration values supplied. During an update, the stored values are displayed when previewing the configuration, and may not be up to date if engine-config was used to update configuration after installation. For example, if engine-config was used to update SANWipeAfterDelete to true after installation, engine-setup will output "Default SAN wipe after delete: False" in the configuration preview. However, the updated values will not be overwritten by engine-setup.
Important
The update process may take some time; allow time for the update process to complete and do not stop the process once initiated.
Update the base operating system and any optional packages installed on the Manager:
```
# yum update
```
Important
If any kernel packages were updated, reboot the host to complete the update.