When a backup to S3 runs nightly, it pretty much requires that the disk size be at least 2x the space used. On my 200GB disk, Discourse uses about 50% and during the backup, disk use jumps to just over 90% until the backup is uploaded to S3. [backups takong up disk space] I’m curious if there is …

There was a plan: Reduce local disk space needs by not (redundantly) gzipping backups [imagen] Reduce local disk space needs by not (redundantly) gzipping backups Development of that feature is currently paused and it isn’t on our current roadmap. I hope we will get to it in 2024.

La copia de seguridad requiere 2 veces el espacio en disco. ¿Se podría mejorar el proceso?

Soporte

Ed_S (Ed S) 14 Agosto, 2025 07:51 2

Había un plan:
Reducir las necesidades de espacio en disco local al no (redundantemente) comprimir las copias de seguridad con gzip

Tema		Respuestas	Vistas
Better auto-backup options Feature backups , s3	4	2048	4 Diciembre 2025
How can I tell how much disk space might would be needed for an auto backup? Self-hosting server-resources	0	493	23 Julio 2020
'Download remote images to local' disabled despite enough free disk space Support	3	73	23 Agosto 2025
Discourse not respecting the number of S3 backups to keep Self-hosting backups , s3	8	962	10 Abril 2024
Does using S3 for uploads mean redownloading all files when creating backups? Support	7	1292	13 Septiembre 2020

La copia de seguridad requiere 2 veces el espacio en disco. ¿Se podría mejorar el proceso?

Temas relacionados