Red Hat SummitEste contenido no está disponible en el idioma seleccionado.
Chapter 8. Migrating the Self-Hosted Engine Database to a Remote Server Database
You can migrate the
engine database of a self-hosted engine to a remote database server after the Red Hat Virtualization Manager has been initially configured. Use engine-backup to create a database backup and restore it on the new database server. This procedure assumes that the new database server has Red Hat Enterprise Linux 7 installed and the appropriate subscriptions configured. See Subscribing to the Required Entitlements in the Installation Guide.
To migrate Data Warehouse to a separate machine, see Migrating Data Warehouse to a Separate Machine in the Data Warehouse Guide.
Procedure 8.1. Migrating the Database
- Log in to a self-hosted engine node and place the environment into
globalmaintenance 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
- Log in to the Red Hat Virtualization Manager machine and stop the
ovirt-engineservice so that it does not interfere with the engine backup:# systemctl stop ovirt-engine.service
- Create the
enginedatabase backup:# engine-backup --scope=files --scope=db --mode=backup --file=file_name --log=backup_log_name
- Copy the backup file to the new database server:
# scp /tmp/engine.dump root@new.database.server.com:/tmp
- Log in to the new database server and install
engine-backup:# yum install ovirt-engine-tools-backup
- 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
- Now that the database has been migrated, start the
ovirt-engineservice:# systemctl start ovirt-engine.service
- Log in to a self-hosted engine node and turn off maintenance mode, enabling the High Availability agents:
# hosted-engine --set-maintenance --mode=none
