Bug 1531912 - [Doc RFE] Document how to implement a disaster recovery policy to leverage geo-replication to failover data to a secondary site and protect data maintained in RHHI 2.0 deployment
Summary: [Doc RFE] Document how to implement a disaster recovery policy to leverage ge...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Deploying_RHHI
Version: rhgs-3.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHHI-V 1.5
Assignee: Laura Bailey
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1531908
TreeView+ depends on / blocked
 
Reported: 2018-01-06 16:48 UTC by Anjana Suparna Sriram
Modified: 2019-02-15 10:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-15 10:07:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Anjana Suparna Sriram 2018-01-06 16:48:55 UTC
Additional info:


As an administrator who is implementing a disaster recovery policy to protect data maintained in my RHHI 2.0 deployment, I need to understand what disaster recovery policies are available.

This use case includes documenting overview information that includes the following content:
(a) a brief statement as to the availability of geo-replication based disaster recovery for data maintained in an RHHI 2.0 deployment
(b) the advantages of implementing disaster recovery in an active-passive mode with failback to the backed up site
(c) a high-level overview of the implementation workflow
(d) A cross-reference to the disaster recovery content available in the Maintaining Red Hat Hyperconverged Infrastructure 2.0 documentation

Comment 8 Sahina Bose 2018-02-26 10:29:07 UTC
Aravinda, are they any considerations in case of failback with geo-replication. Once the master site is restored with data from secondary site, should the geo-rep session be recreated?

Comment 9 Aravinda VK 2018-03-12 03:58:37 UTC
(In reply to Sahina Bose from comment #8)
> Aravinda, are they any considerations in case of failback with
> geo-replication. Once the master site is restored with data from secondary
> site, should the geo-rep session be recreated?

Session already exists from Master site to secondary site. That is stopped while restoring data from secondary site. Once data is restored, this session needs to be started. (Secondary site to Primary site session need to be deleted)

Comment 13 Sahina Bose 2018-04-03 05:50:04 UTC
Is this different from Bug 1531916? I've provided my inputs there.

Comment 17 SATHEESARAN 2018-07-25 11:41:00 UTC
Content about DR and recovery process looks good.


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