# Shards remain UNASSIGNED after \_restore operation **URL:** \ **Category:** Elasticsearch\ **Created:** [February 15, 2017, 6:53pm UTC](https://discuss.elastic.co/t/shards-remain-unassigned-after--restore-operation/75239 "2017-02-15T18:53:35Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![jspooner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jspooner/32/12984_2.png) [@jspooner](https://discuss.elastic.co/u/jspooner)\ **Post date:** [February 16, 2017, 12:25am UTC](https://discuss.elastic.co/t/shards-remain-unassigned-after--restore-operation/75239/2 "2017-02-16T00:25:19Z")
After a few hours of debugging I narrowed the issue down to an issue with \_id. I moved the issue over to a new question > [@Restoring to a different cluster with version 5.2.0](https://discuss.elastic.co/t/restoring-to-a-different-cluster/75255): > > In the guides for [restoring to a different cluster](https://www.elastic.co/guide/en/elasticsearch/reference/5.2/modules-snapshots.html#_restoring_to_a_different_cluster) it says If indices in the original cluster were assigned to particular nodes using shard allocation filtering, the same rules will be enforced in the new cluster. Therefore if the new cluster doesn’t contain nodes with appropriate attributes that a restored index can be allocated on, such index will not be successfully restored unless these index allocation settings are changed during restore operation. In my situation I have an index that w… --- _[View the full topic](https://discuss.elastic.co/t/shards-remain-unassigned-after--restore-operation/75239)._