This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --v5c3oNXSCPUgD3stLT4bbIJo68u5GsQkN Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Almost, when you mean random password, you mean for the engine user in the database? The new install and the old differ in some things in the db, so I tried to made then the same, but I saw a post of a user that removed the engine database and user and created them again before trying to restore, is that a good path? Regards, On 12/02/14 16:03, Yedidyah Bar David wrote:
----- Original Message -----
From: "Juan Pablo Lorier" <jplorier@gmail.com> To: "Yedidyah Bar David" <didi@redhat.com> Cc: "Sahina Bose" <sabose@redhat.com>, "users" <users@ovirt.org> Sent: Wednesday, February 12, 2014 7:55:35 PM Subject: Re: [Users] Problems accesing the database
Hi Yedidyah,
But If I run engine-setup and then engine-backup restore shuldn't it import the data to the existing db created by engine-setup? That's shown everywhere so I thought it's a valid way to migrate No.
There is a specific case in which this works automatically: All on the same host: 1. engine-setup 2. engine-backup --mode=3Dbackup (perhaps do other stuff here) 3. engine-cleanup 4. engine-backup --mode=3Drestore
Why does this work? Because 'engine-cleanup', since 3.3, does not drop the database nor user inside postgres. So when restore tries to access this database using this user and password it succeeds.
In general, if you do the restore on another machine, and do there 'engine-setup; engine-cleanup' as a quick-postgres-provisioning-tool, you end up almost ready, but not quite - because the password is random= , and therefore different between the installations. In principle you cou= ld have provided just the password to restore, but we decided that if you need to change the credentials, you should pass all of them (except for=
defaults).
Hope this clarifies,
--v5c3oNXSCPUgD3stLT4bbIJo68u5GsQkN Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS+7yeAAoJEC5KDDg2+NMMPEEIALsW3vjK+IBcCAWoX+EjahHu 0FQpa5Lqk2vlz74LH9gU4Q42jU12sYwi1mz9vb6zgtUj1tR+zqK56iwjIqjyOSY4 hyLbKcQCe9QJNbBT+m48lYzhZsdvJypaEIEIaHoAt4lT9rQUmMvVCCKSC6NadNbS Uy1MCU9Qg6jCcUFG4EXguOTfZaAfKkHbl/Vm58C+HidZT5W0I41AJVav0QzWG5GJ 6Fu25rxtWGMXQsqofre8bCPhp3eaHp2A06ldMJpR4lV7VV19o9+tu3c1BTC3+w9i hSWSu9XJnYMZjl1zmJIPYba1+z45ovKjAlgH/JvKBu+kJ1EwWiPY25k7UeIaHNY= =4e9Z -----END PGP SIGNATURE----- --v5c3oNXSCPUgD3stLT4bbIJo68u5GsQkN--