Is there any way to restore your site from backup in the terminal?

[Ankhamax]

I did a backup of my site before I upgraded to the latest version of the discourse however I can’t even access my site any more even though the upgrade appears to be successful as no error is displayed. Is there anyway that I can restore my site from the backup that I created earlier from terminal app as I can’t access the site?

1. Is it possible?

2. If yes, where do discourse save or store the backups that I executed from the admin panel?

3. Is there any guide on how to restore the site from backup?

Thanks

[zogstrip]

@Ankhamax

Is it possible?

Yes.

@Ankhamax

If yes, where do discourse save or store the backups that I executed from the admin panel?

They’re stored in public/backups/default/.

@Ankhamax

Is there any guide on how to restore the site from backup?

Just run the following command (in the discourse directory)

script/discourse restore <filename.of.the.backup.tar.gz>

[Ankhamax]

Thank you.

[pfaffman (Jay Pfaffman)]

This seems like a handy thing to be able to do since if you screw up configuring SSO you can’t get back into your site. I spent a week one day trying to get SSO configured, and now that it is configured correctly it seems that my account on the SSO (which I don’t control) is gone, so I can’t get in.

So, script/discourse restore fails because thor isn’t installed.

gem install thor fixes that, but then I’m still denied because:

URGENT: FATAL:  Peer authentication failed for user "discourse"

Solving my immediate problem, I suppose I could turn off SSO from the Rails console. . .

edit: to disable SSO from the rails console:

cd /var/discourse
./launcher enter app
rails c
SiteSetting.enable_sso=false
exit
exit

[fefrei (Felix Freiberger)]

@pfaffman

since if you screw up configuring SSO you can’t get back into your site.

There’s a way to log in: Visit /users/admin-login, which can be used to log in via email

[srchip (Ranuka Perera)]

It worked for me by first getting into the app

./launcher enter app

then

discourse enable_restore
discourse restore <filename.of.the.backup.tar.gz>
discourse disable_restore

Using the script/discourse didn’t work

[Eric_Keller]

restoring from a app.yml and an external tar.gz file was mixing up some of the items I found along this thread:

TARBALL_PATH=$(ls local/backups/-*.tar.gz | tail -n 1)
TARBALL_NAME=$(basename ${TARBALL_PATH})
cat ${TARBALL_PATH} | docker exec -i app sh -c "cat - > /var/www/discourse/public/backups/default/${TARBALL_NAME}"
docker exec -i app sh -x << EOF
discourse enable_restore
discourse restore ${TARBALL_NAME}
discourse disable_restore
EOF

I had several pitfalls:

1. the tarball to restore has to be placed exactly in /var/www/discourse/public/backups/default/
2. the /var/www/discourse/script/discourse restore tarball-name did not work due to some single sign-on known issue
3. the version of thor installed by gem install thor was too recent and then incompatible with the rest.
4. finally one of the tarball I tried to restore from did not contain the “meta.json” file…

Hope this helps other in their restore journey.

[pfaffman (Jay Pfaffman)]

Rather than try to restore from app.yml it’s much easier to just ./launcher enter app and restore it from the command line.

[Eric_Keller]

The goal was to automate it without any entering container with the launcher.
Imagine your instance got lost for any reason. The only files you stored in git was your containers/app.yml and luckily you have a daily tarball backup.

[mrded (Dmitry Demenchuk)]

You can also do it directly to Postgres:

dropdb dbname
createdb dbname
gunzip -c filename.gz | psql dbname

[deargle (Dave Eargle)]

discourse is script/discourse – executed via bundle exec and with rails_env=production. Look at /usr/local/bin/discourse.

Running bundle exec script/discourse takes care of the thor mismatched gem version, too. Or just using the discourse convenience script.

[lyseoy]

Lo intenté y para esta línea:

discourse restore <filename.of.the.backup.tar.gz>

usé:

discourse restore root@droplet-01:/test/MyBackup.tar.gz

No estaba seguro si esa era la forma correcta de acceder a un archivo “fuera de la aplicación desde dentro de la aplicación”, pero pareció encontrar el archivo de respaldo e iniciar la restauración. La restauración terminó con mensajes ambiguos:

¡Terminado!
[FAILED]
Restauración completada.

Intenté acceder a mi foro nuevamente, pero aún no funciona, así que supongo que la restauración no funcionó.

[gerhard (Gerhard Schlager)]

@lyseoy

acceder a un archivo “fuera de la aplicación desde dentro de la aplicación”

No puedes. Necesitas copiar el archivo de respaldo en el directorio correcto. Sigue las instrucciones en Restore a backup from the command line si deseas restaurar desde la línea de comandos.

[Eric_Keller]

Aquí está el script de trabajo que utilizo para restaurar producción a desarrollo y pruebas:

#!/bin/sh
set +x
set -e
# Este script restaura la última copia de seguridad productiva al entorno de prueba/desarrollo
CONTAINER_NAME=app-test
LATEST_BACKUP=$(mc ls s3/backup-prod/default | tail -n 1 | cut -d ' ' -f 5)
mc cp s3/backup-prod/default/${LATEST_BACKUP} /tmp
# asegurar que /var/www/discourse/public/backups/default/ exista con la propiedad adecuada
docker exec -i ${CONTAINER_NAME} sh -c "mkdir -p /var/www/discourse/public/backups/default/ && chown -R discourse:www-data /var/www/discourse/public/backups/default/"
cat /tmp/${LATEST_BACKUP} | docker exec -i ${CONTAINER_NAME} sh -c "cat - > /var/www/discourse/public/backups/default/${LATEST_BACKUP}"
docker exec -i ${CONTAINER_NAME} sh -x << EOF
discourse enable_restore
rails runner "SiteSetting.set('backup_location', 'local')"
discourse restore ${LATEST_BACKUP}
discourse disable_restore
rm -f /var/www/discourse/public/backups/default/${LATEST_BACKUP}
EOF
# reconstruir contenedor
cd /var/lib/discourse/discourse_docker
stdbuf -oL -eL ./launcher rebuild ${CONTAINER_NAME} 2>&1 | sed 's/DISCOURSE_google_oauth2_client_secret=[^ ]*/DISCOURSE_google_oauth2_client_secret=***REDACTED***/g'
cd -
rm -f /tmp/${LATEST_BACKUP}

Faltaba rails runner "SiteSetting.set('backup_location', 'local')" y esto impedía la restauración desde el archivo tar de copia de seguridad.

Tenga en cuenta que la salida del script del lanzador tuvo que ser redactada, ya que revelaría secretos en su salida, especialmente cuando se realiza a través de un trabajo visible de CI/CD.

[pfaffman (Jay Pfaffman)]

Me alegra que tengas una solución. Aquí hay un par de cosas que facilitarán las cosas a otra persona.

Si usas DISCOURSE_ALLOW_RESTORE: 'true' en tu app.yml, puedes omitir la activación de la restauración. (De manera similar, puedes poner tu autenticación de Google en ENV y mantenerla completamente fuera de la base de datos).

Si tienes tanto staging como producción usando el mismo bucket S3, puedes restaurar la última copia de seguridad con

docker exec ${CONTAINER_NAME} bash -c '$(discourse restore|grep gz|head -1)'

Si necesitas leerlo localmente, de manera similar podrías anular la configuración del sitio con una ENV y leería la copia de seguridad más reciente de la tienda local.