We use a hook script that is defined in /etc/vzdump.conf.
The hook script mounts an encrypted backup disk using cryptsetup.
At the completion of the backup the hook script looks at the size of the backups, the current qty of backups and dynamically changes the maxfiles setting in /etc/vzdump.conf.
This ensures we retain the largest number of backups possible while ensuring there is always enough free space for the next backup without humans needing to constantly monitor free space on dozens of backup disks and manually change maxfiles.
When scheduling backups from the GUI in 2.0 it always passes the maxfiles option overriding the setting in /etc/vzdump.conf.
Would be nice if we could select "default" to prevent the maxfiles option from being explicitly passed so vzdump will use whatever is set in /etc/vzdump.conf.
The hook script mounts an encrypted backup disk using cryptsetup.
At the completion of the backup the hook script looks at the size of the backups, the current qty of backups and dynamically changes the maxfiles setting in /etc/vzdump.conf.
This ensures we retain the largest number of backups possible while ensuring there is always enough free space for the next backup without humans needing to constantly monitor free space on dozens of backup disks and manually change maxfiles.
When scheduling backups from the GUI in 2.0 it always passes the maxfiles option overriding the setting in /etc/vzdump.conf.
Would be nice if we could select "default" to prevent the maxfiles option from being explicitly passed so vzdump will use whatever is set in /etc/vzdump.conf.
Last edited: