Thanks for getting back to me, apologies for not including obvious details like version. We’re on v2.3.1 +12 right now (stable channel, I think). 2019-07-03→2019-07-06 could’ve easily covered a period where we updated and some backup logic was changed. Uploads are stored locally (as our forum is pretty tiny as you can see).
Fab idea to look inside the backups. Here’s where the size difference presents itself:
% du -sh forum-190703/uploads/default/* | sort -h | tail -n 6
508K forum-190703/uploads/default/25
780K forum-190703/uploads/default/1
1.6M forum-190703/uploads/default/avatars
2.9M forum-190703/uploads/default/_optimized
86M forum-190703/uploads/default/optimized
120M forum-190703/uploads/default/original
% du -sh forum-190706/uploads/default/* | sort -h | tail -n 6
488K forum-190706/uploads/default/103
508K forum-190706/uploads/default/25
776K forum-190706/uploads/default/1
1.6M forum-190706/uploads/default/avatars
2.9M forum-190706/uploads/default/_optimized
120M forum-190706/uploads/default/original
So it’s the entire optimized
directory that disappears. I’m assuming this is all intentional to save on backup size, especially after finding this commit, so all seems good. Thanks.