# Deprecating path.data volume, preserving closed indices **URL:** \ **Category:** Elasticsearch\ **Created:** [March 1, 2018, 4:29pm UTC](https://discuss.elastic.co/t/deprecating-path-data-volume-preserving-closed-indices/122120 "2018-03-01T16:29:07Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![excalq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/excalq/32/20924_2.png) [@excalq](https://discuss.elastic.co/u/excalq)\ **Post date:** [March 1, 2018, 4:29pm UTC](https://discuss.elastic.co/t/deprecating-path-data-volume-preserving-closed-indices/122120/1 "2018-03-01T16:29:07Z")
I have an ES node, which has temporarily attached EBS volumes belonging to our former cluster which went down due to operator error. Attaching these EBS volumes, and adding them to `path.data` has allowed fairly easy reallocation to the other nodes of the cluster, so that I can decommission these older, slower (st1) EBS volumes. The issue that I have now is that there are about 700 closed indices (all log data from months ago). I've tried opening a small set of closed indices at a time, and letting it reallocate. This caused the cluster to be "red" for too long. That at doing this process x700, x100, etc. would not be fun. Maybe someone has a better suggestion how how to handle this? Perhaps I should manually copy these indices deep directories in the filesystem to the newer node's SSD volumes and restart the ES node? Tell me if this is a terrible idea or not! ---
**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, 4:29pm UTC](https://discuss.elastic.co/t/deprecating-path-data-volume-preserving-closed-indices/122120/2 "2018-03-29T16:29:25Z")
Closed on March 29, 2018, 4:29pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.