Ubicación de copia de seguridad

[gerhard (Gerhard Schlager)]

Hace unos días añadimos una nueva función que te permite seleccionar dónde se almacenan las copias de seguridad. La nueva configuración del sitio se llama backup_location y actualmente admite “Local” y “Amazon S3”.

La configuración predeterminada es “Local”, a menos que hayas configurado previamente enable_s3_backups para cargar automáticamente las copias de seguridad a S3.

¿Qué ha cambiado?

Hasta ahora, las copias de seguridad siempre se almacenaban en el disco local del servidor; cargar las copias de seguridad a S3 era solo un paso adicional y opcional al final del proceso de copia de seguridad. Con la nueva configuración, puedes elegir almacenar las copias de seguridad ya sea localmente o en S3. El almacenamiento local se utilizará solo para archivos temporales durante las copias de seguridad y las restauraciones si seleccionas S3.

Además, la pestaña Backups ahora funciona igual para cualquier ubicación de copia de seguridad.

Ya no es necesario iniciar sesión en Amazon S3 para cargar, descargar o eliminar una copia de seguridad. Incluso puedes restaurar una copia de seguridad directamente desde S3.

Complementos

Lamentablemente, el nuevo sistema rompe los complementos existentes que sincronizaban automáticamente las copias de seguridad con Dropbox, Google Drive, Nextcloud o Box.

La buena noticia es que debería ser mucho más fácil agregar nuevas ubicaciones de copia de seguridad desde un complemento que antes. ¿Te gustaría probarlo?

Mientras tanto, puedes consultar Use rclone to sync backups to Dropbox or Google Drive.

¿Existe un tema de cómo hacerlo?

Sí, existe. Configure automatic backups for Discourse

[omarfilip]

@gerhard

Up until now backups were always stored on the server’s local disk – uploading backups to S3 was just an additional, optional step at the end of the backup process. With the new setting you can choose to store backups either locally or on S3.

Will the old way still work—local + S3? I like having a local backup along with the S3 for redundancy.

[gerhard (Gerhard Schlager)]

Local backups and sync to S3 is not possible anymore. You need to choose one backup location.

[pfaffman (Jay Pfaffman)]

This sounds great! Does it really mean Amazon S3 or will it also work with S3 lookalikes like Digital Ocean Spaces and that thing that starts with M? (I think that I’d made backups push to Spaces a while ago.)

Is it related to this bug? Admin dashboard won’t load after upgrade to v2.2.0.beta3 +36

[gerhard (Gerhard Schlager)]

I haven’t tested it with anything other than Amazon S3. It might work on lookalikes too if they support the required APIs. DO might work – /reference/api/spaces-api/ looks promising.

@pfaffman

Is it related to this bug? Admin dashboard won’t load after upgrade to v2.2.0.beta3 +36

Yes, it is.

[littleviolette]

I haven’t been able to get DigitalOcean Spaces to serve as my Discourse backup location. Might require extra setups than Amazon S3. Would appreciate it if someone can give me some pointers. Thanks!

[davidkingham]

I have this working on DO Spaces. Below are my settings for reference, be sure to take the bucket name out of the endpoint url.

[RBoy]

Clarification on how this works when settings are changed:

1. When once switches from S3 to Local or vice versa, do the existing backups get transferred or are they removed or are they left alone?
2. When one see’s the list of backups in the Backup page is there a way to tell the location or are they all from the selected location in the setting?
3. What is the meaning of this setting given that backups are no longer “synced” and either on S3 or Local? Disable the removal of backups from S3 when removed locally.

[gerhard (Gerhard Schlager)]

@RBoy

When once switches from S3 to Local or vice versa, do the existing backups get transferred or are they removed or are they left alone?

Existing backups won’t be touched. You need to delete them manually if you want to free up space.

@RBoy

When one see’s the list of backups in the Backup page is there a way to tell the location or are they all from the selected location in the setting?

Only from the selected backup location.

@RBoy

What is the meaning of this setting given that backups are no longer “synced” and either on S3 or Local? Disable the removal of backups from S3 when removed locally.

The description of the s3_disable_cleanup setting needs an update. It disables the removal of backups from S3 and makes the system ignore the value of maximum_backups when backup_location is set to S3.
I think we could actually remove the s3_disable_cleanup setting and allow disabling the cleanup by setting maximum_backups to 0. That would make it work for all backup locations the same way.

[RBoy]

@gerhard

The description of the s3_disable_cleanup setting needs an update. It disables the removal of backups from S3 and makes the system ignore the value of maximum_backups when backup_location is set to S3.
I think we could actually remove the s3_disable_cleanup setting and allow disabling the cleanup by setting maximum_backups to 0. That would make it work for all backup locations the same way.

That makes sense to remove the option and use zero to disable removal of back ups. A follow up clarification on this, when one changes the settings, say from 120 days to 30 days, would that trigger an automatic cleanup of all the back ups?

[gerhard (Gerhard Schlager)]

maximum_backups has nothing to do with days…
And no, the cleanup only happens after successful backups. Changing settings doesn’t trigger anything.

[RBoy]

Sorry, let me rephrase my question. When I change the maximum back ups from 120 to 30, the next time when it backs up, will it delete anything older than the last 30 back ups?

[gerhard (Gerhard Schlager)]

Yes, it will delete the older backups except for the last 30.