# Updating .kibana on the unpreferred cluster node when using tribe architecture

**URL:** <https://discuss.elastic.co/t/updating-kibana-on-the-unpreferred-cluster-node-when-using-tribe-architecture/74924>\
**Category:** Elasticsearch\
**Created:** [February 13, 2017, 7:38pm UTC](https://discuss.elastic.co/t/updating-kibana-on-the-unpreferred-cluster-node-when-using-tribe-architecture/74924 "2017-02-13T19:38:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mr\_chang7](https://avatars.discourse-cdn.com/v4/letter/m/cc9497/32.png) [@mr\_chang7](https://discuss.elastic.co/u/mr_chang7)\
**Post date:** [February 13, 2017, 7:38pm UTC](https://discuss.elastic.co/t/updating-kibana-on-the-unpreferred-cluster-node-when-using-tribe-architecture/74924/1 "2017-02-13T19:38:50Z")

</div>

I have two separate ES nodes and put a tribe node with preferring one of the ES nodes by setting the on\_conflict attribute. I specifically interested in the .kibana index to be updated in the un-preferred node to protect any failure of the preferred node. What would be your recommendations? Or wondering if there a simple way to update/copy the .kibana index to another ES server.

p.s. not using the manual export/import on kibana

Thanks!

---

<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:** [March 13, 2017, 7:38pm UTC](https://discuss.elastic.co/t/updating-kibana-on-the-unpreferred-cluster-node-when-using-tribe-architecture/74924/2 "2017-03-13T19:38:54Z")

</div>

Closed on March 13, 2017, 7:38pm UTC

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