All Proxmox VE related storage configuration is stored within a single text
file at /etc/pve/storage.cfg
. As this file is within /etc/pve/
, it
gets automatically distributed to all cluster nodes. So all nodes
share the same storage configuration.
Sharing storage configuration makes perfect sense for shared storage, because the same “shared” storage is accessible from all nodes. But it is also useful for local storage types. In this case such local storage is available on all nodes, but it is physically different and can have totally different content.
Each storage pool has a <type>
, and is uniquely identified by its
<STORAGE_ID>
. A pool configuration looks like this:
<type>: <STORAGE_ID> <property> <value> <property> <value> <property> ...
The <type>: <STORAGE_ID>
line starts the pool definition, which is then
followed by a list of properties. Most properties require a value. Some have
reasonable defaults, in which case you can omit the value.
To be more specific, take a look at the default storage configuration
after installation. It contains one special local storage pool named
local
, which refers to the directory /var/lib/vz
and is always
available. The Proxmox VE installer creates additional storage entries
depending on the storage type chosen at installation time.
Default storage configuration (/etc/pve/storage.cfg
).
dir: local path /var/lib/vz content iso,vztmpl,backup # default image store on LVM based installation lvmthin: local-lvm thinpool data vgname pve content rootdir,images # default image store on ZFS based installation zfspool: local-zfs pool rpool/data sparse content images,rootdir
A few storage properties are common among different storage types.
A storage can support several content types, for example virtual disk images, cdrom iso images, container templates or container root directories. Not all storage types support all content types. One can set this property to select what this storage is used for.
vzdump
).
prune-backups
instead. Maximum number of backup files
per VM. Use 0
for unlimited.
raw|qcow2|vmdk
)
It is not advisable to use the same storage pool on different Proxmox VE clusters. Some storage operation need exclusive access to the storage, so proper locking is required. While this is implemented within a cluster, it does not work between different clusters.