Closed rickygarg closed 2 years ago
Ended up implementing this on another repo. Sharing for reference:
https://github.com/getfundwave/s3-mysql-backup-cron/blob/main/backup.sh
@rickygarg oh, nice! Happy to merge this change into this repo if you'd like. Just submit a new PR!
Not an issue, but a feature request.
Before uploading to S3, it is possible to check the md5sum of the last backup using HEAD operation on s3api. If the md5sum doesn't matches the md5sum received, upload new backup with md5sum as a part of the metadata.
Alternately, the same thing could be done locally too, if the last one or two backups aren't deleted from local filesystem immediately on upload.
This would save an incredible amount of storage on S3!