# Use existing named volume from deleted stack

**URL:** <https://forums.suse.com/t/use-existing-named-volume-from-deleted-stack/5530>\
**Category:** Rancher 1.x\
**Created:** [February 15, 2017, 3:35am UTC](https://forums.suse.com/t/use-existing-named-volume-from-deleted-stack/5530 "2017-02-15T03:35:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Domigan](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/chris_domigan/32/2160_2.png) [@Chris\_Domigan](https://forums.suse.com/u/Chris_Domigan)\
**Post date:** [February 15, 2017, 3:35am UTC](https://forums.suse.com/t/use-existing-named-volume-from-deleted-stack/5530/1 "2017-02-15T03:35:28Z")

</div>

Hi there. I understand that named volumes are scoped by stack. I removed a stack, and recreated it, and want to use the existing volume from the previous stack. The volume is still present on the host. Is there a standard way to reuse this volume?

Eg my volume is called “db\_data” in my compose file. My old stack used the volume “staging\_db\_data\_44d01”, but my new one is using “staging\_db\_data\_821da”. I want to go back to the old one instead. (Those are volume names as listed in “docker volume ls” command).

---

<div class="post-metadata">

**Author:** ![Guido\_Steiner](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/guido_steiner/32/5862_2.png) [@Guido\_Steiner](https://forums.suse.com/u/Guido_Steiner)\
**Post date:** [February 15, 2017, 8:13am UTC](https://forums.suse.com/t/use-existing-named-volume-from-deleted-stack/5530/2 "2017-02-15T08:13:31Z")

</div>

Hmm you could use docker volume inspect db\_data and then cd to the path and copy the data to the new docker volume.

---

<div class="post-metadata">

**Author:** ![vthyng](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vthyng/32/2501_2.png) [@vthyng](https://forums.suse.com/u/vthyng)\
**Post date:** [February 15, 2017, 6:57pm UTC](https://forums.suse.com/t/use-existing-named-volume-from-deleted-stack/5530/3 "2017-02-15T18:57:03Z")

</div>

I have a similar challenge. My intended solution is to only use the ‘In Service’ upgrade, and not the ‘Rolling Service’ upgrade so that id will not change. However I am very nervous about that and figure it will likely change at some point. I also plan to run regular database dumps as a normal backup process, and possibly some kind of clustering between containers running at different sites. Oh and one other solution I may use is rancher-nfs mount: [Is it possible to directly map rancher-nfs subfolders as volumes?](http://forums.suse.com/t/is-it-possible-to-directly-map-rancher-nfs-subfolders-as-volumes/5111)