My Sympl backup2l cron job is now emailing me to say that there isn’t enough space for a backup:
=> Checking there is enough free space for a backup...
* Free space on /var/backups/localhost: 15.6 GB
* Estimated backup size: 15.6 GB
!! There is not enough space to take a backup. Aborting!
However, using backup2l --estimate /etc/sympl/backup.d/backup2l.conf gives:
That looks to me as though it should only be backing up 333.6 MB, not 15.6 GB.
The regex /\/ (?<int>[0-9]*\.?[0-9]+)(?<suff>[ KMGT]B) \(uncompressed\)$/m in /etc/sympl/backup.d/pre-backup.d//05-check-availspace is selecting the second figure from the output of the estimation command; is that correct?
I’ve found I need significantly more available disk space for the backup than is actually needed in terms of the diff backup as though it’s overestimating the amount required.
That wasn’t too bad in the Bytemark BigV days when the backup storage was on a separate cheaper volume so the size could be bigger without much additional cost.
I raised this question with MB Support a while back:
I have a Synology NAS backing up to archive grade storage discs at
Bytemark which I need to migrate. The data’s about 500Gb before
weeding. I guess the best option would be to setup a low spec Mythic vm
with plenty of backup space and thereafter mount the backup space. I’d
value your advice?
Response from MB Support:
Another option would be to order a low spec HDD-based virtual server, and just backup straight to that. The cost per GB is cheaper than backup space (2p/GBmo vs 8p/GBmo) but this reflects the fact that the backup space is mirrored to two different sites, and we take ZFS snapshots of the data.