# Moving Snaps to another disk

**URL:** <https://discuss.elastic.co/t/moving-snaps-to-another-disk/147275>\
**Category:** Elasticsearch\
**Created:** [September 4, 2018, 9:16pm UTC](https://discuss.elastic.co/t/moving-snaps-to-another-disk/147275 "2018-09-04T21:16:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeffharper](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@jeffharper](https://discuss.elastic.co/u/jeffharper)\
**Post date:** [September 4, 2018, 9:16pm UTC](https://discuss.elastic.co/t/moving-snaps-to-another-disk/147275/1 "2018-09-04T21:16:44Z")

</div>

I'm trying to move our snapshots to a new larger drive.  
I've mounted both drives, and I stopped the curator job that creates new snapshots.

I'm using "rsync -av /oldmount/logstash\_snaps /newmount" to copy the files, and initial checks show it is creating the same structure, preserving owner/perms/times etc.

The job has been running for a while, and has now copied more data than is on the source drive.

Should this process work, or is there a better way to move the snapshots to another disk?

Cheers,  
Jeff

---

<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 2, 2018, 9:16pm UTC](https://discuss.elastic.co/t/moving-snaps-to-another-disk/147275/2 "2018-10-02T21:16:50Z")

</div>

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