Skip to content

Proxmox storage management

Storage & Backups > Storage is the storage management page for the Proxmox VE datacenter storage configuration of a connection (one node, or a whole cluster). It edits the same storage list you see under Datacenter > Storage in Proxmox. To see a single node’s storages and their usage, use the Storage tab on the node page instead.

Pick the connection in the selector at the top. The table lists its storages with Storage (the ID), Type, Content, Nodes, Enabled and Target (the directory path, or server and export or share), read live from Proxmox. Use the search box to filter it.

  1. Click Add storage.
  2. Enter a Storage ID (lowercase letters, digits, ., _ and -) and pick the Type:
    • DIR: a local Directory path (absolute, for example /srv/storage).
    • NFS: the NFS server and Export (for example /exports/data).
    • SMB / CIFS: the SMB server, Share, Username and optional Password.
  3. Tick at least one of the Content types: images, iso, vztmpl, backup, snippets, rootdir.
  4. Optionally Restrict to nodes (comma-separated node names, for example node1,node2) and set Enabled.
  5. Click Add storage.

Edit changes only the content types, the node restriction and whether the storage is enabled. The ID, type and connection details can’t be changed; remove and re-add the storage instead.

Remove asks you to type the storage ID to confirm.

The content types decide what Proxmox may store on a storage:

Content typeHolds
imagesQEMU virtual machine disks.
rootdirLXC container root and mount point volumes.
isoISO images for installing an operating system by hand.
vztmplLXC container templates.
backupvzdump backup files.
snippetsCloud-init snippets, such as the guest-agent snippet NexoVirt adds to new VMs.

A storage that should host new guests needs images for VMs and rootdir for containers.

During onboarding the node agent creates its own nexovirt-images directory storage at /var/lib/nexovirt/images on each node. It holds the cached cloud images that new VMs are imported from. It appears in this list like any other storage; leave it in place, or QEMU guest creation on that node stops working until the agent is set up again.

The page is admin-only; adding, editing and removing storages require permission to change settings. Every change is recorded in the audit log (storage.create, storage.update, storage.delete).