smarter calculation of PI Backup required free space
When backfilling tags from AF its very easy to update many archives. I would like the backup script to only require free space for archives that don't exist in the target folder. We have periodic incremental backup failures do to a lack of free disk space, even though almost all of the archives being backuped up will replace files that already exist in the target folder
We have the same issue when AF backfills many archives. The precommit folder becomes too large for the available backup disk space and we have to do multiple manual backups increasing the numarch parameter for each backup to accomplish this. We basically look at archive size and available disk space on backup drive and determine how much to increase numarch with each manual backup. Would like the backup utility to somehow automatically accomplish the same thing.
Kenneth Barber commented
I also encountered this issue. It seems that PI backs up the archives first and then deletes any corresponding older backups, or at least, that is what the free-space check would suggest. If you don't have enough space for all of the archives that will be backed up, the backup fails. The older backup archives that will be replaced as part of the backup are not counted towards the free space, but they should be.
There are complexities associated with this idea in that we would need to know the content of the archives both from the source and also destination. Did I understand your request correctly?