Skip to main content

Proxmox VE 9 introduces external QCOW2 snapshots on thick-provisioned LVM volumes over SAN (including FC and iSCSI). There is already an updated plugin, that supports not only this version but also those specific snapshots.

@Iams3le already gave insight about the installation of the new plugin: Veeam Plug-in for Proxmox VE v12.1.5.17 update to Support Proxmox VE 9.0 | Veeam Community Resource Hub

Now, using a shared FC (or iSCSI) SAN is possible just like we did with VMware - while still being able to generate nice Veeam backups of the VMs on the LUNs: Plug-in for Proxmox VE v12.1.5.17 -> shared LVM? - R&D Forums

 

Here's the breakdown:

  • QCOW2 is required for snapshot functionality on SAN LUNs.
  • Snapshots are implemented as external overlays (not internal QCOW2 snapshots).
  • Each snapshot creates a new logical volume to store delta data.
  • This allows rollback and versioning, even on raw block devices like FC LUNs.

[TUTORIAL] - Inside Proxmox VE 9 SAN Snapshot Support | Proxmox Support Forum

 

⚠️ Limitations to Keep in Mind

  • Performance impact: QCOW2 introduces overhead—up to 30–90% degradation compared to raw disks.
  • Thick provisioning required: You must allocate full-size LVM volumes for both base and snapshot images.
  • No linked clones: You can't create linked clones from templates using this method.
  • Snapshot deletion can increase usage: Merging overlay data may defeat SAN thin provisioning.
  • TPM support is limited: Snapshots of VMs using TPM are not supported.
  • Not production-ready: This feature is currently a technology preview.

Let’s hope for the feature to become ready for production on the Proxmox side and also to get rid of the high performance impact it seems to suffer currently.

Not great hearing that performance is an issue but hopefully it will get resolved.  👍


Nice to hear about progress being made, but obviously not anything to consider for prod. But good to know..thanks for sharing Michael. Really appreciate it!