Clustering and local storage misunderstanding


Mar 9, 2021
I started playing with clustering and my goal is to replicate vms from one node to another while keeping the replicated vm shutdown until needed. No HA here for now. I understand that NFS / ISCSI accessible storages might be required to do so but I'm not there yet since both nodes are using local ZFS storages. What I don't understand at this point is how the local storages are represented in the gui and generated.
For some reason, some local storages from node1 are also represented in node2 (USB_backup for exemple). This is a bit confusing and I made sure the "share" checkbox wasn't enabled when adding that storage. So, why when creating a new storage without checking the shared button will create the "equivalent" storage (and directory structure) in the second node ?
The case of the USB_BACKUPS storage is a directory storage mounted on /backup in node1 where I mount an external disk to make some vm backups.
Is there anyway to create directory storage that will be only visible from one node ?


Proxmox Staff Member
Staff member
Aug 1, 2019
this is because often you'll have a storage with the same settings on different nodes, e.g. required for ZFS replication. If a storage is not available on all nodes, use the Nodes option to restrict it. Enabled shared means that Proxmox VE treats the storage as shared, but it's up to you to ensure that it's actually shared (e.g. useful when a directory resides on a network mount).
  • Like
Reactions: tlex


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!