# How to fix repository\_missing\_exception?

**URL:** <https://discuss.elastic.co/t/how-to-fix-repository-missing-exception/122013>\
**Category:** Elasticsearch\
**Created:** [March 1, 2018, 9:38am UTC](https://discuss.elastic.co/t/how-to-fix-repository-missing-exception/122013 "2018-03-01T09:38:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![asp](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@asp](https://discuss.elastic.co/u/asp)\
**Post date:** [March 1, 2018, 9:38am UTC](https://discuss.elastic.co/t/how-to-fix-repository-missing-exception/122013/1 "2018-03-01T09:38:24Z")

</div>

Hi,

I made a snapshot on production tared the complete repository folder and moved it to another system for deeper analysis.  
Path configuration for repository and snapshot is identical.

But on my target system I had too few storage, so I added a 2nd harddisk and tried:

- symlinking the new harddisk to the repository folder
- mounting the new harddisk directly to the repository folder

Then I extracted the tar there.  
But my snapshots are not listed:

```
GET _snapshot/export

->

{
  "export": {
    "type": "fs",
    "settings": {
      "location": "/usr/local/elk/backup/export"
    }
  }
}

GET _snapshot/export/_all

->

{
  "error": {
    "root_cause": [
      {
        "type": "repository_missing_exception",
        "reason": "[export] missing"
      }
    ],
    "type": "repository_missing_exception",
    "reason": "[export] missing"
  },
  "status": 404
}

```

in filesystem it looks l

in filesystem it looks like this:

```
[root@vm export]# pwd
/usr/local/elk/backup/export

[root@vm export]# ls -l
insgesamt 60
-rw-r--r-- 1 elasticsearch elasticsearch 29 24. Jan 09:37 incompatible-snapshots
-rw-r--r-- 1 elasticsearch elasticsearch 1664 24. Jan 11:20 index-1
-rw-r--r-- 1 elasticsearch elasticsearch 1744 24. Jan 15:27 index-2
-rw-r--r-- 1 elasticsearch elasticsearch 8 24. Jan 15:27 index.latest
drwxr-xr-x 14 elasticsearch elasticsearch 4096 24. Jan 11:20 indices
drwx------ 2 root root 16384 1. Mär 09:08 lost+found
-rw-r--r-- 1 elasticsearch elasticsearch 90 24. Jan 15:27 meta-5HRAvCrzTMWjkk3gCsui5Q.dat
-rw-r--r-- 1 elasticsearch elasticsearch 90 24. Jan 09:34 meta-AbNDcf5_TjWV-HPFIWdsOg.dat
-rw-r--r-- 1 elasticsearch elasticsearch 90 24. Jan 11:20 meta-IJ4iNAWTQ5Oxug8mEvrPBw.dat
-rw-r--r-- 1 elasticsearch elasticsearch 230 24. Jan 15:27 snap-5HRAvCrzTMWjkk3gCsui5Q.dat
-rw-r--r-- 1 elasticsearch elasticsearch 513 24. Jan 09:37 snap-AbNDcf5_TjWV-HPFIWdsOg.dat
-rw-r--r-- 1 elasticsearch elasticsearch 561 24. Jan 11:20 snap-IJ4iNAWTQ5Oxug8mEvrPBw.dat
[root@vm export]#

```

so, permissions are correct.

Any pitfall I trapped in?

Thanks, Andreas

---

<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:** [March 29, 2018, 9:38am UTC](https://discuss.elastic.co/t/how-to-fix-repository-missing-exception/122013/2 "2018-03-29T09:38:27Z")

</div>

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