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 TABLE [2019-07-16 20:08:12] ALTER TABLE [2019-07-16 20:08:12] ALTER TABLE [2019-07-16 20:08:12] Migrating the database... [2019-07-16 20:08:16] Reconnecting to the database... [2019-07-16 20:08:16] Reloading site settings... [2019-07-16 20:08:16] Disabling outgoing emails for non-staff users... [2019-07-16 20:08:16] Clearing emoji cache... [2019-07-16 20:08:16] Disabling readonly mode... [2019-07-16 20:08:16] Clear theme cache [2019-07-16 20:08:22] Extracting uploads... [2019-07-16 20:08:40] Migrating uploads to S3... [2019-07-16 20:08:46] Restore process was cancelled! [2019-07-16 20:08:46] Trying to rollback... [2019-07-16 20:08:46] Rolling back... [2019-07-16 20:08:47] Cleaning stuff up... [2019-07-16 20:08:47] Removing tmp '/var/www/discourse/tmp/restores/default/2019-07-16-200516' directory... [2019-07-16 20:08:48] Unpausing sidekiq... [2019-07-16 20:08:48] Marking restore as finished...

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.

I did on the old server. Restoring I got the same error [2026-01-16 13:45:52] EXCEPTION: 3 posts are not remapped to new S3 upload URL. S3 migration failed for db ‘default’. [2026-01-16 13:45:52] /var/www/discourse/lib/file_store/to_s3_migration.rb:132:in `raise_or_log’

[imagem] Saiano: This check gave me 0 errors Well. Darn. Not sure what else to tell you. Did the good find your uploads? I’d probably just use the --pause switch and stop the restore before it does that check. I’d do what Richard said.

I’m not sure about your exact situation but you might simply want to turn off s3 uploads, make the backup, restore, and turn it on again. This has saved me many times.

So, I have to turn off this options, correct? [image]

Correct. uncheck “enable s3 uploads” backup / download upload / restore check “enable s3 uploads”

[imagem] RGJ: Correct. uncheck “enable s3 uploads” backup / download upload / restore check “enable s3 uploads” While checking “enable s3 uploads” I got an error [IMG_8462]

I don’t speak Italian when it’s not about food… maybe you can do us all a favor and copy/paste it into Google Translate :slight_smile:

[imagem] RGJ: I don’t speak Italian when it’s not about food… maybe you can do us all a favor and copy/paste it into Google Translate :slight_smile: Sorry Enable S3 uploads Stores uploads on Amazon S3 disk space. IMPORTANT: requires valid S3 credentials to be provided (both the access key ID and the access key secret). You cannot enable S3 uploads because they are already enabled globally, and enabling S3 uploads at the site level could cause critical issues with uploads.

I assume you already did it in app.yml then. Are (new) uploads working correctly? If so, then there is no issue.

[imagem] RGJ: I assume you already did it in app.yml then. Are (new) uploads working correctly? If so, then there is no issue. In app.yml I have s3 configured, correct. So, what I have to do to safely backup and restore without checking uploads? Simply uncheck “enable s3 uploads” doesn’t work

Processo de restauração cancelado na etapa de migração de uploads para o S3

Suporte ao Produto

Saiano (Saiano) 24 Janeiro , 2026 15:43 52

Muito obrigado, funcionou.

Tópico		Respostas	Vistas
Restore failed at "EXCEPTION: x of y uploads are not migrated to S3. S3 migration failed for db 'default'." Self-hosting	4	1244	10 Junho , 2022
Restore from backup fails due to S3 migration Product Support	8	1510	10 Setembro , 2019
Restore fails due to s3 migration failure Product Support	2	165	12 Agosto , 2026
Restore to New Host Product Support	13	858	15 Janeiro , 2026
Intended path to migrate S3 to local Self-hosting uploads , s3	5	985	13 Maio , 2023

Processo de restauração cancelado na etapa de migração de uploads para o S3

Related topics