# Data persistence - Am I going nuts? **URL:** \ **Category:** Rancher 1.x\ **Created:** [August 21, 2017, 9:22pm UTC](https://forums.suse.com/t/data-persistence-am-i-going-nuts/7159 "2017-08-21T21:22:01Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![srcnix](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/srcnix/32/2715_2.png) [@srcnix](https://forums.suse.com/u/srcnix)\ **Post date:** [August 21, 2017, 9:22pm UTC](https://forums.suse.com/t/data-persistence-am-i-going-nuts/7159/1 "2017-08-21T21:22:01Z")
Hi all, Currently using Rancher in Development, looking to go into production in September. It’s a fantastic piece of automation and orchestration software. I have a bit of an issue though! Whenever I upgrade a container, I lose all data stored in named volumes. Why is this? Am I missing something? As an example, I have several database nodes running. I upgraded the entire stack (Forced upgrade for all containers), then all data was lost across the board! Why is this? Should named volumes not be persisted through upgrades? Any and all help is appreciated! ---
**Author:** ![thoth](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/thoth/32/2696_2.png) [@thoth](https://forums.suse.com/u/thoth)\ **Post date:** [August 21, 2017, 10:49pm UTC](https://forums.suse.com/t/data-persistence-am-i-going-nuts/7159/2 "2017-08-21T22:49:16Z")
Are you certain the volumes are gone? I had a similar issue awhile back, but it only happened to rancher/server itself, I upgraded rancherOS and when it came back up it ‘forgot’ my named `rancher-data` container that had my data volumes attached. The volumes were still there they just were not associated with my named `rancher-data` data container (which was missing). I ended up using busybox and just attaching all unused volumes until I found what I was looking for (not that hard in this case as rancher/server was the only thing running on that node), then built a new data volume using `docker create`. Details [here](https://github.com/rancher/os/issues/1981) The first thing you should do is `docker volumes ls` and look through that to see if you can find your data. using something like this: ```auto docker run -v 73c07cf3671:/tmp/test -it busybox /bin/sh # ls /tmp/test ``` ---
**Author:** ![srcnix](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/srcnix/32/2715_2.png) [@srcnix](https://forums.suse.com/u/srcnix)\ **Post date:** [August 22, 2017, 1:34pm UTC](https://forums.suse.com/t/data-persistence-am-i-going-nuts/7159/3 "2017-08-22T13:34:19Z")
Thanks Thoth, turns out the Bitnami Cassandra and Redis info was wrong! Very useful link though! ---
**Author:** ![shubbard343](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@shubbard343](https://forums.suse.com/u/shubbard343)\ **Post date:** [August 22, 2017, 4:52pm UTC](https://forums.suse.com/t/data-persistence-am-i-going-nuts/7159/4 "2017-08-22T16:52:47Z")
Are your volumes on a shared storage like NFS? If not, and the volumes are created on the host itself, then the problem might be that when you upgrade, the new container is started on a different host, and the volume gets created on the new host with no data on it.