Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

5.4. Migrating Data Warehouse and Reports to Separate Machines

Migrate the Data Warehouse service, the Reports service, or both from the Red Hat Enterprise Virtualization Manager to separate machines. Hosting the Data Warehouse service and the Reports service on separate machines reduces the load on each individual machine, and allows each service to avoid potential conflicts caused by sharing CPU and memory with other processes.
Migrate the Data Warehouse service and connect it with the existing ovirt_engine_history database, or optionally migrate the ovirt_engine_history database to a new database machine before migrating the Data Warehouse service. If the ovirt_engine_history database is hosted on the Manager, migrating the database in addition to the Data Warehouse service further reduces the competition for resources on the Manager machine. You can migrate the database to the same machine onto which you will migrate the Data Warehouse service, or to a machine that is separate from both the Manager machine and the new Data Warehouse service machine.

5.4.1. Migrating the Data Warehouse Database to a Separate Machine

Optionally migrate the ovirt_engine_history database before you migrate the Data Warehouse service. This procedure uses pg_dump to create a database backup, and psql to restore the backup on the new database machine. The pg_dump command provides flexible options for backing up and restoring databases; for more information on options that may be suitable for your system, see the pg_dump manual page.
The following procedure assumes that a PostgreSQL database has already been configured on the new machine. To migrate the Data Warehouse service only, see Section 5.4.2, “Migrating the Data Warehouse Service to a Separate Machine”.

Important

If the existing Data Warehouse database is connected to an existing Reports service, you must reconfigure that service by running engine-setup and entering the details of the new Data Warehouse database when prompted. If you do not do this, the Reports service is still connected to the old database, and does not receive any new data.

Procedure 5.9. Migrating the Data Warehouse Database to a Separate Machine

  1. On the existing database machine, dump the ovirt_engine_history database into a SQL script file:
    Copy to Clipboard Toggle word wrap 
    # pg_dump ovirt_engine_history > ovirt_engine_history.sql
  2. Copy the script file from the existing database machine to the new database machine.
  3. Restore the ovirt_engine_history database on the new database machine:
    Copy to Clipboard Toggle word wrap 
    # psql -d ovirt_engine_history -f ovirt_engine_history.sql
    The command above assumes that the database on the new machine is also named ovirt_engine_history.

5.4.2. Migrating the Data Warehouse Service to a Separate Machine

Migrate a Data Warehouse service that was installed and configured on the Red Hat Enterprise Virtualization Manager to a dedicated host machine. Hosting the Data Warehouse service on a separate machine helps to reduce the load on the Manager machine. Note that this procedure migrates the Data Warehouse service only; to migrate the Data Warehouse database (also known as the ovirt_engine_history database) prior to migrating the Data Warehouse service, see Section 5.4.1, “Migrating the Data Warehouse Database to a Separate Machine”.
Installing this scenario involves four key steps:
  1. Set up the new Data Warehouse machine.
  2. Stop the Data Warehouse service on the Manager machine.
  3. Configure the new Data Warehouse machine.
  4. Remove the Data Warehouse package from the Manager machine.
Prerequisites

Ensure that you have completed the following prerequisites:

  1. You must have installed and configured the Manager and Data Warehouse on the same machine.
  2. To set up the new Data Warehouse machine, you must have the following:
    • A virtual or physical machine with Red Hat Enterprise Linux 6.6 or later versions of Red Hat Enterprise Linux 6 installed.
    • A subscription to the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization entitlement pools.
    • The password from the Manager's /etc/ovirt-engine/engine.conf.d/10-setup-database.conf file.
    • Allowed access from the Data Warehouse machine to the Manager database machine's TCP port 5432.
    • The ovirt_engine_history database credentials from the Manager's /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-database.conf file. If you migrated the ovirt_engine_history database using Section 5.4.1, “Migrating the Data Warehouse Database to a Separate Machine”, retrieve the credentials you defined during the database setup on that machine.

Procedure 5.10. Step 1: Setting up the New Data Warehouse Machine

  1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:
    Copy to Clipboard Toggle word wrap 
    # subscription-manager register
  2. Find the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization subscription pools and note down the pool IDs.
    Copy to Clipboard Toggle word wrap 
    # subscription-manager list --available
  3. Use the pool IDs located in the previous step to attach the entitlements to the system:
    Copy to Clipboard Toggle word wrap 
    # subscription-manager attach --pool=pool_id
  4. Disable all existing repositories:
    Copy to Clipboard Toggle word wrap 
    # subscription-manager repos --disable=*
  5. Enable the required channels:
    Copy to Clipboard Toggle word wrap 
    # subscription-manager repos --enable=rhel-6-server-rpms
