# .kibana\_task\_manager index red in ECK , no snapshot possible

**URL:** <https://discuss.elastic.co/t/kibana-task-manager-index-red-in-eck-no-snapshot-possible/323902>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Tags:** snapshot-and-restore\
**Created:** [January 25, 2023, 9:35am UTC](https://discuss.elastic.co/t/kibana-task-manager-index-red-in-eck-no-snapshot-possible/323902 "2023-01-25T09:35:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Suny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suny/32/22082_2.png) [@Suny](https://discuss.elastic.co/u/Suny)\
**Post date:** [January 25, 2023, 9:35am UTC](https://discuss.elastic.co/t/kibana-task-manager-index-red-in-eck-no-snapshot-possible/323902/1 "2023-01-25T09:35:25Z")

</div>

We have two Elasticsearch clusters in Kubernetes, managed by ECK (on Azure AKS), and are now trying to implement snapshots. The repository is in place.  
However, when we try to actually take a snapshot, we get an error:

```auto
{"error":{"root_cause":[{"type":"snapshot_exception","reason":"[test_repo_1:test-snapshot/aPrOh1pfQi6tb7mwRgHAzw] Indices don't have primary shards [.kibana_task_manager_8.2.3_001]"}],"type":"snapshot_exception","reason":"[test_repo_1:test-snapshot/aPrOh1pfQi6tb7mwRgHAzw] Indices don't have primary shards [.kibana_task_manager_8.2.3_001]"},"status":500}

```

The `.kibana_task_manager_8.2.3_001` index is red on both clusters. This is a major issue for us.

Is there a way to restore that index?  
Or should we use a different way to backup our (rather small) indices, like exporting as json to disk?

A user reported a similar issues [here](https://discuss.elastic.co/t/kibana-index-kibana-task-manager-goes-unassigned-after-few-days-and-cause-red-cluster-health-on-eck/309104), but ther is no answer.

---

<div class="post-metadata">

**Author:** ![Suny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suny/32/22082_2.png) [@Suny](https://discuss.elastic.co/u/Suny)\
**Post date:** [January 25, 2023, 1:45pm UTC](https://discuss.elastic.co/t/kibana-task-manager-index-red-in-eck-no-snapshot-possible/323902/2 "2023-01-25T13:45:55Z")

</div>

We ended up using Elasticsearch only as a temporary storage and doing the data security part in another system.

Technically, we were able to make the the index green - but empty - with

```auto
curl -XPOST "https://$HOST/elasticsearch/_cluster/reroute?pretty" -H 'Content-Type: application/json' -d'
{
    "commands": [{
        "allocate_empty_primary": {
            "index": ".kibana_task_manager_8.2.3_001",
            "shard": 0,
            "node": "any-old-node",
			"accept_data_loss":true
        }
    }]
}'

```

However, this means losing our backups.  
Our manager told us to use a database with proven backup / restore mechanism instead, and we could only agree.

Generally, metadata that is critical for Backup / Restore should not be kept in the system itself. In this case, that wasn't even the issue, just that this index is flaky in ECK.

---

<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:** [February 22, 2023, 1:46pm UTC](https://discuss.elastic.co/t/kibana-task-manager-index-red-in-eck-no-snapshot-possible/323902/3 "2023-02-22T13:46:10Z")

</div>

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