I’m trying to restore a backup from a hosted site running
"Discourse 2.0.0.beta5 - https://github.com/discourse/discourse version 6f32de186aa1d9e0814183f354bb01f5b66d1c0e.
When I restore on a clean build, or one that’s gone through the setup wizard, it fails and leaves the database in such a state that Discourse doesn’t run anymore.
(PostgreSQL) 9.5.10 in the container.
Starting restore: discourse-2018-04-03-183844-v20180328180317.tar.gz [STARTED] 'system' has started the restore! Marking restore as running... Making sure /var/www/discourse/tmp/restores/default/2018-04-03-222730 exists... Copying archive to tmp directory... Unzipping archive, this may take a while... tar: meta.json: Not found in archive tar: Exiting with failure status due to previous errors No metadata file to extract. Validating metadata... Current version: 20180328180317 Restored version: 20180328180317 tar: dump.sql: Not found in archive tar: Exiting with failure status due to previous errors Extracting dump file... Cannot restore into different schema, restoring in-place Enabling readonly mode... Pausing sidekiq... Waiting for sidekiq to finish running jobs... Restoring dump file... (can be quite long)
And then, when it’s done, Discourse says: