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" <jplor...@gmail.com> >> To: "Yedidyah Bar David" <d...@redhat.com> >> Cc: "Sahina Bose" <sab...@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=backup > (perhaps do other stuff here) > 3. engine-cleanup > 4. engine-backup --mode=restore > > 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 could > 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,
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users