I’ve been running into issues trying to run a restore on our Staging Discourse instance. Staging is running v2.4.0.beta1 +36 . Any idea where the breakdown might be or where to look? Thanks in advance! Below is the end of the log output: [2019-07-16 20:08:12] ALTER TABLE [2019-07-16 20:08:12] ALTER…

Discourse keeps a backup schema so it can roll back when a restore goes bad. You can go into your Postgres and issue drop schema backup cascade; If you don’t know how to do that you shouldn’t probably be doing it.

So S3 uploads are enabled in the database but not S3 backups?

Correct, this is about uploads migration. The S3 access credentials are present in the restored database so there is no need to require these to be in an environment variable as well. Providing the environment variables yield a failure as well Restoring uploads, this may take a while... Checking …

[图片] RGJ: it took a lot of work to figure out which ones needed to be mapped back to s3 and which one should not. Mixing local uploads with uploads stored on S3 isn’t supported. Yes, I know, it’s possible to end up in such a state when someone switches from local to S3 and doesn’t migrate exi…

If you need any help with drilling down to the root cause of issues like this, please let me know. I’m happy to help.

So, tried to restore my 2.2GB backup and got this - the restore failed: EXCEPTION: 44 posts are not remapped to new S3 upload URL. S3 migration failed for db ‘default’. I am on the 2.6b6, so a fairly recent version. The site is fairly old, from 2016. From time to time we run into backups were …

@gerhard Gave this another shot and I am still failing on the restore to the 44 posts are not remapped -error. Temporary disabling of S3 uploads prior to the backup (proposed by @RGJ does not solve the issue, and currently I don’t have a working backup scheme, which is pretty damn serious. …

[图片] ljpp: Any suggestions on what to try? Okay, this is the weirdest case I’ve seen so far. I stumpled upon this post. https://meta.discourse.org/t/using-object-storage-for-uploads-s3-clones/148916/160?u=ljpp After wasting hours on this already, I defined the DISCOURSE_CDN_URL just for kic…

@ljpp I seem to be in a similar situation with a restore failing with EXCEPTION: 1 posts are not remapped to new S3 upload URL. S3 migration failed for db ‘default’. Can you elaborate on how you found and deleted the offending posts? What commands are used?

He deleted the posts in question. But you wiped your install so you can’t do that, right?

[图片] BryanV: @ljpp I seem to be in a similar situation with a restore failing with EXCEPTION: 1 posts are not remapped to new S3 upload URL. S3 migration failed for db ‘default’. Can you elaborate on how you found and deleted the offending posts? What commands are used? I have this probl…

在迁移上传至 S3 步骤时恢复进程已取消

支持

ljpp (ljpp) 2020 年12 月 13 日 18:50 24

@gerhard

我又试了一次，但在恢复时仍然遇到“44 篇帖子未重新映射”的错误。

在备份前临时禁用 S3 上传（由 @RGJ 提出）并不能解决问题，目前我还没有可用的备份方案，这相当严重。

有什么建议可以尝试吗？

话题		回复	浏览量
Restore failed at "EXCEPTION: x of y uploads are not migrated to S3. S3 migration failed for db 'default'." Self-hosting	4	1093	2022 年6 月 10 日
Restore from backup fails due to S3 migration Support	9	1278	2019 年10 月 10 日
Restore to New Host Support	13	626	2026 年1 月 15 日
Intended path to migrate S3 to local Self-hosting uploads , s3	5	836	2023 年5 月 13 日
Unable to migrate to S3, therefore unable to restore from backup Self-hosting	3	1215	2022 年4 月 8 日

在迁移上传至 S3 步骤时恢复进程已取消

相关话题