Agregar opción para desactivar la compresión de respaldo

Contribuir Característica
21

Note to self:

Recently hit space issues again and backups failing so this post needs revisiting soon.

Note that in order to create a backup resulting in a 12GB gzip file I require ~36GB+ of space dedicated to backups, ~24GB+ of free space:

  • 12GB for the backup from the day before
  • 12GB for the new backup file
  • ~12GB+ tar archive to be compressed into gzip file (original DB file backup + original image files

So as backup sizes increase by 1GB, the backup / space requirements are actually increasing by a ~3GB.

This assumes that you are only keeping a single previous backup - where the Discourse setting maximum backups is set to 1.

The Discourse default is 5, so using defaults I would need ~84GB dedicated to backups to allow them to work.

2 Me gusta
22

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.)

23

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 other Discourse instances that would benefit in the backups being created in a more streamlined way.

2 Me gusta
24

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.

25

¿Cuáles son las opciones actuales de gzip utilizadas para la compresión de las copias de seguridad?

A diferencia de lo que se menciona en el tema, mi interés era ahorrar espacio mediante un método de compresión más eficiente. Realicé algunas pruebas rápidas y poco pulidas comparando nuestro volcado SQL con diferentes niveles de gzip y también con brotli.

2630702226 level1.sql.gz
2276305530 level1.sql.br
2216602536 level5.sql.gz
2147212204 level9.sql.gz
2036157791 level2.br
1851831279 level4.br

Como podemos ver, Brotli nivel 4 supera a Gzip nivel 5 en términos de eficiencia, mientras que el tiempo de compresión fue comparable. El resultado de Brotli nivel 1 no fue nada mal, considerando que es una herramienta extremadamente rápida.

De todos modos, considero que las ganancias del 10 % o más son bastante interesantes.

1 me gusta
26

Interesante, ¿cuáles fueron los tiempos reales de compresión? :thinking:

27

Zopfli será más interesante aquí, ya que es compatible con las herramientas normales de descompresión gzip. Brotli requiere un descompresor diferente.

2 Me gusta
28

zopfli es muy lento, dudo que querramos usarlo para algo como una copia de seguridad gigante. Al menos brotli está algo optimizado para la velocidad.

3 Me gusta
29

nivel de compresión gzip de copia de seguridad para cargas

¿hay alguna forma de desactivar la compresión gzip? dado que mis cargas son principalmente imágenes ya comprimidas, es una pérdida de recursos y tiempo intentar comprimirlas de nuevo.

1 me gusta
30

Del hilo relacionado:

1 me gusta