Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1284364 - (RHV_DR) [RFE][Tracker] recovery manager for disaster recovery in RHV
[RFE][Tracker] recovery manager for disaster recovery in RHV
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs (Show other bugs)
3.5.0
All All
high Severity urgent
: ovirt-4.2.3
: ---
Assigned To: Tal Nisan
Elad
http://www.ovirt.org/develop/projects...
: FutureFeature, Tracking
: 890655 1021066 1117056 1395763 (view as bug list)
Depends On: 1193961 1205739 1393839 1451018 1458745 1460513
Blocks: 1181636 1534978
  Show dependency treegraph
 
Reported: 2015-11-23 02:20 EST by Gajanan
Modified: 2018-07-04 08:44 EDT (History)
18 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1534978 (view as bug list)
Environment:
Last Closed: 2018-05-15 13:36:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
ratamir: testing_plan_complete+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Bugzilla 1489232 None CLOSED [Docs][RFE] Document Active-Active Disaster Recovery failover using a stretch cluster 2018-10-04 04:58 EDT
Red Hat Knowledge Base (Solution) 2044903 None None None 2017-10-29 20:53 EDT
Red Hat Product Errata RHEA-2018:1488 None None None 2018-05-15 13:38 EDT

  None (edit)
Description Gajanan 2015-11-23 02:20:53 EST
============= RFE REQUEST ================

1. Proposed title of this feature request

SRM - site recovery manager for disaster recovery in RHEV

3. What is the nature and description of the request?

Customer is looking for a feature like VMware site recovery manager for  disaster recovery. Like taking a VM from on RHEV site and failing it over to another. VMware uses a tool called SRM which creates a plan that will break our snapmirror (NetApp NAS/SAN) between the Prod and DR site and will mount once broken. 

https://www.vmware.com/products/site-recovery-manager

Customer wants this feature for RHEV. 


4. Why does the customer need this? (List the business requirements here)

> To failover our Production environment to our Disaster recovery site.

5. How would the customer like to achieve this? (List the functional requirements here)

> A pluging that would see both our storage devices (netapp filers) on both end (RHEV prod, RHEV colo) that would allow us to create a recovery plan and automatically spin up the VMs when the plan is initiated. This would see the array replication and make corrective actions when needed.

https://www.youtube.com/watch?v=kgZ62GS21Vc (great video on how SRM works)


6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

> No

8. Does the customer have any specific timeline dependencies and which release would they like to target ?

> None, we have a manual way of doing it now. Breaking a snapmirror and turning the host on the other side.

9. Is the sales team involved in this request and do they have any additional input?

10. List any affected packages or components.

11. Would the customer be able to assist in testing this functionality if implemented?

>  Possibly, depending if this does not affect our production environment.
Comment 2 Yaniv Lavi 2016-01-10 10:43:33 EST
*** Bug 890655 has been marked as a duplicate of this bug. ***
Comment 3 Yaniv Lavi 2016-01-10 10:59:45 EST
*** Bug 1021066 has been marked as a duplicate of this bug. ***
Comment 6 Oved Ourfali 2016-01-31 12:21:23 EST
*** Bug 1117056 has been marked as a duplicate of this bug. ***
Comment 11 Yaniv Lavi 2017-06-13 05:04:47 EDT
*** Bug 1395763 has been marked as a duplicate of this bug. ***
Comment 15 Elad 2018-05-10 16:24:04 EDT
Site to site:
Covered all the feature's functionality, including fail over and fail back (which include generate mapping and validator). According to Polarion test plan external tracker attached.


Used:
ovirt-ansible-disaster-recovery-0.4-1.el7ev.noarch
ansible-2.5.2-1.el7ae.noarch


Active active:
Certified according to https://docs.google.com/document/d/1-ZWco1Z-BcTJezqSGhdQC9gBSC79sw9cDiq7Dfx_czE/edit
Comment 18 errata-xmlrpc 2018-05-15 13:36:24 EDT
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.

https://access.redhat.com/errata/RHEA-2018:1488

Note You need to log in before you can comment on or make changes to this bug.