# 1.3.2 snapshot file system question

**URL:** <https://discuss.elastic.co/t/1-3-2-snapshot-file-system-question/21486>\
**Category:** Elasticsearch\
**Created:** [January 5, 2015, 3:40pm UTC](https://discuss.elastic.co/t/1-3-2-snapshot-file-system-question/21486 "2015-01-05T15:40:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bitsofinfo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bitsofinfo/32/459_2.png) [@bitsofinfo](https://discuss.elastic.co/u/bitsofinfo)\
**Post date:** [January 5, 2015, 3:40pm UTC](https://discuss.elastic.co/t/1-3-2-snapshot-file-system-question/21486/1 "2015-01-05T15:40:02Z")

</div>

I have a cluster (1.3.2) of 10 data nodes and 5 master nodes.

I want to take a snapshot of one index.

I'd like to configure a new "fs" snapshot "mybackupdir" where the  
"location" is ONLY accessible from the node (master node) I am issuing the  
snapshot creation PUT against.

Next, if I issue a snapshot PUT for "mybackupdir/backup1" against the  
master node where that location is indeed accessible, will this work? Does  
the node that gets the snapshot request pull all the shard data from the  
data nodes over to itself and write them to the snapshot dir on disk? Or  
does each data-node responsible for each shard attempt to write to that  
same location? (thereby requiring that the snapshot "location" be  
accessible by all 15 nodes...)

I ask this because I have a cluster that spans two data-centers and they  
don't all have access to a globally available NFS share where I could have  
a common mount path for the snapshots root

thanks

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1b2274d3-304d-4470-8cda-f9462c831aad%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1b2274d3-304d-4470-8cda-f9462c831aad%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**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:** [January 5, 2015, 8:07pm UTC](https://discuss.elastic.co/t/1-3-2-snapshot-file-system-question/21486/2 "2015-01-05T20:07:31Z")

</div>

It won't work, the snapshot is run against any node that has shards of the  
index and doesn't funnel data back to the node you ran the command on.

On 6 January 2015 at 02:40, [bitsofinfo.g@gmail.com](mailto:bitsofinfo.g@gmail.com) wrote:

> I have a cluster (1.3.2) of 10 data nodes and 5 master nodes.
> 
> I want to take a snapshot of one index.
> 
> I'd like to configure a new "fs" snapshot "mybackupdir" where the  
> "location" is ONLY accessible from the node (master node) I am issuing the  
> snapshot creation PUT against.
> 
> Next, if I issue a snapshot PUT for "mybackupdir/backup1" against the  
> master node where that location is indeed accessible, will this work? Does  
> the node that gets the snapshot request pull all the shard data from the  
> data nodes over to itself and write them to the snapshot dir on disk? Or  
> does each data-node responsible for each shard attempt to write to that  
> same location? (thereby requiring that the snapshot "location" be  
> accessible by all 15 nodes...)
> 
> I ask this because I have a cluster that spans two data-centers and they  
> don't all have access to a globally available NFS share where I could have  
> a common mount path for the snapshots root
> 
> thanks
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/1b2274d3-304d-4470-8cda-f9462c831aad%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1b2274d3-304d-4470-8cda-f9462c831aad%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/1b2274d3-304d-4470-8cda-f9462c831aad%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1b2274d3-304d-4470-8cda-f9462c831aad%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8h2LV0OSWmEwYZ\_SAF7t41k4G00\_p6\_9XVw3SVLk5n\_w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8h2LV0OSWmEwYZ_SAF7t41k4G00_p6_9XVw3SVLk5n_w%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![bitsofinfo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bitsofinfo/32/459_2.png) [@bitsofinfo](https://discuss.elastic.co/u/bitsofinfo)\
**Post date:** [June 1, 2015, 2:28pm UTC](https://discuss.elastic.co/t/1-3-2-snapshot-file-system-question/21486/3 "2015-06-01T14:28:55Z")

</div>

in case anyone else comes across this, I ended up making this to assist w/  
my issue of aggregating fs snapshots

> **[GitHub - bitsofinfo/elasticsearch-snapshot-manager: Scala tool for managing elasticsearch snapshots....](https://github.com/bitsofinfo/elasticsearch-snapshot-manager)**
>
> Scala tool for managing elasticsearch snapshots. In particular aggregating and backing up snapshots files from fs local-disk snapshot repositories distributed across a large cluster.

On Monday, January 5, 2015 at 1:08:05 PM UTC-7, Mark Walkom wrote:

> It won't work, the snapshot is run against any node that has shards of the  
> index and doesn't funnel data back to the node you ran the command on.
> 
> On 6 January 2015 at 02:40, \<[bitsof...@gmail.com](mailto:bitsof...@gmail.com) \<javascript:\>\> wrote:
> 
> > I have a cluster (1.3.2) of 10 data nodes and 5 master nodes.
> > 
> > I want to take a snapshot of one index.
> > 
> > I'd like to configure a new "fs" snapshot "mybackupdir" where the  
> > "location" is ONLY accessible from the node (master node) I am issuing the  
> > snapshot creation PUT against.
> > 
> > Next, if I issue a snapshot PUT for "mybackupdir/backup1" against the  
> > master node where that location is indeed accessible, will this work? Does  
> > the node that gets the snapshot request pull all the shard data from the  
> > data nodes over to itself and write them to the snapshot dir on disk? Or  
> > does each data-node responsible for each shard attempt to write to that  
> > same location? (thereby requiring that the snapshot "location" be  
> > accessible by all 15 nodes...)
> > 
> > I ask this because I have a cluster that spans two data-centers and they  
> > don't all have access to a globally available NFS share where I could have  
> > a common mount path for the snapshots root
> > 
> > thanks
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/1b2274d3-304d-4470-8cda-f9462c831aad%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1b2274d3-304d-4470-8cda-f9462c831aad%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/1b2274d3-304d-4470-8cda-f9462c831aad%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1b2274d3-304d-4470-8cda-f9462c831aad%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/)

You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/359543f4-89c7-4194-8ac1-d6c26fdbdffa%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/359543f4-89c7-4194-8ac1-d6c26fdbdffa%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 12:10am UTC](https://discuss.elastic.co/t/1-3-2-snapshot-file-system-question/21486/4 "2017-07-06T00:10:28Z")

</div>


