# Full restore process **URL:** \ **Category:** Elasticsearch\ **Created:** [September 8, 2016, 7:35pm UTC](https://discuss.elastic.co/t/full-restore-process/60110 "2016-09-08T19:35:48Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![newelasticuser](https://avatars.discourse-cdn.com/v4/letter/n/50afbb/32.png) [@newelasticuser](https://discuss.elastic.co/u/newelasticuser)\ **Post date:** [September 8, 2016, 7:35pm UTC](https://discuss.elastic.co/t/full-restore-process/60110/1 "2016-09-08T19:35:48Z")
How full restore is done using the SNAPSHOT api if snapshot is done incrementally? Is NAS recommended for the backup repository or it can be any FS NFS mount? ---
**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\ **Post date:** [September 9, 2016, 3:44am UTC](https://discuss.elastic.co/t/full-restore-process/60110/2 "2016-09-09T03:44:59Z")
A snapshot being incremental means that it will only copy the segments that have changed, for the segments that have not changed, a pointer to the old (already backed up) segments will suffice. For a full backup then, it means copying the unique segments from a snapshot as well as resolving the pointers to any other segment files when copying the data from the repository back to the index location. > Is NAS recommended for the backup repository or it can be any FS NFS mount? NAS is recommended only because it is an easy way to have a mount point that is accessible from all nodes in the cluster. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:21pm UTC](https://discuss.elastic.co/t/full-restore-process/60110/3 "2017-07-05T22:21:42Z")
Closed on July 5, 2017, 10:21pm UTC