----- Original Message -----
From: "Neil" <nwilson123@gmail.com> To: users@ovirt.org Sent: Monday, September 15, 2014 6:26:18 PM Subject: [ovirt-users] Move ovirt-engine to a new server
Hi guys,
Please could someone try assist me. I'm starting to lose hair over this :)
I'm trying to migrate my current engine to a new host with the same OS and hostname. Centos 6.5, ovirt-engine-3.4.3-1.el6.noarch
I've installed all the packages, I run engine-setup and go through the options keeping the details the same as before, I then restore my config back to /etc/ovirt-engine as well as to /etc/pki/ovirt-engine, but when it gets to trying to restore my database I get the following error...
[root@backup dbscripts]# ./restore.sh -u postgres -f /mnt/fw-ovirt-backup/engine-db-2014-09-15-16-48.sql psql: FATAL: Ident authentication failed for user "postgres" Database engine does not exist, please create an empty database named engine.
[root@backup dbscripts]# su - postgres -c "psql -d template1 -c 'drop database engine;'" DROP DATABASE [root@backup dbscripts]# su - postgres -c "psql -d template1 -c 'create database engine owner engine;'" CREATE DATABASE
[root@backup dbscripts]# ./restore.sh -u postgres -f /mnt/fw-ovirt-backup/engine-db-2014-09-15-16-48.sql psql: FATAL: Ident authentication failed for user "postgres" Database engine does not exist, please create an empty database named engine.
or even
[root@backup dbscripts]# ./restore.sh -u engine -f /mnt/fw-ovirt-backup/engine-db-2014-09-15-16-48.sql psql: FATAL: Ident authentication failed for user "engine" Database engine does not exist, please create an empty database named engine.
This is my pg_hba.conf as well..
# TYPE DATABASE USER CIDR-ADDRESS METHOD
# "local" is for Unix domain socket connections only local all all ident host engine engine 0.0.0.0/0 md5 host engine engine ::0/0 md5 # IPv4 local connections: host all all 127.0.0.1/32 ident # IPv6 local connections: host all all ::1/128 ident
I've done this a couple time before and haven't encountered this issue, so it seems rather odd.
What guide are you following? You should be able to do this with engine-backup, see [1]. That said, your problems above seem to be caused by some postgres-specific issues, which might not be solved by simply using engine-backup. I suggest that you try and report if you still have problems. Good luck! [1] http://www.ovirt.org/Ovirt-engine-backup -- Didi