feat: Graceful degradation when remote upload fails #66
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Currently, if remote upload (S3/FTP/GDrive) fails, the entire backup record is marked as failed even though the local archive was created successfully. The backup should be marked as "complete (upload failed)" with a warning, not as a full failure.
Proposed Behavior
completeremote_filename = '', add warning to log, send failure notification for the upload onlyremote_statuscolumn:none,success,failed,pendingWhy
A local backup that exists is infinitely better than no backup. Failing the entire record because S3 credentials expired means the cleanup system may delete the "failed" local file.
Files
src/Engine/BackupEngine.php— separate upload failure from backup failuresrc/Engine/SteppedBackupEngine.php— samesql/updates/mysql/— addremote_statuscolumn