Setting Up Proxmox Storage

What This Article Covers

• Storage types supported by Proxmox.
• When to choose LVM, ZFS, Ceph, NFS, or iSCSI.
• How to configure storage in Proxmox.
• Where backups, ISOs, containers, and VMs are stored.
• Common pitfalls and best practices.

Introduction: Setting Up Proxmox Storage

Storage is central to any Proxmox deployment. Your choice of storage technology affects performance, flexibility, redundancy, and backup strategies. Proxmox supports various solutions: local disks with LVM or ZFS, network storage via NFS or iSCSI, and distributed systems like Ceph. Selecting the right approach for your needs prevents bottlenecks and data loss later on.

This article explains the most common storage types in Proxmox and when each makes sense.

Key Terms

• Storage: Space for VMs, LXC containers, ISOs, backups, and templates.
• LVM: Logical Volume Manager, a classic Linux storage tool.
• LVM-Thin: Thin-provisioned volumes that enable snapshots.
• ZFS: Modern filesystem with integrated RAID and snapshots.
• Ceph: Distributed storage system for clusters.
• NFS: Network filesystem.
• iSCSI: Block storage over TCP/IP.
• Pool: Aggregation of multiple storage devices.

Local Storage Types

LVM and LVM-Thin

LVM is the standard in many Proxmox installations. It provides logical volumes that can be managed flexibly. LVM-Thin uses thin provisioning, meaning space is allocated only when needed. Snapshots are fast and storage-efficient.

ZFS

ZFS outperforms LVM and offers:

• Integrated RAID (RAID-Z).
• Checksums against data corruption.
• Snapshots and replication.
• Compression.
• High stability.

Drawbacks:

• Higher RAM consumption.
• Not freely mixable with other filesystems.
• Steep learning curve.

Directory

Simple directory-based storage on any filesystem. Good for ISOs, backups, or templates, but unsuitable for VM disks since snapshots are not supported.

Network Storage

NFS

NFS is straightforward to set up and works well for:

• Backups
• ISOs and templates
• Shared data

Performance is often inadequate for VM disks.

iSCSI

iSCSI provides block storage over the network. It’s better suited for VM disks than NFS, but requires an iSCSI target like TrueNAS or Synology.

Ceph

Ceph is a distributed storage system for Proxmox clusters. It provides high availability and scalability, though it’s complex and requires at least three nodes.

Adding Storage

In the Proxmox GUI:

1. Select Datacenter.
2. Select Storage.
3. Click Add.
4. Choose a type (ZFS, LVM, NFS, etc.).
5. Enter parameters.
6. Add the storage.

Assigning Content Types

Each storage can be enabled for specific content:

• VM Disks: Virtual machine hard drives.
• CT Volumes: Container volumes.
• ISO Images: Installation media.
• Container Templates: LXC templates.
• VZDump backup files: Proxmox backups.
• Snippets: Custom scripts.

ZFS on Proxmox

Creating a Pool

zpool create tank /dev/disk/by-id/ata-wwn-... -f

Should I Use RAID-Z1?

RAID-Z1 is roughly equivalent to RAID 5 and tolerates one device failure. For critical data, RAID-Z2 or RAID-Z3 is safer.

Adding Storage

Add it in the GUI as ZFS and specify the pool name.

Storing Backups Correctly

Backups should live on separate storage. Options include:

• External USB drive.
• NFS on a NAS.
• Proxmox Backup Server.
• CIFS/SMB share.

Storage Capacity Planning

Example for a small setup:

Content	Storage	Recommendation
VM Disks	LVM-Thin or ZFS	fast, snapshots
LXC	LVM-Thin or ZFS	fast, snapshots
Backups	NFS or PBS	external
ISOs	Directory or NFS	low overhead

Common Pitfalls

• ZFS consumes significant RAM: Without enough RAM, performance degrades.
• Overprovisioning LVM-Thin: Don’t allocate more space than physically available.
• Backups on the same storage: No protection if the storage fails.
• Wrong disk ID: Disks can be reordered; prefer by-id.
• Network storage too slow: NFS is often unsuitable for VM disks.

Further Reading and Resources

• BotServ.de Proxmox Basics
• BotServ.de Proxmox Backups and Restore
• BotServ.de Proxmox LXC vs. VM
• BotServ.de NAS

FAQ: Proxmox Storage

Which is better, LVM or ZFS? ZFS offers more features but requires more RAM. LVM-Thin is sufficient for simple setups.

Can I store backups on NFS? Yes, it’s a common and straightforward approach.

Do I need Ceph? Only for clusters with multiple nodes and high-availability requirements.

How much RAM does ZFS need? At least 8 GB, preferably 16 GB or more depending on pool size.

What happens with LVM-Thin when storage is full? All volumes based on it can fail. Monitor your available space.

Sources and Further Reading

• Proxmox Storage Wiki: https://pve.proxmox.com/wiki/Storage
• OpenZFS: https://openzfs.org/
• Proxmox Backup Server: https://pbs.proxmox.com/

Summary: Setting Up Proxmox Storage

Choosing the right Proxmox storage depends on budget, performance needs, and availability requirements. LVM-Thin and ZFS are ideal for local VM and LXC disks, while NFS and PBS suit backups and ISOs. ZFS offers more features but consumes more RAM. What matters most is keeping production data and backups on separate storage systems. Pay attention to proper disk IDs, adequate capacity, and regular backups, and you’ll build a solid storage foundation for your homelab.