# subscription-manager repos --enable=rhel-6-server-supplementary-rpms
# subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
# subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms
  6. Ensure that all packages currently installed are up to date:
    Copy to Clipboard Toggle word wrap 
    # yum update
  7. Install the rhevm-dwh-setup package:
    Copy to Clipboard Toggle word wrap 
    # yum install rhevm-dwh-setup

Procedure 5.11. Step 2: Stopping the Data Warehouse Service on the Manager Machine

  1. Stop the Data Warehouse service:
    Copy to Clipboard Toggle word wrap 
    # service ovirt-engine-dwhd stop
  2. If the ovirt_engine_history database, the Manager database, or both are hosted on the Manager machine and were configured by a previous version (Red Hat Enterprise Virtualization 3.4 or prior) that was then upgraded, you must allow the new Data Warehouse machine to access them. Edit the /var/lib/pgsql/data/postgresql.conf file and modify the listen_addresses line so that it matches the following:
    Copy to Clipboard Toggle word wrap 
    listen_addresses = '*'
    If the line does not exist or has been commented out, add it manually.
    If one or both databases are hosted on a remote machine, you must manually grant access by editing the postgres.conf file on each machine, and adding the listen_addresses line, as above. If both databases are hosted on the Manager machine and were configured during a clean setup of Red Hat Enterprise Virtualization Manager 3.5, access is granted by default.
  3. Restart the postgresql service:
    Copy to Clipboard Toggle word wrap 
    # service postgresql restart

Procedure 5.12. Step 3: Configuring the New Data Warehouse Machine

  1. Run the engine-setup command to begin configuration of Data Warehouse on the machine:
    Copy to Clipboard Toggle word wrap 
    # engine-setup
  2. Press Enter to configure Data Warehouse:
    Copy to Clipboard Toggle word wrap 
    Configure Data Warehouse on this host (Yes, No) [Yes]:
  3. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:
    Copy to Clipboard Toggle word wrap 
    Setup can automatically configure the firewall on this system.
Note: automatic configuration of the firewall may overwrite current settings.
Do you want Setup to configure the firewall? (Yes, No) [Yes]:
    If you choose to automatically configure the firewall, and no firewall managers are active, you are prompted to select your chosen firewall manager from a list of supported options. Type the name of the firewall manager and press Enter. This applies even in cases where only one option is listed.
  4. Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:
    Copy to Clipboard Toggle word wrap 
    Host fully qualified DNS name of this server [autodetected host name]:
  5. Answer the following question about the location of the ovirt_engine_history database:
    Copy to Clipboard Toggle word wrap 
    Where is the DWH database located? (Local, Remote) [Local]: Remote
    Type the alternative option as shown above and then press Enter.
  6. Enter the fully qualified domain name and password for your ovirt_engine_history database host. Press Enter to accept the default values in each other field:
    Copy to Clipboard Toggle word wrap 
    DWH database host []: dwh-db-fqdn
DWH database port [5432]: 
DWH database secured connection (Yes, No) [No]: 
DWH database name [ovirt_engine_history]: 
DWH database user [ovirt_engine_history]: 
DWH database password: password
  7. Enter the fully qualified domain name and password for the Manager database machine. Press Enter to accept the default values in each other field:
    Copy to Clipboard Toggle word wrap 
    Engine database host []: engine-db-fqdn
Engine database port [5432]: 
Engine database secured connection (Yes, No) [No]: 
Engine database name [engine]: 
Engine database user [engine]: 
Engine database password: password
  8. Press Enter to create a backup of the existing Data Warehouse database:
    Copy to Clipboard Toggle word wrap 
    Would you like to backup the existing database before upgrading it? (Yes, No) [Yes]:
    The time and space required for the database backup depends on the size of the database. It may take several hours to complete. If you choose not to back up the database here, and engine-setup fails for any reason, you will not be able to restore the database or any of the data within it. The location of the backup file appears at the end of the setup script.
  9. Confirm that you want to permanently disconnect the existing Data Warehouse service from the Manager:
    Copy to Clipboard Toggle word wrap 
    Do you want to permanently disconnect this DWH from the engine? (Yes, No) [No]:
  10. Confirm your installation settings: Copy to Clipboard Toggle word wrap 
    Please confirm installation settings (OK, Cancel) [OK]:

