Proxmox

NFS Mounts

Currently, I a running two independant PVE nodes - an older Gigabyte mini-pc/NUC PC runnnig an 10th Gen i5 4C/4T, and a newer Protectli 6600 series with a newer 10C/12T with 96G ram.

As a result, there are some data that I want to share between the two, like import images and ISOs; and there is some data that I don’t want to be mixed together - mostly backups. If you point two nodes at the same NFS export and have them backup to that mount, you will clobber data. You could do something with VMIDs like putting everything for one in the 1000-1999 range and 2000-2999 range but that’s kinda of a PITA.

The solution I’ve chosen is to have a single shared NFS Mount for imports and templates, and then a dedicated NFS Export for each node.

On my NAS, I have these folders as NFS exports:

  • /volume1/proxmox/ which is the shared export for all nodes. See below for file organization.
  • /volume1/pve-gigabyte is the node specific export to be used for backups and other node specific things
  • /volume1/pve-protectli is node specific export to be used for backups and other node specific things

Hardlinking Files on NAS

On my NAS, I keep all of my ISOs for proxmox in /data/iso for organization, but then have an NFS export under /proxmox for shared storage. Essentially, /proxmox is where I keep iso, qcow2, and vmdk images for mounting inside of my two independant proxmox instances.

These one liners will hardlink to either /import or /template/iso based on the file format.

find /volume1/data/iso/ -type f -name "*.qcow2" -o -name "*.vmdk" | xargs -I % ln --force % /volume1/proxmox/import/

find /volume1/data/iso/ -type f -name "*.iso" | xargs -I % ln --force % /volume1/proxmox/template/iso/

Doug Byrd