Description of problem: Upgrade from 3.2 does: 1. create a database user 'engine_history' 2. Update ownership of all objects to this user 3. backup 4. update the schema to 3.3 This means that if we fail during 1 or 2, we have no backup, and if we fail during 4 we restore from a backup that is different from what we started with. We should backup as soon as possible, then start doing other things.
ok is32.2. backup before `rhevm-dwh-setup' and one created by upgrade itself is equal. # /bin/su -l postgres -c "PGPASSWORD=123456 /usr/bin/pg_dump -C -E UTF8 -w --disable-dollar-quoting --disable-triggers --format=p -Fc ovirt_engine_history" > ovirt_engine_history # rhevm-dwh-setup ...snip... # ls -l /root/ovirt_engine_history /var/lib/ovirt-engine/backups/ovirt-engine-history.backup.2014_01_16_12_25_56 -rw-r--r--. 1 root root 750422 Jan 16 12:24 /root/ovirt_engine_history -rw-r--r--. 1 root root 750422 Jan 16 12:25 /var/lib/ovirt-engine/backups/ovirt-engine-history.backup.2014_01_16_12_25_56
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0036.html