PebbleRack

Guide 12 of 25 · intermediate

Choose Proxmox Storage and Decide Whether ZFS Fits

Match guest disks, images, and backups to suitable storage.

Source-verified · Not lab-testedOfficial sources checked 2026-09-29. No PebbleRack hardware compatibility claim.

Outcome

You will have a map that says where VM disks, container volumes, installer images, and backups belong. You will know when to postpone ZFS. No filesystem is universally right for unknown hardware.

Before you start

Inventory physical disks by model, capacity, and serial number. Record existing data and whether you have a tested separate backup. Check RAM, drive health, and growth. The installer erases selected target drives. A ZFS mirror is not a backup: deletion or host loss can affect both members.

Steps

  1. Separate content types. In Datacenter → Storage, inspect existing stores and their allowed content. Proxmox storage types vary in whether they hold VM images, container root directories, ISO files, backups, or templates. Record current stores instead of assuming everything belongs on one disk.
  2. Estimate capacity. Add planned guest disk sizes, snapshots, OS images, and free space for updates. Thin provisioning can initially use less physical storage, but overcommitting can eventually fill the host. Set a threshold for reviewing free space.
  3. Choose a simple first design. For a disposable first host, the installer's default storage may suffice. Proxmox documents directory, LVM-thin, and ZFS backends; each has different allocation and snapshot features. Select a backend for a needed feature.
  4. Evaluate ZFS deliberately. ZFS offers checksumming and useful storage capabilities, but pool layout must be chosen before putting important data on it. Read Proxmox installer ZFS options and performance notes, including memory and drive considerations. Decide whether single-disk risk, mirror capacity loss, or a more complex layout fits your budget. Never create a pool on a disk with data you need; pool creation is destructive.
  5. Place backups separately. Proxmox can send backups to supported storage or a Proxmox Backup Server. A backup only on the same host or pool can disappear with it. Plan an independent destination with enough capacity and a restore path.
  6. Write the storage map. For example, installation and guest disks on the selected local backend, ISO images on a directory store, backups on another device. Replace this with actual store names and retention. Do not count a snapshot as an independently held backup.

Check it worked

You can point to each store in the GUI and state what content it accepts. You know free space and growth headroom. Your plan names an off-host backup destination and restore test.

If it fails or rollback

If a disk's identity or existing contents are ambiguous, stop and do not initialize it. If the capacity plan does not fit, reduce planned guests or add suitable storage. If a store disappears, avoid creating new volumes under its name before identifying the cause and protecting existing data.

Safety and data notes

Formatting and pool creation destroy data. Verify serial numbers, backups, and target selection. Mirroring addresses some drive failures but not deletion, malware, or a failed restore process.

Sources

Official Proxmox pages checked 2026-09-29: storage backends and content types, installer and ZFS options, backup and restore.

Next guide

Continue with guide 13 to build a small test VM on the chosen guest-disk store.