Procedure 5.13. Step 4: Removing the Data Warehouse Package from the Manager Machine

  1. Remove the Data Warehouse package:
    Copy to Clipboard Toggle word wrap 
    # yum remove rhevm-dwh
    This step prevents the Data Warehouse service from attempting to automatically restart after an hour.
  2. Remove the Data Warehouse files:
    Copy to Clipboard Toggle word wrap 
    # rm -rf /etc/ovirt-engine-dwh /var/lib/ovirt-engine-dwh
The Data Warehouse service is now hosted on a separate machine from that on which the Manager is hosted.

5.4.3. Migrating the Reports Service to a Separate Machine

Migrate a Reports service that was installed and configured on the Red Hat Enterprise Virtualization Manager to a dedicated host machine. Hosting the Reports service on a separate machine helps to reduce the load on the Manager machine. Note that this procedure migrates the Reports service only. The Reports database (also known as the ovirt_engine_reports database) cannot be migrated; you must create a new ovirt_engine_reports database when you configure Reports on the new machine. Saved ad hoc reports can be migrated from the Manager machine to the new Reports machine. Migrate the Reports service only after the Manager and Data Warehouse have been configured.
Installing this scenario involves three key steps:
  1. Configure the new Reports machine.
  2. Migrate any saved reports to the new Reports machine.
  3. Remove the Reports service from the Manager machine.
Prerequisites

Ensure that you have completed the following prerequisites:

  1. You must have installed and configured the Manager and Reports on the same machine.
  2. You must have installed and configured Data Warehouse, either on the Manager machine or on a separate machine.
  3. To set up the new Reports machine, you must have the following:
    • A virtual or physical machine with Red Hat Enterprise Linux 6.6 or later versions of Red Hat Enterprise Linux 6 installed
    • A subscription to the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization entitlement pools
    • The password from the Data Warehouse machine's /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-database.conf file
    • Allowed access from the Reports machine to the Manager database machine's TCP port 5432

Procedure 5.14. Step 1: Configuring the New Reports Machine

  1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:
    Copy to Clipboard Toggle word wrap 
    # subscription-manager register
  2. Find the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization subscription pools and note down the pool IDs.
    Copy to Clipboard Toggle word wrap 
    # subscription-manager list --available
  3. Use the pool IDs located in the previous step to attach the entitlements to the system:
    Copy to Clipboard Toggle word wrap 
    # subscription-manager attach --pool=pool_id
  4. Disable all existing repositories:
    Copy to Clipboard Toggle word wrap 
    # subscription-manager repos --disable=*
  5. Enable the required channels:
    Copy to Clipboard Toggle word wrap 
    # subscription-manager repos --enable=rhel-6-server-rpms
# subscription-manager repos --enable=rhel-6-server-supplementary-rpms
# subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
# subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms
  6. Ensure that all packages currently installed are up to date:
    Copy to Clipboard Toggle word wrap 
    # yum update
  7. Install the rhevm-reports-setup package:
    Copy to Clipboard Toggle word wrap 
    # yum install rhevm-reports-setup
  8. Run the engine-setup command to begin configuration of Reports on the machine:
    Copy to Clipboard Toggle word wrap 
    # engine-setup
  9. Press Enter to configure Reports:
    Copy to Clipboard Toggle word wrap 
    Configure Reports on this host (Yes, No) [Yes]:
  10. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:
    Copy to Clipboard Toggle word wrap 
    Setup can automatically configure the firewall on this system.
Note: automatic configuration of the firewall may overwrite current settings.
Do you want Setup to configure the firewall? (Yes, No) [Yes]:
    If you choose to automatically configure the firewall, and no firewall managers are active, you are prompted to select your chosen firewall manager from a list of supported options. Type the name of the firewall manager and press Enter. This applies even in cases where only one option is listed.
  11. Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:
    Copy to Clipboard Toggle word wrap 
    Host fully qualified DNS name of this server [autodetected host name]:
  12. Enter the fully qualified domain name of the Manager machine, and then press Enter:
    Copy to Clipboard Toggle word wrap 
    Host fully qualified DNS name of the engine server []:
  13. Answer the following questions about the ovirt_engine_reports database. Press Enter to allow setup to create and configure a local database:
    Copy to Clipboard Toggle word wrap 
    Where is the Reports database located? (Local, Remote) [Local]:
