@malvim said in Backup Improvements: Restic Backend:
@necrevistonnezr how have you been testing backups? I have a raspberry pi at home, set up with restic/rclone backups as well. Once in a while I mount one of the latest snapshots and check a bit randomly if things "look ok". I'd like to have a better system to check if backups are okay, so any pointers would be appreciated.
https://restic.readthedocs.io/en/latest/045_working_with_repos.html#checking-integrity-and-consistency
and, as I said, spot checks for files with restic-browser.
@d19dotca Thanks for the write up, I will repurpose it for some our docs.
Another user had actually informed us about this and it's been working reliably for them. So, we already had added OVH storage in the backups UI for the next release.
[image: 1588704852591-357c53be-e4aa-4bcc-8cac-b8d7d543e388-image-resized.png]
@girish thanks for the info and extra-feature, that's good to know and might come in handy! I'll also tell people not to use that long filenames to avoid such errors.
Maybe we could at least introduce an optimization of the databases from time to time. The size of the referenced "ttrss_entries" table went from an insane 1,238 MB (!) to 583 MB after optimization.
The following command, maybe via a button, should to the trick:
mysqlcheck -Aos --user=${MYSQL_USERNAME} --password=${MYSQL_PASSWORD} --host=${MYSQL_HOST};
@girish I also realized that the mysqldump for the TT-RSS app is huge (679 MB in my case). Could you implement some compession in the database dumps (and use PostgreSQL as recommended by the author)?
This would go well with a secondary backup facility for all things Cloudron doesn't currently back up, which is valuable, such as Volumes.
Add a few protocols for this such as FTPS, SFTP, RCLONE, RSYNC, etc..
