# Best practices for (distributed) storage with multiple projects/environments **URL:** \ **Category:** Rancher 1.x\ **Created:** [February 25, 2016, 9:59am UTC](https://forums.suse.com/t/best-practices-for-distributed-storage-with-multiple-projects-environments/1856 "2016-02-25T09:59:16Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![johan](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@johan](https://forums.suse.com/u/johan)\ **Post date:** [February 25, 2016, 9:59am UTC](https://forums.suse.com/t/best-practices-for-distributed-storage-with-multiple-projects-environments/1856/1 "2016-02-25T09:59:16Z")
Hey, I am currently trying to set up a Rancher environment for our organization. There are multiple projects that want to make use of Rancher, and I would like to seperate these projects using environments, so that they cannot stop/control containers of others. I believe it is a good practice to set up a Rancher host for each project, since you can access all stacks that run on a single host. Data that is stored in volumes should be backed up or replicated. I was thinking about one of the following approaches: - Projects store their container data in volumes on their own Rancher host. We would however need a solution to backup these volumes. - We could use a distributed storage solution such as GlusterFS. I have tried to set up a GlusterFS cluster using Rancher on three machines. However, I found out that a GlusterFS/Convoy service cannot be shared across multiple environments. What would be the best approach to this? Best regards, Johan ---
**Author:** ![johan](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@johan](https://forums.suse.com/u/johan)\ **Post date:** [March 2, 2016, 9:44am UTC](https://forums.suse.com/t/best-practices-for-distributed-storage-with-multiple-projects-environments/1856/2 "2016-03-02T09:44:26Z")
Would still appreciate some tips! 🙂