# Problem backing-up indexes when using VM on NAS

**URL:** <https://discuss.elastic.co/t/problem-backing-up-indexes-when-using-vm-on-nas/201818>\
**Category:** Elasticsearch\
**Created:** [October 1, 2019, 2:00pm UTC](https://discuss.elastic.co/t/problem-backing-up-indexes-when-using-vm-on-nas/201818 "2019-10-01T14:00:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![neergttocsdivad](https://avatars.discourse-cdn.com/v4/letter/n/43a26b/32.png) [@neergttocsdivad](https://discuss.elastic.co/u/neergttocsdivad)\
**Post date:** [October 1, 2019, 2:00pm UTC](https://discuss.elastic.co/t/problem-backing-up-indexes-when-using-vm-on-nas/201818/1 "2019-10-01T14:00:53Z")

</div>

My files to be indexed are stored on volume1 of a Synology NAS  
elasticsearch, kibana and fscrawler are running on a VM, also on volume1  
Hyper-Backup backs-up the contents of volume1 to a second volume(2)  
I would like to backup elasticsearch indexeswith reference to this website ([https://askubuntu.com/questions/205841/how-do-i-mount-a-folder-from-another-partition](https://askubuntu.com/questions/205841/how-do-i-mount-a-folder-from-another-partition)) I have added a line in fstab which makes the index folder accessible to Hyper-Backup

/media/elastic-indexes /var/lib/elasticsearch none bind

now, I can see and open '/var/lib/elasticsearch', from Synology File Station, but the indexes have gone

```auto
14:30:37,674 INFO [f.p.e.c.f.c.BootstrapChecks] Memory [Free/Total=Percent]: HEAP [473.3mb/7.8gb=5.89%], RAM [25.5gb/31.4gb=81.37%], Swap [1.9gb/1.9gb=100.0%].
14:30:39,818 INFO [f.p.e.c.f.c.v.ElasticsearchClientV7] Elasticsearch Client for version 7.x connected to a node running version 7.3.2
14:30:40,044 INFO [f.p.e.c.f.FsCrawlerImpl] Starting FS crawler
14:30:40,044 INFO [f.p.e.c.f.FsCrawlerImpl] FS crawler started in watch mode. It will run unless you stop it with CTRL+C.
14:31:10,494 WARN [f.p.e.c.f.c.v.ElasticsearchClientV7] failed to create index [numb3rs], disabling crawler...
14:31:10,494 FATAL [f.p.e.c.f.c.FsCrawlerCli] **Fatal error received while running the crawler: [Elasticsearch exception [type=master_not_discovered_exception, reason=null]]**
14:31:10,497 INFO [f.p.e.c.f.FsCrawlerImpl] FS crawler [numb3rs] stopped
14:31:10,498 INFO [f.p.e.c.f.FsCrawlerImpl] FS crawler [numb3rs] stopped
root@volume1:/media/fscrawler# 

```

Is there a way for Hyper-Backup to 'see' and backup my indexes?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 1, 2019, 2:39pm UTC](https://discuss.elastic.co/t/problem-backing-up-indexes-when-using-vm-on-nas/201818/2 "2019-10-01T14:39:52Z")

</div>

I don't really see the relationship between backups and FSCrawler.

The error you pasted here shows that FSCrawler is not able to join an elasticsearch instance. That's why it refuses to start.

---

<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:** [October 29, 2019, 2:51pm UTC](https://discuss.elastic.co/t/problem-backing-up-indexes-when-using-vm-on-nas/201818/3 "2019-10-29T14:51:16Z")

</div>

Closed on October 29, 2019, 2:51pm UTC

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