What is the lion’s share of the backup? I assume uploaded images and so on? Wouldn’t it be easier to specify the backup is database-only, and thus make it a tiny fraction of the overall size?
(Yes, we’d still need some way to back up the images independently, but at least then the urgent need for 100GB+ of space would not be present.)
Yes the lions share of the backup content is “uploads”.
However a backup is not complete without the “uploads”.
My personal target is to move the images / “uploads” to Amazon S3 to avoid this issue for this specific instance, however there is still some testing to be done on a high topic / post count instance before I can trust the migration to S3, some issues already highlighted in that thread (more specifically avoiding a rebake of all posts).
I have the same problem as this thread, I have many GB of images and while I want to migrate them to S3 from what I have read the migration script seems a bit buggy still. So, I still have images locally but am running out of disk space given the high ceiling needed to allow a backup. Even if I could delete the old backup before creating the new one it would be OK for me. In fact I have been doing that manually.
Note that the backup system also seems to be failing me on the free disk space calculation, it will fill up the whole disk before giving up, and not even delete the partial files. Then the whole computer gets unhappy. There should be a calculation to not do a backup if there is no disk space for it, taking into account the space needed for the compression etc.
Edit: I am going to run a cron job which will delete the (sole) local backup every day. That should solve my immediate problem, but I think it would also be nice to have an option to immediately delete any (local) backup that was already successfully copied to S3.
Quais são as opções atuais do gzip usadas para a compressão dos backups?
Ao contrário do que foi discutido no tópico, meu interesse era economizar espaço utilizando um método de compressão mais eficiente. Fiz alguns testes rápidos e não tão refinados comparando nosso dump SQL com diferentes níveis do gzip e também o brotli.
Como podemos ver, o Brotli nível 4 supera o Gzip nível 5 em termos de eficiência, enquanto o tempo de compressão ficou na mesma faixa. O resultado do Brotli nível 1 não foi ruim, considerando que é uma ferramenta extremamente rápida.
De qualquer forma, acho ganhos de 10% ou mais bastante interessantes.
O Zopfli é assustadoramente lento; duvido que quiséssemos usá-lo para algo como um backup gigante. Pelo menos o Brotli é um pouco otimizado para velocidade.
nível de compactação gzip de backup para uploads
há alguma forma de desativar a compactação gzip. como meus uploads são principalmente imagens já compactadas, é um desperdício de recursos e tempo tentar compactá-los novamente.