# Multiple tribe nodes - disaster recovery

**URL:** <https://discuss.elastic.co/t/multiple-tribe-nodes-disaster-recovery/40057>\
**Category:** Elasticsearch\
**Created:** [January 25, 2016, 7:24pm UTC](https://discuss.elastic.co/t/multiple-tribe-nodes-disaster-recovery/40057 "2016-01-25T19:24:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![bennett](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bennett/32/4903_2.png) [@bennett](https://discuss.elastic.co/u/bennett)\
**Post date:** [January 25, 2016, 7:24pm UTC](https://discuss.elastic.co/t/multiple-tribe-nodes-disaster-recovery/40057/1 "2016-01-25T19:24:28Z")

</div>

Hi,

I have a setup with 3 tribe nodes, all looking at the same 4 elasticsearch clusters. The reason behind this, is they are all in separate datacenters and if one goes down, we still have visibility in the other 3 datacenters.

All the tribe nodes are looking at one index. But if that datacenter goes away, those tribenodes will no longer have the configurations.

Is there a way to sync the primary tribe node index to the other 2 tribe node index's? I was thinking of just doing an rsync every so often but wasn't sure if anyone else has an answer for this.

---

<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:** [January 25, 2016, 9:48pm UTC](https://discuss.elastic.co/t/multiple-tribe-nodes-disaster-recovery/40057/2 "2016-01-25T21:48:18Z")

</div>

> [@bennett](#):
>
> primary tribe node index

Can you elaborate on this, it's not clear what you mean as tribe nodes don't create indices, they just read.

---

<div class="post-metadata">

**Author:** ![bennett](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bennett/32/4903_2.png) [@bennett](https://discuss.elastic.co/u/bennett)\
**Post date:** [January 25, 2016, 9:50pm UTC](https://discuss.elastic.co/t/multiple-tribe-nodes-disaster-recovery/40057/3 "2016-01-25T21:50:44Z")

</div>

The dashboards and visuals and searches are saved to an index. Or is this not how it's suppose to go?

---

<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:** [January 25, 2016, 10:45pm UTC](https://discuss.elastic.co/t/multiple-tribe-nodes-disaster-recovery/40057/4 "2016-01-25T22:45:53Z")

</div>

So you mean the `.kibana` index.

There's currently no way in ES to really keep these synched across multiple clusters. You'd have to do something like Snapshot+Restore, maybe.

---

<div class="post-metadata">

**Author:** ![bennett](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bennett/32/4903_2.png) [@bennett](https://discuss.elastic.co/u/bennett)\
**Post date:** [January 26, 2016, 6:42pm UTC](https://discuss.elastic.co/t/multiple-tribe-nodes-disaster-recovery/40057/5 "2016-01-26T18:42:20Z")

</div>

yes, the .kibana (i forget that's the default, we renamed it).

thanks, that was my plan if there wasn't a proper solution.

---

<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 5, 2017, 11:21pm UTC](https://discuss.elastic.co/t/multiple-tribe-nodes-disaster-recovery/40057/6 "2017-07-05T23:21:20Z")

</div>