Chapter 1. Migration Overview

When you specify a backup file during self-hosted engine deployment, the Manager backup is restored on a new virtual machine, with a dedicated self-hosted engine storage domain. Deploying on a fresh host is highly recommended; if the host used for deployment existed in the backed up environment, it will be removed from the restored database to avoid conflicts in the new environment. If you deploy on a new host, you must assign a unique name to the host. Reusing the name of an existing host included in the backup can cause conflicts in the new environment.

At least two self-hosted engine nodes are required for the Manager virtual machine to be highly available. You can add new nodes, or convert existing hosts.

The migration involves the following key steps:

  1. Install a new host to deploy the self-hosted engine on. You can use either host type:

  2. Prepare storage for the self-hosted engine storage domain. You can use one of the following storage types:

  3. Update the original Manager to the latest minor version before you back it up.
  4. Back up the original Manager using the engine-backup tool.
  5. Deploy a new self-hosted engine and restore the backup.
  6. Enable the Manager repositories on the new Manager virtual machine.
  7. Convert regular hosts to self-hosted engine nodes that can host the new Manager.

This procedure assumes that you have access and can make changes to the original Manager.

Prerequisites

  • FQDNs prepared for your Manager and the deployment host. Forward and reverse lookup records must both be set in the DNS. The new Manager must have the same FQDN as the original Manager.
  • The management network (ovirtmgmt by default) must be configured as a VM network, so that it can manage the Manager virtual machine.