Setup can configure the local postgresql server automatically for the Reports to run. This may conflict with existing applications.
Would you like Setup to automatically configure postgresql and create Reports database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
  14. Enter the fully qualified domain name and password for your ovirt_engine_history database host. Press Enter to accept the default values in each other field:
    Copy to Clipboard Toggle word wrap 
    DWH database host []: dwh-db-fqdn
DWH database port [5432]: 
DWH database secured connection (Yes, No) [No]: 
DWH database name [ovirt_engine_history]: 
DWH database user [ovirt_engine_history]: 
DWH database password: password
  15. Press Enter to allow setup to sign the Reports certificate and Apache certificate on the Manager via SSH:
    Copy to Clipboard Toggle word wrap 
    Setup will need to do some actions on the remote engine server. Either automatically, using ssh as root to access it, or you will be prompted to manually perform each such action.
Please choose one of the following:
1 - Access remote engine server using ssh as root
2 - Perform each action manually, use files to copy content around
(1, 2) [1]:
  16. Press Enter to accept the default SSH port, or enter an alternative port number and then press Enter:
    Copy to Clipboard Toggle word wrap 
    ssh port on remote engine server [22]:
  17. Enter the root password for the Manager machine:
    Copy to Clipboard Toggle word wrap 
    root password on remote engine server manager-fqdn.com:
  18. Press Enter to allow automatic configuration of SSL on Apache:
    Copy to Clipboard Toggle word wrap 
    Setup can configure apache to use SSL using a certificate issued from the internal CA.
Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
  19. Set a password for the Reports administrative users (admin and superuser). Note that the reports system maintains its own set of credentials that are separate to those used for the Manager:
    Copy to Clipboard Toggle word wrap 
    Reports power users password:
    You are prompted to enter the password a second time to confirm it.
  20. Confirm your installation settings:
    Copy to Clipboard Toggle word wrap 
    Please confirm installation settings (OK, Cancel) [OK]:

Procedure 5.15. Step 2: Migrating Saved Reports to the New Reports Machine

  1. On the Manager machine, run the ovirt-engine-reports-tool command:
    Copy to Clipboard Toggle word wrap 
    # ovirt-engine-reports-tool
  2. Enter the number that corresponds to the export option, and press Enter:
    Copy to Clipboard Toggle word wrap 
    (2) Export Jasperreports saved reports to a zip file
(1, 2, 3) []: 2
  3. Enter the absolute path for the zip file to export saved reports to, and press Enter:
    Copy to Clipboard Toggle word wrap 
    Filename to export saved reports to: /tmp/saved-reports.zip
  4. Copy the zip file to the new Reports machine:
    Copy to Clipboard Toggle word wrap 
    # scp /tmp/saved-reports.zip reports-machine-fqdn:/tmp/
  5. On the new Reports machine, run the ovirt-engine-reports-tool command:
    Copy to Clipboard Toggle word wrap 
    # ovirt-engine-reports-tool
  6. Enter the number that corresponds to the import option, and press Enter:
    Copy to Clipboard Toggle word wrap 
    (3) Import a saved reports zip file to Jasperreports
(1, 2, 3) []: 3
  7. Enter the absolute path of the zip file from which to import, and press Enter:
    Copy to Clipboard Toggle word wrap 
    Filename to import saved reports from: /tmp/saved-reports.zip
When the command completes, the saved reports are visible in the Reports Portal of the new Reports machine.

Procedure 5.16. Step 3: Removing the Reports Service from the Manager Machine

  1. Stop the Reports service:
    Copy to Clipboard Toggle word wrap 
    # service ovirt-engine-reportsd stop
  2. Remove the Reports package:
    Copy to Clipboard Toggle word wrap 
    # yum remove rhevm-reports
  3. Remove the Reports files:
    Copy to Clipboard Toggle word wrap 
    # rm -rf /etc/ovirt-engine-reports /var/lib/ovirt-engine-reports
  4. Remove the Reports database and user. The default name for both is ovirt_engine_reports:
    Copy to Clipboard Toggle word wrap 
    # su - postgres
$ psql
postgres=# drop database ovirt_engine_reports;
postgres=# drop user ovirt_engine_reports;

Note

You can configure more than one working Reports instance, and continue to log in and view reports from an older instance; however, the Manager will directly connect to and have SSO with only the last Reports instance that was configured using engine-setup. This means that the Administration Portal includes dashboards from and direct links to only the most recent Reports installation.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat, Inc.