# Restore snapshot from another cluster (7.8 to 8.5) **URL:** \ **Category:** Kibana\ **Tags:** snapshot-and-restore\ **Created:** [January 9, 2023, 3:51pm UTC](https://discuss.elastic.co/t/restore-snapshot-from-another-cluster-7-8-to-8-5/322747 "2023-01-09T15:51:44Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Maria\_Gabriela\_Perez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maria_gabriela_perez/32/100571_2.png) [@Maria\_Gabriela\_Perez](https://discuss.elastic.co/u/Maria_Gabriela_Perez)\ **Post date:** [January 9, 2023, 3:51pm UTC](https://discuss.elastic.co/t/restore-snapshot-from-another-cluster-7-8-to-8-5/322747/1 "2023-01-09T15:51:44Z")
I have a question/problem. I have a GCP bucket with tons of snapshots taken from a kibana 7.8, A new kibana has been deployed in another cluster v8.5, that kibana has been connected to the GCP bucket where the old kibana snapshots are being stored, but even when the kibana connects succesfully to the bucket it doesn't detect any snapshots. Am I missing something? What should I take into consideration in this case? is this accomplishable? ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [January 16, 2023, 5:16pm UTC](https://discuss.elastic.co/t/restore-snapshot-from-another-cluster-7-8-to-8-5/322747/2 "2023-01-16T17:16:57Z")
Have you tried to [query the snapshots](https://www.elastic.co/guide/en/elasticsearch/reference/current/get-snapshot-api.html) repository with the Kibana Dev tools? A query like this should list the available snapshots in your repository ```auto GET _snapshot/{repository_name}/* ``` If that query does not return any data then this feels more an issue with the repository configuration and it should be forwarded to the Elasticsearch forum. If what you see in the query results is not the same presented by the Kibana Stack Management interface then that seems more like a bug that would need further exploration. According to the [documentation,](https://www.elastic.co/guide/en/elasticsearch/reference/8.6/snapshot-restore.html#snapshot-index-compatibility) snapshots created with 7.8 should be compatible with 8.5. ---
**Author:** ![Maria\_Gabriela\_Perez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maria_gabriela_perez/32/100571_2.png) [@Maria\_Gabriela\_Perez](https://discuss.elastic.co/u/Maria_Gabriela_Perez)\ **Post date:** [January 18, 2023, 9:34pm UTC](https://discuss.elastic.co/t/restore-snapshot-from-another-cluster-7-8-to-8-5/322747/3 "2023-01-18T21:34:17Z")
yes.. and nothing came up ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [January 19, 2023, 10:22am UTC](https://discuss.elastic.co/t/restore-snapshot-from-another-cluster-7-8-to-8-5/322747/4 "2023-01-19T10:22:54Z")
If your query does not return any results then I'd suggest to review the settings of your repository to confirm everything is correct (permissions, authentication, paths, etc). ---
**Author:** ![Maria\_Gabriela\_Perez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maria_gabriela_perez/32/100571_2.png) [@Maria\_Gabriela\_Perez](https://discuss.elastic.co/u/Maria_Gabriela_Perez)\ **Post date:** [January 23, 2023, 3:24pm UTC](https://discuss.elastic.co/t/restore-snapshot-from-another-cluster-7-8-to-8-5/322747/5 "2023-01-23T15:24:21Z")
For anyone interested, the problem was the version of Elasticsearch used, a 7.8v was deployed and snapshots were found. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 20, 2023, 3:24pm UTC](https://discuss.elastic.co/t/restore-snapshot-from-another-cluster-7-8-to-8-5/322747/6 "2023-02-20T15:24:30Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.