Currently we provide instructions to backup and restore the self-hosted engine VM by creating a new self-hosted engine environment[1]. We need to add instructions to restore the self-hosted engine Manager DB without needing to create a new environment. See comment 35, 36 in BZ#1420604[2] We can link to the current Restore procedure in the Admin Guide[3], but we need to add instructions to move the environment into global maintenance before performing the procedure, and exit global maintenance after restoring the environment. [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/self-hosted_engine_guide/#chap-Backing_up_and_Restoring_a_RHEL-Based_Self-Hosted_Environment [2] https://bugzilla.redhat.com/show_bug.cgi?id=1420604 [3] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/administration_guide/#Restoring_a_Backup_to_Overwrite_an_Existing_Installation
*** Bug 1512583 has been marked as a duplicate of this bug. ***
Moving this one back to the unassigned queue while we await further information.
Targeting at 4.3, to be reviewed together with bug 1420604 as part of the overall content strategy for SHE backup and restore.
Isn't this is what we are asking here: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/self-hosted_engine_guide/sect-restoring_she_bkup#Restoring_the_Self-Hosted_Engine_Manager_Manually
(In reply to Marina from comment #24) > Isn't this is what we are asking here: > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ > html/self-hosted_engine_guide/sect-restoring_she_bkup#Restoring_the_Self- > Hosted_Engine_Manager_Manually I don't think so; that procedure is still for restoring in a new environment rather than over an existing one (although the way the content is structured makes that a little unclear at first).
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.