Re: [Users] engine-backup --restore

----- Original Message ----- > From: "Juan Pablo Lorier" <jplorier(a)gmail.com&gt; > To: "Yedidyah Bar David" <didi(a)redhat.com&gt; > Cc: "Sahina Bose" <sabose(a)redhat.com&gt;, "users" <users(a)ovirt.org&gt; > 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=

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,

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS+8czAAoJEC5KDDg2+NMMTD4H/AuPXcDPxDfh9lka535o7d+Q ncI7YkPYU+mdn5UylRZ0rJwNa8ixKhByy69HcDsE1AxMUwHTTmUrxNOsAwtcE0Gk 6l2lu57F9ZD1etnB1ni6GPLLmexV7GAvBCeut2AXfCudDEqRh37qfR2cBZQgX1uN XtA+bQA47+s9w4Ej3Wj8K88FTbFtaMi5fa16ZsUhuEC9IFOaHT0bCL7YQWLMStHP VnPhuTaxjQXSo4ZaqyILalzEChv5y8qm8eDm8huue+4MYz9OLSWhkRAe9kbYaYcz UGBk/kKVwG5SrvPWkZNCPC/g6LaliYBRqPvQGiAu8LW4w6QAIfFItyxZoKWQfeI= =9qzR -----END PGP SIGNATURE-----