Bug 1422144

Summary: [Docs][RFE][Admin] Option to remove previous hosted engine when performing Backup and restore
Product: Red Hat Enterprise Virtualization Manager Reporter: Emma Heftman <eheftman>
Component: DocumentationAssignee: rhev-docs <rhev-docs>
Status: CLOSED DUPLICATE QA Contact: rhev-docs <rhev-docs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: gklein, lbopf, lsurette, rbalakri, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.1.1Keywords: FutureFeature
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: 2017-03-29 11:53:15 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: 1235200    
Bug Blocks:    

Description Emma Heftman 2017-02-14 15:04:03 UTC
Backup and restore of hosted-engine will now include the possibility to use a CLI command to remove the

Comment 1 Yaniv Lavi 2017-02-21 12:54:03 UTC
Previously, when restoring a backup of a hosted engine on a different environment, for disaster recovery purposes, administrators were sometimes required to remove the previous hosts from the engine. This was accomplished from within the engine's database, which is a risk-prone procedure.
In this release, a new CLI option can be used during the restore procedure to enable administrators to remove the previous host directly from the engine backup.

Scenario setup: 
- Deploy hosted-engine on a couple of hosts;
- also add an host not involved in hosted-engine
- add a regular storage domain,
- add a couple of VMs
- take a backup of the engine with engine-backup

Try the recovery over two different hosts and also over the same hosts:
- start hosted-engine-setup on the first host
- point to the same storage
- respond no to: 'Automatically execute engine-setup on the engine appliance on first boot'
- copy the backup of the engine DB to the engine VM
- connect to the engine VM and execute engine-backup to restore the backup appending --he-remove-hosts option
- execute engine-setup
- come back to hosted-engine-setup and terminate the deployment

At the end only the host where you run hosted-engine --deploy should be there as an hosted-engine host; other hosts (non involved in HE) should be there as well

Comment 2 Lucy Bopf 2017-03-29 11:53:15 UTC
We will use bug 1420604 to track items related to SHE backup and restore, and use the information in comment 1 as a reference.

Closing as duplicate.

*** This bug has been marked as a duplicate of bug 1420604 ***