Can you check if the backup format is correct (i.e tgz or rsync) when you restore from the backups? The logs are in journalctl -u box -a.

Thank you @girish for the refund! Much, much appreciated!

@nebulon Yes I know but I think it's a kind of "dirty intregation" regarding how much you have implemented Amazon/DigitalOcean S3 ... And I'm probably not the only one that need a backup in French Infrastructures. @girish Hum, So bad because it's totally functionnal for me ... I don't know if there is some limitations for others countries.

@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 software should be able to do this http://duplicity.nongnu.org/index.html

I agree this will be a nice feature to have. We will prioritize based on how many people request it. Thanks