# How to clone ES+Kibana instance i.e. place a copy next to the same initial instance

**URL:** <https://discuss.elastic.co/t/how-to-clone-es-kibana-instance-i-e-place-a-copy-next-to-the-same-initial-instance/136477>\
**Category:** Elasticsearch\
**Created:** [June 19, 2018, 11:19am UTC](https://discuss.elastic.co/t/how-to-clone-es-kibana-instance-i-e-place-a-copy-next-to-the-same-initial-instance/136477 "2018-06-19T11:19:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mikhail](https://avatars.discourse-cdn.com/v4/letter/m/5daacb/32.png) [@Mikhail](https://discuss.elastic.co/u/Mikhail)\
**Post date:** [June 19, 2018, 11:19am UTC](https://discuss.elastic.co/t/how-to-clone-es-kibana-instance-i-e-place-a-copy-next-to-the-same-initial-instance/136477/1 "2018-06-19T11:19:20Z")

</div>

I have successfully configured Logstash+ES+Kibana instance on my QA environment.  
And have successfully filled ES with data.  
Next, I want to get a copy of ES+Kibana to create a separate QA instance that would not be affected by Logstash actions.  
It is obvious that simple "copy/paste" is not enough and I need to configure elasticsearch.yml and kibana.yml. A have done this. Namely:

- elasticsearch.yml  
\*\* node.name: qa2 (for initial instance I use default name: node-1)  
\*\* http.port: 5555 (for initial instance I use default port: 9200)
- kibana.yml  
\*\* server.port: 7777 (for initial instance I use default port: 5601)  
\*\* server.host: 192.168.71.91 (for initial instance I use the same)  
\*\* elasticsearch.url: "[http://localhost:5555](http://localhost:5555)" (for initial instance I use "[http://localhost:9200](http://localhost:9200)")

When I start elasticsearch.bat of copied ES I see the following error in cmd and in log-file:  
`Can't add node qa2, reason: found existing node with the same id but is a different node instance`  
When I start Kibana I see the following:  
Status Red  
plugin:elasticsearch@6.1.3 Service Unavailable

What else I need to do to clone my instance successfully?  
P.S. I also need a copy of all existing visualizations that were created in Kibana of initial instance

---

<div class="post-metadata">

**Author:** ![Mikhail](https://avatars.discourse-cdn.com/v4/letter/m/5daacb/32.png) [@Mikhail](https://discuss.elastic.co/u/Mikhail)\
**Post date:** [June 19, 2018, 12:02pm UTC](https://discuss.elastic.co/t/how-to-clone-es-kibana-instance-i-e-place-a-copy-next-to-the-same-initial-instance/136477/2 "2018-06-19T12:02:41Z")

</div>

I guess I have found solution here:

> **[Elasticsearch scaling and same node id problem – Francium Tech](https://blog.francium.tech/elasticsearch-scaling-and-same-node-id-problem-84c5d653f0ec?gi=69b361dbc23d)**
>
> We index huge amount of data using elasticsearch every 3 months. As a devops, I need to provision extra Elasticsearch EC2 instances…

Deleted `nodes` folder from `elasticsearch-6.1.3\data` folder and now everything seems to be ok. All Kibana stuff is in place.

---

<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 17, 2018, 12:02pm UTC](https://discuss.elastic.co/t/how-to-clone-es-kibana-instance-i-e-place-a-copy-next-to-the-same-initial-instance/136477/3 "2018-07-17T12:02:45Z")

</div>

Closed on July 17, 2018, 12:02pm UTC

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