# Backing up Kibana Dashboards on Docker Container with Snapshot and Restore

**URL:** <https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229>\
**Category:** Kibana\
**Created:** [February 6, 2020, 5:49pm UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229 "2020-02-06T17:49:24Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![14kporter](https://avatars.discourse-cdn.com/v4/letter/1/cc9497/32.png) [@14kporter](https://discuss.elastic.co/u/14kporter)\
**Post date:** [February 6, 2020, 5:49pm UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229/1 "2020-02-06T17:49:24Z")

</div>

Currently I am trying to find a way to backup the Elasticsearch data and the Kibana Dahsboards using the Snapshot and Restore. Right now the Elasticsearch and Kibana instances are hosted on their respective containers. Is there a way to regularly back up Kibana Dashboards from the Kibana instance? Preferably a way that could save off the dashboard and the Elasticsearch data to a repository?

---

<div class="post-metadata">

**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\
**Post date:** [February 7, 2020, 8:38am UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229/2 "2020-02-07T08:38:29Z")

</div>

Kibana has no own data store and stores all data in Elasticsearch in a special `.kibana` index. So if you back up all your Elasticsearch indices you have also backed up your Kibana data.

Backing up Elasticsearch is described in detail in the docs: [https://www.elastic.co/guide/en/elasticsearch/reference/current/backup-cluster.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/backup-cluster.html)

If you have follow-up question about backing up Elasticsearch feel free to ask in the Elasticsearch forum for further guidance.

---

<div class="post-metadata">

**Author:** ![14kporter](https://avatars.discourse-cdn.com/v4/letter/1/cc9497/32.png) [@14kporter](https://discuss.elastic.co/u/14kporter)\
**Post date:** [February 14, 2020, 2:33pm UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229/3 "2020-02-14T14:33:32Z")

</div>

How do you get the .kibana index to populate? I have been unable to find this in indexes or and documentation on how to get the .kibana index in Elasticsearch.

---

<div class="post-metadata">

**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\
**Post date:** [February 14, 2020, 2:56pm UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229/4 "2020-02-14T14:56:17Z")

</div>

I'm not sure what you are referring to - `.kibana` is a regular index stored in Elasticsearch. It is searchable and modifiable with the regular commands over the REST api of Elasticsearch, just like your data indices.

---

<div class="post-metadata">

**Author:** ![14kporter](https://avatars.discourse-cdn.com/v4/letter/1/cc9497/32.png) [@14kporter](https://discuss.elastic.co/u/14kporter)\
**Post date:** [February 17, 2020, 5:49pm UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229/5 "2020-02-17T17:49:20Z")

</div>

The .kibana index does not exist in the my Elasticsearch and is no callable over REST api of Elasticsearch. Nothing is returned from the .kibana index. There must be a missing piece. Do you have any suggestions?

---

<div class="post-metadata">

**Author:** ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)\
**Post date:** [February 17, 2020, 9:34pm UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229/6 "2020-02-17T21:34:57Z")

</div>

Kibana creates a `.kibana` alias that points to `.kibana_n` where n is an increasing number each time Kibana performs migrations. There is no reason the Elasticsearch REST API shouldn't work so you might be sending requests to the wrong cluster.

What's the output of `GET _cat/indices` and `GET _cat/aliases`?

---

<div class="post-metadata">

**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\
**Post date:** [February 18, 2020, 9:43am UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229/7 "2020-02-18T09:43:42Z")

</div>

Along with what @rudolf said:

- If you have a security solution running, please check whether the ES user you are using to access the data has read rights for the `.kibana`/`.kibana_*` indices.
- It's possible to change the index Kibana stores data in by setting `kibana.index` to something else in your `kibana.yml`. Please check whether this setting is present for you.

---

<div class="post-metadata">

**Author:** ![14kporter](https://avatars.discourse-cdn.com/v4/letter/1/cc9497/32.png) [@14kporter](https://discuss.elastic.co/u/14kporter)\
**Post date:** [February 18, 2020, 2:32pm UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229/8 "2020-02-18T14:32:26Z")

</div>

> [@rudolf](#):
>
> GET \_cat/indices

Thank you for your help! Below is the output that I got:

![image](https://us1.discourse-cdn.com/elastic/original/3X/8/7/8782214db3f6a374bebfa3cfb45fd5637da73e86.png)

---

<div class="post-metadata">

**Author:** ![14kporter](https://avatars.discourse-cdn.com/v4/letter/1/cc9497/32.png) [@14kporter](https://discuss.elastic.co/u/14kporter)\
**Post date:** [February 18, 2020, 4:34pm UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229/9 "2020-02-18T16:34:29Z")

</div>

- I currently do no have a security solution running
- I have added the kibana.index as an environment variable. I do not see the index populating in index management.

---

<div class="post-metadata">

**Author:** ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)\
**Post date:** [February 25, 2020, 6:47pm UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229/10 "2020-02-25T18:47:37Z")

</div>

The output of `_cat/indices` shows that you have a `.kibana` alias that points to the `.kibana_1` index and that it contains documents. So if you're unable to query this index, there is something wrong in the way in which you use the Elasticsearch REST API.

---

<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 24, 2020, 6:47pm UTC](https://discuss.elastic.co/t/backing-up-kibana-dashboards-on-docker-container-with-snapshot-and-restore/218229/11 "2020-03-24T18:47:47Z")

</div>

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