# Cross Cluster Replication - Disaster Recovery Failback

**URL:** <https://discuss.elastic.co/t/cross-cluster-replication-disaster-recovery-failback/275809>\
**Category:** Elasticsearch\
**Tags:** ccr-cross-cluster-replication\
**Created:** [June 14, 2021, 8:41am UTC](https://discuss.elastic.co/t/cross-cluster-replication-disaster-recovery-failback/275809 "2021-06-14T08:41:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rverchere](https://avatars.discourse-cdn.com/v4/letter/r/dbc845/32.png) [@rverchere](https://discuss.elastic.co/u/rverchere)\
**Post date:** [June 14, 2021, 8:41am UTC](https://discuss.elastic.co/t/cross-cluster-replication-disaster-recovery-failback/275809/1 "2021-06-14T08:41:58Z")

</div>

Hello,

I'm currently working on a CCR architecture, to use a follower cluster as a Disaster Recovery.  
I have a question with the failback:

1. When production cluster is down, then I use the DR (follower) one
2. I promote the follower as my main cluster, as users need to continue indexing data
3. Then I need to resync the production one with the up-to-date DR cluster, how can I manage this?

- Making my production cluster as follower, and once every data is sync'ed, promote to my main cluster?
- Restore my last known backup, but how can I get documents which where indexed in the DR cluster it there is no Message Queue system in front of the cluster?
- Any other idea?

Thanks for your feedback,

Rémi

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 15, 2021, 7:24am UTC](https://discuss.elastic.co/t/cross-cluster-replication-disaster-recovery-failback/275809/2 "2021-06-15T07:24:56Z")

</div>

You will probably want to setup bi-directional CCR in this case - [Bi-directional replication with Elasticsearch cross-cluster replication (CCR) | Elastic Blog](https://www.elastic.co/blog/bi-directional-replication-with-elasticsearch-cross-cluster-replication-ccr)

If you used specific index names in each cluster (eg `indexA` and `indexB`) and an alias pointing to the underlying index (eg `index`), you can use that to switch between which ever one you want to be the one the app writes to in each cluster.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 13, 2021, 7:25am UTC](https://discuss.elastic.co/t/cross-cluster-replication-disaster-recovery-failback/275809/3 "2021-07-13T07:25:09Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.