I saw a report in a Proxmox user group from a colleague who encountered a critical issue:
During a backup job targeting a CIFS-mounted storage on Proxmox, the remote storage reached 100% usage. As a result, Proxmox froze, the backup failed, and even some VMs became unstable or froze due to the full mount point.
According to him, the job is configured with a retention policy (Keep Last: 3), but it seems Proxmox tries to write the new backup before removing the old ones — which causes the failure if the storage is already at its limit.
My questions are:
Any guidance to help prevent this kind of situation would be greatly appreciated.
During a backup job targeting a CIFS-mounted storage on Proxmox, the remote storage reached 100% usage. As a result, Proxmox froze, the backup failed, and even some VMs became unstable or froze due to the full mount point.
According to him, the job is configured with a retention policy (Keep Last: 3), but it seems Proxmox tries to write the new backup before removing the old ones — which causes the failure if the storage is already at its limit.
My questions are:
- Is there a native way for Proxmox to check available space on the CIFS target before starting the backup?
- Is it possible to configure it to delete old backups before writing new ones?
- Any best practices for dealing with this kind of scenario when space is limited?
Any guidance to help prevent this kind of situation would be greatly appreciated.