I really don’t think it’s worth nickel and diming space.
All this will fill up again.
Address the bigger issue; you’ve outgrown this sever.
Spin up a bigger one and migrate asap.
Recover this server only to create or move a backup file.
4 Likes
Possibly, but if the server has never had a ./launcher cleanup then it could be old images jamming the place up. It seems like it was created from a one-click install, so may have skipped the server maintenance section of the standard install.
I’d quite like to see the output of docker images to confirm, but if there’s an orphaned one in there that’s prime for removal, and that frees up enough space to get it back online and on the right maintenance track, that should give a clearer picture.
But you’re right, resizing may be simpler.
4 Likes
You are right that’s worth a try.
You could also consider moving to another server of equal size to resolve the local issue.
2 Likes
I also suspect 5 full backups of an “upload intensive” forum (but that would also be good news, the existence of full backups 
)
2 Likes
5 is arguably excessive, 3 is probably good enough?
3 Likes
I think I followed your advice about that actually, or maybe it was Jay, I kept 5 by default but only because I’ve got room to spare on s3, I’ve set the frequency to every two days (that was after the ovh’s datacenter fire) and backup with uploads is on by default.
In that case, with 5Go uploads, that would amount to 25+ for backups + maybe a system a little bloated, that’s almost 50G probably
2 Likes
Hi @danielabc 
Your forum seems to be working again at least, so you must be doing something right. 
4 Likes