Chapter 8. Migrating the Self-Hosted Engine Database to a Remote Server Database

Procedure 8.1. Migrating the Database

1. Log in to a self-hosted engine node and place the environment into global maintenance mode. This disables the High Availability agents and prevents the Manager virtual machine from being migrated during the procedure:

   # hosted-engine --set-maintenance --mode=global

   Copy to Clipboard Toggle word wrap
2. Log in to the Red Hat Virtualization Manager machine and stop the ovirt-engine service so that it does not interfere with the engine backup:

   # systemctl stop ovirt-engine.service

   Copy to Clipboard Toggle word wrap
3. Create the engine database backup:

   # engine-backup --scope=files --scope=db --mode=backup --file=file_name --log=backup_log_name

   Copy to Clipboard Toggle word wrap
4. Copy the backup file to the new database server:

   # scp /tmp/engine.dump root@new.database.server.com:/tmp

   Copy to Clipboard Toggle word wrap
5. Log in to the new database server and install engine-backup:

   # yum install ovirt-engine-tools-backup

   Copy to Clipboard Toggle word wrap
6. Restore the database on the new database server. file_name is the backup file copied from the Manager.

   # engine-backup --mode=restore --scope=files --scope=db --file=file_name --log=restore_log_name --provision-db --no-restore-permissions

   Copy to Clipboard Toggle word wrap
7. Now that the database has been migrated, start the ovirt-engine service:

   # systemctl start ovirt-engine.service

   Copy to Clipboard Toggle word wrap
8. Log in to a self-hosted engine node and turn off maintenance mode, enabling the High Availability agents:

   # hosted-engine --set-maintenance --mode=none

   Copy to Clipboard Toggle word wrap