Bug 1217297

The backup tool has been updated for 3.5 and 3.4 but this procedure should be checked against 3.3

+++ This bug was initially created as a clone of Bug #1092388 +++

Didi just brought this to my attention. It's too late for 3.4 as docs freeze has passed. 

Wiki has the info:
http://www.ovirt.org/Ovirt-engine-backup

--- Additional comment from Julie on 2014-09-16 01:26:08 EDT ---

Hi Tomas,
  You mentioned the support team gets ticket daily for this bug, I checked with Andrew Dahms who documented most of the engine restore and backup content which can be found here [1] and he's really interested to know what is missing from the documentation. What are the customers running into and what are they trying to solve? If you could help us find some of answers and perhaps attach a few support cases, that would really help us to understand what else needs to be added in for the engine restore and backup section.


[1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html-single/Administration_Guide/index.html#Backing_up_Red_Hat_Enterprise_Virtualization_Manager_using_the_engine-backup_Command

--- Additional comment from Tomas Dosek on 2014-09-16 01:45:53 EDT ---

Hi Julie,

The missing steps are for reports/dwhd databases. While engine-backup provides with full backup of engine database, it does not create dumps of reports/dwhd database if these are installed.

There's already pending request for improvement in engine-backup, but until that is solved we need to back these up manually (using pg_dump) so it would be nice if documentation mentioned it.

So far we use articles like:
https://access.redhat.com/solutions/225823
https://access.redhat.com/solutions/759413

--- Additional comment from Julie on 2014-09-23 04:43:08 EDT ---