9.4. Migrating the Data Warehouse Service to a Separate Machine
ovirt_engine_history database) prior to migrating the Data Warehouse service, see Section 9.3, “Migrating the Data Warehouse Database to a Separate Machine”.
- Set up the new Data Warehouse machine.
- Stop the Data Warehouse service on the Manager machine.
- Configure the new Data Warehouse machine.
- Remove the Data Warehouse package from the Manager machine.
Ensure that you have completed the following prerequisites:
- You must have installed and configured the Manager and Data Warehouse on the same machine.
- 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 ServerandRed Hat Enterprise Virtualizationentitlement pools. - The password from the Manager's
/etc/ovirt-engine/engine.conf.d/10-setup-database.conffile. - Allowed access from the Data Warehouse machine to the Manager database machine's TCP port 5432.
- The
ovirt_engine_historydatabase credentials from the Manager's/etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-database.conffile. If you migrated theovirt_engine_historydatabase using Section 9.3, “Migrating the Data Warehouse Database to a Separate Machine”, retrieve the credentials you defined during the database setup on that machine.
Procedure 9.4. Step 1: Setting up the New Data Warehouse Machine
- Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:
# subscription-manager register
- Find the
Red Hat Enterprise Linux ServerandRed Hat Enterprise Virtualizationsubscription pools and note down the pool IDs.# subscription-manager list --available
- Use the pool IDs located in the previous step to attach the entitlements to the system:
# subscription-manager attach --pool=pool_id
- Disable all existing repositories:
# subscription-manager repos --disable=*
- Enable the required channels:
# 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
- Ensure that all packages currently installed are up to date:
# yum update
- Install the rhevm-dwh-setup package:
# yum install rhevm-dwh-setup
Procedure 9.5. Step 2: Stopping the Data Warehouse Service on the Manager Machine
- Stop the Data Warehouse service:
# service ovirt-engine-dwhd stop
- If the
ovirt_engine_historydatabase, 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.conffile and modify thelisten_addressesline so that it matches the following: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 thepostgres.conffile on each machine, and adding thelisten_addressesline, 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. - Restart the postgresql service:
# service postgresql restart
Procedure 9.6. Step 3: Configuring the New Data Warehouse Machine
- Run the
engine-setupcommand to begin configuration of Data Warehouse on the machine:# engine-setup
- Press Enter to configure Data Warehouse:
Configure Data Warehouse on this host (Yes, No) [Yes]:
- Press Enter to automatically configure the firewall, or type
Noand press Enter to maintain existing settings: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. - Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:
Host fully qualified DNS name of this server [autodetected host name]:
- Answer the following question about the location of the
ovirt_engine_historydatabase:Where is the DWH database located? (Local, Remote) [Local]: Remote
Type the alternative option as shown above and then press Enter. - Enter the fully qualified domain name and password for your
ovirt_engine_historydatabase host. Press Enter to accept the default values in each other field: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
- Enter the fully qualified domain name and password for the Manager database machine. Press Enter to accept the default values in each other field:
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
- Press Enter to create a backup of the existing Data Warehouse database:
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, andengine-setupfails 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. - Confirm that you want to permanently disconnect the existing Data Warehouse service from the Manager:
Do you want to permanently disconnect this DWH from the engine? (Yes, No) [No]:
- Confirm your installation settings:
Please confirm installation settings (OK, Cancel) [OK]:
Procedure 9.7. Step 4: Removing the Data Warehouse Package from the Manager Machine
- Remove the Data Warehouse package:
# yum remove rhevm-dwh
This step prevents the Data Warehouse service from attempting to automatically restart after an hour. - Remove the Data Warehouse files:
# rm -rf /etc/ovirt-engine-dwh /var/lib/ovirt-engine-dwh

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.