# Snapshots recovery **URL:** \ **Category:** Elasticsearch\ **Created:** [May 22, 2019, 7:09am UTC](https://discuss.elastic.co/t/snapshots-recovery/182152 "2019-05-22T07:09:43Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![rodrigue](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@rodrigue](https://discuss.elastic.co/u/rodrigue)\ **Post date:** [May 22, 2019, 7:09am UTC](https://discuss.elastic.co/t/snapshots-recovery/182152/1 "2019-05-22T07:09:43Z")
Hello, I have a special problem. I can't find a solution because I have problems to explain it. I'm using ELK and I create a new index every day. In order to free space on my production system, I'm creating compressed snapshots, and then I retrieve those snapshots on my local system. Once the snapshots have been recovered I delete them from production. Everything works fine except for one detail : - The snapshots are not visible on my local system. The files are here, but elastic doesn't see them, and I known why : It's because I synchronize the snapshot with rsync. Rsync pulls the new snapshots, and pulls as well the repository metadatas. When I delete the snapshot on my production system, the files are deleted from the production disk, and the snapshot properties (ex : snapshot list) are updated. Then, when I execute rsync, my local repository properties are updated and the snaphot disapears (but the files remain). I'll give you an exemple : On my production I create a snapshot called snapshot.2018-05-21 containing the logstash index logstash.2018-05-21. Then I rsync the repository : all the files are transfered to my local drive. The next day, I create a snapshot called snapshot.2018-05-22 containing the logstash index lostash.2018-05-22. I delete the snapshot snapshot.2018-05-21. Then I rsync the repository : all the new files are transfered, but the old files are not deleted. Once this operation is finished, on my local drive I have the snapshot files for 2018-05-21 and 2018-05-22, but my local repository thinks that the 2018-05-21 was deleted (because I deleted it on production, and the repository properties has been synchronized) Here is my question : Is there an elastic command to help me ? I need to re-scan my repository, on my local system, in order that elastic detects that my old snapshot (2018-05-21) still exists? I hope I was clear... Maybe I'm not using your tool right. At the end, what I need is a big backup on my local system, with 3 years of history. On my production, I only need 6 month. Because of network restrictions, my servers can't speak together. I need to work with SSH. ---
**Author:** ![rodrigue](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@rodrigue](https://discuss.elastic.co/u/rodrigue)\ **Post date:** [May 29, 2019, 7:26am UTC](https://discuss.elastic.co/t/snapshots-recovery/182152/2 "2019-05-29T07:26:20Z")
Hello, Is there anyone to help me with my problem? Should I add some explanations? Thanks for your help, I really don't know what to do. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [May 29, 2019, 10:49am UTC](https://discuss.elastic.co/t/snapshots-recovery/182152/3 "2019-05-29T10:49:45Z")
> [@rodrigue](#): > > Here is my question : Is there an elastic command to help me ? I need to re-scan my repository, on my local system, in order that elastic detects that my old snapshot (2018-05-21) still exists? No, I can't think of a way to do that. > [@rodrigue](#): > > At the end, what I need is a big backup on my local system, with 3 years of history. On my production, I only need 6 month. > Because of network restrictions, my servers can't speak together. I need to work with SSH. I think it'd work better to create a new repository every so often (e.g. monthly). Then, rather than deleting individual snapshots from your single repository, you can delete an entire repository when it's no longer needed. ---
**Author:** ![rodrigue](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@rodrigue](https://discuss.elastic.co/u/rodrigue)\ **Post date:** [May 29, 2019, 11:00am UTC](https://discuss.elastic.co/t/snapshots-recovery/182152/4 "2019-05-29T11:00:06Z")
Right, thanks... I should have thought of this solution myself. I'm alone on this project and I seriously need more brain storming! Thanks. I'll do what you suggest and delete big repositories instead of small snapshots... But still, maybe you should think about this feature. I don't think that I'm the only one trying to do things like that... And even more. Let's imagine that there is a disk problem and the repository is corrupted. It could be a great idea to re-scan it... Have a nice day 😃 ---
**Author:** ![rodrigue](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@rodrigue](https://discuss.elastic.co/u/rodrigue)\ **Post date:** [May 29, 2019, 11:34am UTC](https://discuss.elastic.co/t/snapshots-recovery/182152/5 "2019-05-29T11:34:50Z")
Oh, and just one last question... Now that I'm in this situation, is eveything lost? I mean, I have nearly 12 month of files that are invisible. Is there a way to cheat (rename a folder, or change a parameter by hand) Maybe I could create fake snapshots and copy the file in it? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [May 29, 2019, 12:49pm UTC](https://discuss.elastic.co/t/snapshots-recovery/182152/6 "2019-05-29T12:49:29Z")
> [@rodrigue](#): > > maybe you should think about this feature. I don't think that I'm the only one trying to do things like that I would expect most people to allow their production clusters to write directly to the proper location rather than to try and do what you're doing with `rsync`. Can you explain the benefits of your setup? > [@rodrigue](#): > > Now that I'm in this situation, is eveything lost? I mean, I have nearly 12 month of files that are invisible. Is there a way to cheat I can't think of one, unless you've got some way of rolling everything in the repository back to an earlier version. ---
**Author:** ![rodrigue](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@rodrigue](https://discuss.elastic.co/u/rodrigue)\ **Post date:** [May 29, 2019, 3:20pm UTC](https://discuss.elastic.co/t/snapshots-recovery/182152/7 "2019-05-29T15:20:20Z")
The price. My production system costs a lot and my local system is free. Everything is backed up on bands... We pay a provider for our production and it costs a lot. We don't need this kind of service for logging production logs. Moreover, elastic is a little slow when there is a lot of data, and when we need big statistics, we prefer to execute it on a local, non critical, machine. If the query is too big and the machine crashs, we just restart it... Thanks a lot for your help. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 26, 2019, 3:20pm UTC](https://discuss.elastic.co/t/snapshots-recovery/182152/8 "2019-06-26T15:20:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.