Procedure 3.17. Preparing the Remote PostgreSQL Database for use with the Red Hat Enterprise Virtualization Manager

1. Log in to the remote database server and install the PostgreSQL server package:

   # yum install postgresql-server

2. Initialize the PostgreSQL database, start the postgresql service, and ensure that this service starts on boot:

   # service postgresql initdb
   # service postgresql start
   # chkconfig postgresql on

3. Connect to the psql command line interface as the postgres user:

   # su - postgres
   $ psql

4. Create a user for the Manager to use when it writes to and reads from the database. The default user name for the ovirt_engine_history database is ovirt_engine_history:

   postgres=# create role user_name with login encrypted password 'password';

   Note

   The password for the ovirt_engine_history user is located in plain text in /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-database.conf. Any password can be used when creating the role on the new server, however if a different password is used then this file, and the /etc/ovirt-engine-reports/ovirt-engine-reports.conf.d/10-setup-database.conf file, must be updated with the new password.
5. Create a database in which to store the history of the Red Hat Enterprise Virtualization environment. The default database name is ovirt_engine_history, and the default user name is ovirt_engine_history:

   postgres=# create database database_name owner user_name template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8';
   

6. Ensure the database can be accessed remotely by enabling md5 client authentication. Edit the /var/lib/pgsql/data/pg_hba.conf file, and add the following line immediately underneath the line starting with local at the bottom of the file, replacing X.X.X.X with the IP address of the Manager:

   host    database_name    user_name    X.X.X.X/32   md5

7. Allow TCP/IP connections to the database. Edit the /var/lib/pgsql/data/postgresql.conf file and add the following line:

   listen_addresses='*'

   This example configures the postgresql service to listen for connections on all interfaces. You can specify an interface by giving its IP address.
8. Open the default port used for PostgreSQL database connections, and save the updated firewall rules:

   # iptables -I INPUT 5 -p tcp --dport 5432 -j ACCEPT
   # service iptables save

9. Restart the postgresql service:

   # service postgresql restart

Procedure 3.18. Migrating the Database

1. Log in to one of the hosted-engine hosts and place the environment into global maintenance mode so that the High Availability agents do not interfere with the Manager virtual machine during the database migration:

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

2. Log in to the Red Hat Enterprise Virtualization Manager machine and stop the ovirt-engine-dwhd service so that it does not interfere with the engine backup:

   # service ovirt-engine-dwhd stop

3. Create the ovirt_engine_history database backup using the PostgreSQL pg_dump command:

   # su - postgres -c 'pg_dump -F c ovirt_engine_history -f /tmp/ovirt_engine_history.dump'

4. Copy the backup file to the new database server. The target directory must allow write access for the postgres user:

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

5. Log in to the new database server and restore the database using the PostgreSQL pg_restore command:

   # su - postgres -c 'pg_restore -d ovirt_engine_history /tmp/ovirt_engine_history.dump'

6. Log in to the Manager server and update the /etc/ovirt-engine-reports/ovirt-engine-reports.conf.d/10-setup-database.conf and /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-database.conf files, replacing the localhost value of DWH_DB_HOST with the IP address of the new database server. If the DWH_DB_DATABASE, DWH_DB_USER, or DWH_DB_PASSWORD differ on the new database server, update those values in these files.
   If the Manager database has also been migrated, these values must also be updated in the /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-database.conf file.
7. Use a web browser to log in to the Reports portal at

   https://hostname.example.com/ovirt-engine-reports

   using the superuser user name. Click View → Repository to open the Folders side pane.
8. In the Folders side pane, select RHEVM Reports → Resources → JDBC → Data Sources.
9. Select oVirt History and click Edit.
10. Update the Host (required) field with the IP address of the new database server and click Save.
11. Now that the database has been migrated and the Reports portal connects to it, start the ovirt-engine-dwhd service:

    # service ovirt-engine-dwhd start

12. Log in to a hosted-engine host and turn off maintenance mode, enabling the High Availability agents:

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