# Como fazer backup do Discourse quando o backup falhou? **URL:** https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834 **Category:** Self-hosting **Created:** [4 Agosto , 2020 23:26 UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834 "2020-08-04T23:26:21Z") **Posts on this page:** 9 **Page:** 1
### Author: ![pauln](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@pauln](https://meta.discourse.org/u/pauln) #### Post date: [4 Agosto , 2020 23:26 UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834/1 "2020-08-04T23:26:21Z")
Olá pessoal, como posso fazer um backup do Discourse quando o backup falha? ![image](https://global.discourse-cdn.com/meta/original/3X/e/d/ed450de085346d20134fc72444eab5d3bb8775f3.png) ```plaintext [2020-08-04 23:22:28] Marcando backup como em execução... [2020-08-04 23:22:28] Verificando se '/var/www/discourse/tmp/backups/default/2020-08-04-232228' existe... [2020-08-04 23:22:28] EXCEÇÃO: Sem espaço no dispositivo - /var/www/discourse/tmp/backups/default/2020-08-04-232228 [2020-08-04 23:22:28] /usr/local/lib/ruby/2.0.0/fileutils.rb:245:in `mkdir' /usr/local/lib/ruby/2.0.0/fileutils.rb:245:in `fu_mkdir' /usr/local/lib/ruby/2.0.0/fileutils.rb:219:in `block (2 levels) in mkdir_p' /usr/local/lib/ruby/2.0.0/fileutils.rb:217:in `reverse_each' /usr/local/lib/ruby/2.0.0/fileutils.rb:217:in `block in mkdir_p' /usr/local/lib/ruby/2.0.0/fileutils.rb:203:in `each' /usr/local/lib/ruby/2.0.0/fileutils.rb:203:in `mkdir_p' /var/www/discourse/lib/backup_restore/backuper.rb:326:in `ensure_directory_exists' /var/www/discourse/lib/backup_restore/backuper.rb:27:in `run' /var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `block in start!' /var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `fork' /var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!' /var/www/discourse/lib/backup_restore/backup_restore.rb:13:in `backup!' /var/www/discourse/app/controllers/admin/backups_controller.rb:31:in `create' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_controller/metal/implicit_render.rb:4:in `send_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/abstract_controller/base.rb:198:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_controller/metal/rendering.rb:10:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/abstract_controller/callbacks.rb:20:in `block in process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/callbacks.rb:117:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/callbacks.rb:117:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/callbacks.rb:505:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/callbacks.rb:505:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/callbacks.rb:92:in ` __run_callbacks__' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/callbacks.rb:81:in `run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/abstract_controller/callbacks.rb:19:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_controller/metal/rescue.rb:29:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/notifications.rb:164:in `block in instrument' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/notifications/instrumenter.rb:20:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/notifications.rb:164:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_controller/metal/instrumentation.rb:30:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_controller/metal/params_wrapper.rb:250:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5/lib/active_record/railties/controller_runtime.rb:18:in `process_action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/abstract_controller/base.rb:137:in `process' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.2.5/lib/action_view/rendering.rb:30:in `process' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.7/lib/mini_profiler/profiling_methods.rb:106:in `block in profile_method' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_controller/metal.rb:196:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_controller/metal.rb:237:in `block in action' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/routing/route_set.rb:76:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/routing/route_set.rb:76:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/routing/route_set.rb:45:in `serve' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/routing/mapper.rb:49:in `serve' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/journey/router.rb:43:in `block in serve' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/journey/router.rb:30:in `each' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/journey/router.rb:30:in `serve' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/routing/route_set.rb:817:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/builder.rb:59:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:38:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/head.rb:13:in `call' /var/www/discourse/lib/middleware/anonymous_cache.rb:129:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/middleware/params_parser.rb:27:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/middleware/flash.rb:260:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/middleware/cookies.rb:560:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5/lib/active_record/query_cache.rb:36:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/callbacks.rb:88:in ` __run_callbacks__' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/callbacks.rb:778:in `_run_call_callbacks' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5/lib/active_support/callbacks.rb:81:in `run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/middleware/callbacks.rb:27:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/middleware/remote_ip.rb:78:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.0.1/lib/logster/middleware/reporter.rb:31:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5/lib/rails/rack/logger.rb:38:in `call_app' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5/lib/rails/rack/logger.rb:22:in `call' /var/www/discourse/config/initializers/100-quiet_logger.rb:10:in `call_with_quiet_assets' /var/www/discourse/config/initializers/100-silence_logger.rb:26:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.5/lib/action_dispatch/middleware/request_id.rb:21:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.7/lib/mini_profiler/profiler.rb:276:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-2.0.0.beta.2/lib/message_bus/rack/middleware.rb:60:in `call' /var/www/discourse/lib/middleware/request_tracker.rb:73:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5/lib/rails/engine.rb:518:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5/lib/rails/application.rb:165:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5/lib/rails/railtie.rb:194:in `public_send' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.5/lib/rails/railtie.rb:194:in `method_missing' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:580:in `process_client' /var/www/discourse/lib/scheduler/defer.rb:85:in `process_client' /var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in `process_client' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:674:in `worker_loop' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:529:in `spawn_missing_workers' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:140:in `start' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.9 ``` Tenho mais de 90 GB de espaço livre. ---
### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco) #### Post date: [5 Agosto , 2020 00:38 UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834/2 "2020-08-05T00:38:45Z")
> [@pauln](#): > > `ruby/2.0.0` Isso é uma instalação muito antiga? > [@pauln](#): > > `EXCEPTION: No space left on device` > [@pauln](#): > > Tenho mais de 90GB de espaço livre. Parece que o disco onde o Discourse tem o volume montado não possui esse mesmo espaço. ---
### Author: ![neounix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neounix/32/215617_2.png) [@neounix](https://meta.discourse.org/u/neounix) #### Post date: [5 Agosto , 2020 02:13 UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834/3 "2020-08-05T02:13:26Z")
> [@pauln](#): > > Olá pessoal, como posso fazer o backup do Discourse quando o backup falhou? Olá @pauln No seu último tópico, você mencionou que estava usando um VPS muito antigo com Linode Debian 7.5. Esse é um problema fácil de resolver se abordarmos passo a passo. Para começar, por favor, poste a saída deste comando, para que possamos ver um relatório do uso de espaço em disco do seu sistema de arquivos: ```plaintext df ``` Além disso, forneça um resumo do uso do seu espaço em disco da seguinte forma: ```plaintext cd /var/discourse/shared du -sh * ``` Esse é um problema fácil de resolver. Não se preocupe! * * * Nota: Também estamos assumindo que você está se preparando para migrar para um novo VPS, conforme mencionado no seu tópico anterior. * * * Referência à postagem anterior de @pauln sobre esta instalação: > [@“Your Docker installation is not using a supported storage driver.”](https://meta.discourse.org/t/your-docker-installation-is-not-using-a-supported-storage-driver/159688): > > Hey Guys, I have problem with an update giving me the following msg: If you wish to continue anyway using your existing unsupported storage driver, read the source code of launcher and figure out how to bypass this check. root@sendy:/var/docker/discourse# git pull Already up-to-date. root@\*\*\*\*:/var/docker/discourse# ./launcher rebuild app Your Docker installation is not using a supported storage driver. If we were t. overlay2 is the recommended storage driver, although zfs and aufs may work as… ---
### Author: ![pauln](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@pauln](https://meta.discourse.org/u/pauln) #### Post date: [5 Agosto , 2020 05:31 UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834/4 "2020-08-05T05:31:53Z")
> Aqui está um resumo da saída do df ![image](https://global.discourse-cdn.com/meta/original/3X/1/d/1d5fa11b30e46e30ff3cd316e5e4594bb1aea55e.png) > Aqui está um resumo do du -sh \* ![image](https://global.discourse-cdn.com/meta/original/3X/2/4/247a7280c039c8c62b0d3881c33171b2f7fc9d6f.png) Sim, vou migrar para um NOVO VPS, mas estou tentando fazer um backup primeiro antes de mudar para o novo host. ---
### Author: ![neounix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neounix/32/215617_2.png) [@neounix](https://meta.discourse.org/u/neounix) #### Post date: [5 Agosto , 2020 05:36 UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834/5 "2020-08-05T05:36:46Z")
> [@pauln](#): > > Sim, vou migrar para um NOVO VPS, mas estou tentando fazer um backup primeiro antes de mudar para o novo host. Sim, eu sei. Você está fazendo a coisa certa e um ótimo trabalho. Vamos tentar uma estratégia diferente. Você consegue fazer um backup com sucesso sem incluir os uploads? Se sim, podemos simplesmente (1) usar esse backup e (2) um `tar` separado do diretório de uploads e alcançar o que você deseja. Portanto, por favor, tente fazer apenas um backup sem os uploads (o botão do meio abaixo); selecionando essa opção na janela de backup; e nos responda. ![Screen Shot 2020-08-05 at 12.37.21 PM](https://global.discourse-cdn.com/meta/original/3X/e/0/e0aa46ec4bae350bdcaa126c0045eec1e7a8b07d.jpeg) Se isso falhar, tentaremos fazer o backup do banco de dados manualmente a partir da linha de comando 🙂, o que é bastante simples e funcionará, tenho quase certeza (fazemos isso o tempo todo e raramente restauramos pela interface gráfica). > Referência: > [@Manually create and restore Discourse backups](https://meta.discourse.org/t/advanced-manual-method-of-manually-creating-and-restoring-discourse-backups/18273): > > As discussed [below](https://meta.discourse.org/t/advanced-manual-method-of-manually-creating-and-restoring-discourse-backups/18273/7), a warning for newbies: this is an advanced method! there is an automated, web UI way to restore from backups at /admin/backups which is so much easier. with the method below, no automatic backup is kept of the /var/discourse/containers/app.yml file which contains essential SMTP credentials and SSL customizations. Keep a copy of this offsite whenever you change it. If you are using digital ocean, keep frequent snapshots of your droplets - preferably before each time you run .… * * * Nota: O que quer que você decida fazer, @pauln, por favor, não destrua seu VPS existente rodando Debian 7.5 e Discourse até que tenha instalado com sucesso outra instância do Discourse (e restaurado e testado) em seu novo VPS. ---
### Author: ![pauln](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@pauln](https://meta.discourse.org/u/pauln) #### Post date: [5 Agosto , 2020 06:32 UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834/6 "2020-08-05T06:32:20Z")
> [@neounix](#): > > Então, por favor, tente fazer apenas um backup sem os uploads (o botão do meio abaixo); selecionando essa opção na janela de backup; e nos avise. Também falhou. Então, nossa próxima opção é fazer via linha de comando? ---
### Author: ![neounix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neounix/32/215617_2.png) [@neounix](https://meta.discourse.org/u/neounix) #### Post date: [5 Agosto , 2020 06:38 UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834/7 "2020-08-05T06:38:23Z")
> [@pauln](#): > > Também falhou. Então, nossa próxima opção é fazer via linha de comando? Sim, senhor. Isso deve ser suficiente. Avise-nos como foi ou se precisar de mais ajuda. Você precisará: 1. realizar um dump manual do banco de dados PostgreSQL do Discourse; e 2. criar um arquivo manual da pasta de uploads. As instruções para criar os arquivos manuais estão OK na referência acima. No entanto, quando testei essas instruções agora mesmo, não consegui escrever no diretório compartilhado de dentro do contêiner, então fiz isso primeiro (assumindo que sua instância é `app`): ```plaintext docker exec -it app bash mkdir /shared/mybackups chown postgres /shared/mybackups ``` e alterei todos os caminhos para escrever em `/shared/mybackups` em vez de `/shared`, mas você pode não ter esse problema. Aguardo suas novidades em breve. ---
### Author: ![pauln](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@pauln](https://meta.discourse.org/u/pauln) #### Post date: [5 Agosto , 2020 19:57 UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834/8 "2020-08-05T19:57:30Z")
Ei, sou muito grato pela sua ajuda. Funcionou! Mudei para um novo VPS e está funcionando bem agora 🙂 ---
### Author: ![neounix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neounix/32/215617_2.png) [@neounix](https://meta.discourse.org/u/neounix) #### Post date: [5 Agosto , 2020 21:40 UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834/9 "2020-08-05T21:40:27Z")
Notícias maravilhosas e ótimo trabalho, @pauln. Parabéns pela sua atualização bem-sucedida!