Hello,
just to notify that the [Case #07827586 — Issue with Recovery Points / Snapshots on Nutanix cluster with Veeam] is still open but with no solution at the moment.
VBR (VBAHV v7) leaves the VG Snapshot expiration period undefined; in this case AOS forcibly marks an expiration period of 60 days; Nutanix's usual cleanup activities then delete VG snapshots older than 60 days.
IMHO, VBR should "mark" these VG Snapshots with a very low retention period and not with an undefined one.
My problem is that if a VM, that uses a VG as storage, daily changes many blocks, I will have 60 huge VG snapshots, with the result that the space used by VG snapshots is far more (600% at the moment) the space provisioned by the VM itself.
In my case this implies that now my cluster can not afford a node fail due to the significant space taken up by the 60 VG snapshots for each VG on the main Storage Pool.
Stay tuned
PAP400
just to notify that the [Case #07827586 — Issue with Recovery Points / Snapshots on Nutanix cluster with Veeam] is still open but with no solution at the moment.
VBR (VBAHV v7) leaves the VG Snapshot expiration period undefined; in this case AOS forcibly marks an expiration period of 60 days; Nutanix's usual cleanup activities then delete VG snapshots older than 60 days.
IMHO, VBR should "mark" these VG Snapshots with a very low retention period and not with an undefined one.
My problem is that if a VM, that uses a VG as storage, daily changes many blocks, I will have 60 huge VG snapshots, with the result that the space used by VG snapshots is far more (600% at the moment) the space provisioned by the VM itself.
In my case this implies that now my cluster can not afford a node fail due to the significant space taken up by the 60 VG snapshots for each VG on the main Storage Pool.
Stay tuned
PAP400
Statistics: Posted by PAP400 — Oct 07, 2025 12:55 pm
