Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1355953

Summary:	[Docs][Admin][SHE] engine-backup no longer depends on rhevm
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Lucy Bopf <lbopf>
Component:	Documentation	Assignee:	Tahlia Richardson <trichard>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Megan Lewis <melewis>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.0.0	CC:	didi, gklein, lsurette, rbalakri, srevivo, ykaul
Target Milestone:	ovirt-4.0.4
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-12 06:31:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Docs	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1216888
Bug Blocks:

Description Lucy Bopf 2016-07-13 06:55:13 UTC

It is now possible to install and use the engine-backup tool without needing to install rhevm and all of its dependencies.

All documentation related to engine-backup should be reviewed, and updated where necessary.

In particular, the procedure for migrating Data Warehouse to a separate machine (which currently includes a procedure that uses pg_dump for backup and restore as a workaround) must be reviewed.

Comment 1 Lucy Bopf 2016-08-25 06:06:21 UTC

Assigning to Tahlia for review.

Comment 2 Tahlia Richardson 2016-08-30 04:57:14 UTC

The only reference I can find, from a quick look, to the dependency on rhevm is in the Admin Guide, but that's in the section on backing up and restoring the Manager, so that makes sense. 

For the DWH, I assume that the current procedure for migrating the DWH database should be updated to use engine-backup instead, but I am undecided on whether it should be folded into the migrating the DWH service procedure, or kept as a separate procedure (restoring using engine-backup may require the machine to be subscribed and packages installed, which is in the migrating service procedure).

Comment 3 Tahlia Richardson 2016-08-31 05:25:43 UTC

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide/#Migrating_the_Engine_Database_to_a_Remote_Server_Database might have to be updated to use engine-backup, too. 

If using engine-backup, is configuring a PostgreSQL database beforehand still a requirement? (and if so, is using engine-backup really any better than using pg_dump? For that reason I would guess no, but I will test to find out).

Comment 4 Tahlia Richardson 2016-08-31 06:20:08 UTC

From test:
Do require the RHV repo to install engine-backup on the new machine.
Do require a configured PostgreSQL database.

Comment 5 Tahlia Richardson 2016-09-01 06:12:39 UTC

doc-Administration_Guide/en-US/topics/Migrating_the_Engine_Database_to_a_Remote_Server_Database.xml 
* Replaced the procedure for setting up a PostgreSQL database with a link to the same procedure in the Install Guide
* Changed the migration procedure to use engine-backup. The restoring part is theoretical at the moment, as I wasn't able to test that part. I may be missing an important step? 

doc-Data_Warehouse_Guide/en-US/topics/Migrating_the_Data_Warehouse_Database_to_a_Separate_Machine.xml 
* Replaced the procedure for setting up a PostgreSQL database with a link to the same procedure in the Install Guide
* Changed the migration procedure to use engine-backup. The restoring part is theoretical at the moment, as I wasn't able to test that part. I may be missing an important step? 

doc-Administration_Guide/en-US/topics/Restoring_a_Backup_to_a_Fresh_Installation.xml 
and
doc-Installation_Guide/en-US/appe-Preparing_a_Remote_PostgreSQL_Database_for_Use_with_the_Red_Hat_Enterprise_Virtualization_Manager.xml 
* Updated with RHEL 7 commands
* Added an iptables step that is required in RHEL 7 (found in a RH solution)

Comment 6 Tahlia Richardson 2016-09-01 23:58:27 UTC

Existing backup and restore procedures in the Admin Guide, which I was using commands from, were out of date, which is why my testing failed. 
Restore command should include --provision-[dwh-]db and --no-restore-permissions (does it have to be no restore? can we restore permissions?), so a pre-configured PostgreSQL database is not necessary. 
I will update those sections, too, as part of this bug.

Comment 11 Tahlia Richardson 2016-09-12 06:31:07 UTC

Now published at 
https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/data-warehouse-guide/#Migrating_the_Data_Warehouse_Database_to_a_Separate_Machine and https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide/#sect-Backing_Up_and_Restoring_the_Red_Hat_Enterprise_Virtualization_Manager