# HDSF backup restore no progress info **URL:** \ **Category:** Elasticsearch\ **Created:** [July 21, 2015, 2:03pm UTC](https://discuss.elastic.co/t/hdsf-backup-restore-no-progress-info/25989 "2015-07-21T14:03:09Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![awislowski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/awislowski/32/3789_2.png) [@awislowski](https://discuss.elastic.co/u/awislowski)\ **Post date:** [July 21, 2015, 2:03pm UTC](https://discuss.elastic.co/t/hdsf-backup-restore-no-progress-info/25989/1 "2015-07-21T14:03:09Z")
Hi, I have a problem with restoring backup through hdfs plugin (elasticsearch/elasticsearch-repository-hdfs/2.1.0-hadoop2) on elasticsearch cluster version 1.6.0 I was restoring 12GB data (20000000 documents) backup from hdfs. After calling: POST \_snapshot/CLUSTER\_NAME/SNAPSHOT\_NAME/\_restore I got answer ok, but - GET \_snapshot/\_status - does not return any info about restoring - GET \_cat/indices - shows added restored index in state red with only one element per shard. - no info in server logs - second try to run restore result in error message f.e. { "error": "ConcurrentSnapshotExecutionException[[CLUSTER\_NAME:SNAPSHOT\_NAME] Restore process is already running in this cluster]", "status": 503} - GET \_cat/shards index\_name 0 p INITIALIZING 8.55.24.233 node1 index\_name 0 r UNASSIGNED index\_name 1 p INITIALIZING 8.55.24.234 node2 index\_name 1 r UNASSIGNED - the only log that restore is taking place is 15 IOPS and 4MB per sec on disk write - and finally after 30 min data stared to grow in the index. and ended in 7 minut. Why does no progress info is presented? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 23, 2015, 7:25am UTC](https://discuss.elastic.co/t/hdsf-backup-restore-no-progress-info/25989/2 "2015-07-23T07:25:23Z")
Anything in your ES logs that might be of use? ---
**Author:** ![awislowski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/awislowski/32/3789_2.png) [@awislowski](https://discuss.elastic.co/u/awislowski)\ **Post date:** [July 23, 2015, 7:39am UTC](https://discuss.elastic.co/t/hdsf-backup-restore-no-progress-info/25989/3 "2015-07-23T07:39:16Z")
Even after changing logs into debug level there was no single line about restore. ---
**Author:** ![awislowski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/awislowski/32/3789_2.png) [@awislowski](https://discuss.elastic.co/u/awislowski)\ **Post date:** [July 29, 2015, 6:33pm UTC](https://discuss.elastic.co/t/hdsf-backup-restore-no-progress-info/25989/4 "2015-07-29T18:33:40Z")
To close the thread @costin has helped me in the issue on the github: ``` To quote the docs: ``` The cluster health operation provides only a high level status of the restore process. It’s possible to get more detailed insight into the current state of the recovery process by using indices recovery and cat recovery APIs. In other words, see [https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-recovery.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-recovery.html) and [https://www.elastic.co/guide/en/elasticsearch/reference/current/cat-recovery.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/cat-recovery.html) That is for recovery, use the dedicated endpoint APIs. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:58pm UTC](https://discuss.elastic.co/t/hdsf-backup-restore-no-progress-info/25989/5 "2017-07-05T23:58:16Z")