So here’s a strange problem. On our servers, we’ve been having issues with the backups’ ‘delete after runs’ setting. We’re on 22.214.171.124, with backup module 126.96.36.199. We have one older backup from v14 in the local storage location.
Below is what happened when I set it to one run. On analysis, the backup deleted itself after finishing. After copying this log, I set it to 0 runs and the system saved the backup to the ASTSPOOLDIR/backup location, which I believe is the error location. Then I set it to 3 runs, and it saved in the right location. So I set it to 2 runs, and it deleted the older v15 file, as if it had 2 runs already. I set it back to 3, and it created a new backup.
My conclusion is that the backups check the filestore location for how many backups have been run, and then deletes the oldest v15 backup, even if it’s the one it just created. Has anybody had a similar issue with this, or was it just me for not deleting those old backups?
End of Backup Logs:
Finished Cleaning up
Finished created backup file: 20210907-135655-1631048215-188.8.131.52-1250419961.tar.gz
Performing Local Maintenance
Finished Local Maintenance
Performing Remote Maintenance
Finished Remote Maintenance
Saving to selected Filestore locations
Finished Saving to selected Filestore locations
There were warnings during the backup process
The module callback returned no data, No backup created
The module callerid returned no data, No backup created
The module calllimit returned no data, No backup created
The module conferencespro returned no data, No backup created
The module miscdests returned no data, No backup created
The module phonebook returned no data, No backup created
The module setcid returned no data, No backup created