Update: Day 5 of the mystery backup issue
After 4 days of backups appearing to succeed (no errors in the notification centre), the backup finally failed on day 5 with this error:
Jun 07 01:24:44 BoxError: Not enough disk space for backup. Needed: 47.1GB Available: 45.71GB
at runBackupUpload (file:///home/yellowtent/box/src/backuptask.js:192:15)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async uploadAppSnapshot (file:///home/yellowtent/box/src/backuptask.js:359:34)
at async backupAppWithTag (file:///home/yellowtent/box/src/backuptask.js:382:26)
Jun 07 01:24:44 Exiting with code 0
This is confusing because:
The server's local disk has about 60 GB free
I don't see any backup files actually being written to the server itself
So I'm not sure what disk or location this error is even referring to. I need to investigate further, but I'm posting this in case it helps explain what's been going wrong.
Thread summary so far: There seem to be a few possibly related issues:
Missing backups: For one app no backups were created from one day onwards. Though a second identical app was unaffected. Only discovered through a Cloudron restauration
Backup to phantom location: After migrating to a new server, backups to a disconnected external drive kept succeding for 4 days. On day 5, that same location finally failed with a "not enough space" error referencing a disk that doesn't match anything visible on the server.
Unreliable integrity check: Integrity check succeeded for backups which didn't contain the backup of the app in question (prior to restauration). Even on the backups to the phantom location, the integrity check kept succeeding